Configuring and Deploying SIS - Details

This topic describes how to configure and deploy Sourcing Integration Services with WebSphere 6.1.0.

How to Configure and Deploy SIS

The following steps explain how to configure and deploy SIS:
  1. Go to Servers > Application servers > server1 > ORB Service. In the Configuration page, enable Pass by reference

  2. Create an .ear file, for example sisApp.ear, using the following steps:

    1. Extract std_eisbeans.jar.

    2. Modify the META-INF/MANIFEST.MF to include classpath fro xjsbeans_ws60.jar.  For example:

      Manifest-Version: 1.0

      Class-Path: xjsbeans_ws60.jar

      Created-By: 1.4.2_05 (Sun Microsystems Inc.)

    3. Create std_eisbeans.jar with the following command:

      jar cvfm std_eisbeans.jar META-INF/MANIFEST.MF com org

      META-INF

    4. Create an .ear file with std_eisbeans.jar, xjsbeans_ws60.jar, and META-INF/application.xml

      jar cvf sisApp.ear std_eisbeans.jar xjsbeans_ws60.jar META-INF

  3. Run the Administration Console.

  4. Click Applications > Install New Application. The Enterprise Application page appears.

  5. Browse for the supplied sisApp.ear file and click Next. The Preparing for the application installation page appears.

  6. Accept the default settings and click Next. The Install New Application page appears.

  7. Select Deploy enterprise beans and click Next.

  8. Click Next. The Provide options to perform the EJB Deploy page is displayed.

  9. Enter the following classpath and select Oracle_V9I for the database type:

    <SIS HOME>\application\lib\csvc-cis-adapter.jar

    <SIS HOME>\application\admin\configs

    <SIS HOME>\application\lib\eis.jar

    <SIS HOME>\application\lib\EXML.jar

    <SIS HOME>\application\lib\logapi.jar

    <SIS HOME>\application\lib\tapi.jar

    <CIS HOME>\lib\cis.jar

    <CIS HOME>\lib\cis-util.jar

    <CIS HOME>\lib\log4j.jar

    <CIS HOME>\lib\client50.jar

    <CIS HOME>\lib\jmxri.jar

    <CIS HOME>\lib\connector.jar

    <CIS HOME>\lib\jaxen-full.jar

    <CIS HOME>\lib\jdom.jar

    Where

    <SIS HOME> = SIS installation directory

    <CIS HOME> = CIS installation directory

  10. Click Next. The Provide listener bindings For message-driven beans page is displayed.

  11. Click Activation Specification options and enter the JNDI name for the MDBs as shown below:

    • For the EJB EventDisplatcherMDB, enter the Activation Specification name as EventDispatcherMDBActivationSpec and make sure that Listener Port is not selected.

    • For the EJBReleaseServiceListenerMDB enter the Activation Specification name as ReleaseServiceListenerMDBActivationSpec and make sure that Listener Port is not selected.

    • For the EJBMultiplexServiceListenerMDB enter the Activation Specification name as MultiplexServiceListenerMDBActivationSpec and make sure that Listener Port is not selected.

    • For the EJB EISHKListener enter the Activation Specification name as EISHKListenerActivationSpec and make sure that Listener Port is not selected.

  12. Click Next. The Provide JNDI Names for Beans page is displayed. This allows specification of the JNDI names. The EJBs should be shown as given below:
     

    EJB JNDI
    ImportBusinessController ImportBusinessController
    ExportBusinessController ExportBusinessController
    ServiceQueueBean ServiceQueueBean
    eis.EISManager eis.EISManager
    eis.ExportHelper eis.ExportHelper
  13. Click Next. The Summary page is displayed.

  14. Click Finish.

  15. Click Save to Master configuration after deploying successfully.

  16. Append the following path to the classpath for the JVM under:

    Servers > Application Servers > <server name> >Java and Process Management > Process Definition > Java Virtual Machine

    <SIS HOME>\application\lib\csvc-cis-adapter.jar

    <SIS HOME>\application\admin\configs

    <SIS HOME>\application\lib\eis.jar

    <SIS HOME>\application\lib\EXML.jar

    <SIS HOME>\application\lib\logapi.jar

    <SIS HOME>\application\lib\tapi.jar

    <CIS HOME>\lib\cis.jar

    <CIS HOME>\lib\cis-util.jar

    <CIS HOME>\lib\log4j.jar

    <CIS HOME>\lib\client50.jar

    <CIS HOME>\lib\saxxon.jar

    <CIS HOME>\lib\xerces.jar

    Where

    <SIS HOME> = SIS installation directory

    <CIS HOME> = CIS installation directory

  17. To create BUS and JMS Providers, do the following:

    •  In the left navigation pane, expand Service Integration and click Buses. The Buses page appears.

    • Click New.

    • On the New bus configuration page, enter SISBUS as the bus Name and click OK.

    • On the Buses page, click SISBUS, which appears as a link to open the relevant configuration page.

    • Click Bus members.

    • On the Bus Members page, click Add.

    • Select the Server, for example <machine_name>:server1, in the Add a new Bus Member page, and click Next.

    • Click Finish to add the bus member.

    • Return to the SISBUS configuration page, and in the Additional Properties section, click Destinations. The Destinations page appears.

    • Click New to create a destination on this bus. The Create New Destination page appears.

    • Select Queue as the destination type and click Next. The Create new queue page appears.

    • Enter HKQueue as the Identifier and click Next.

    • Select a server, the same one selected above, as the Bus member and click Finish.

    • Similarly, create four more destinations with the name JCQueue, OBQueue, MSQueue, and RSQueue.

    • Click Save link to save the changes to the master configuration.

  18. To create JMS Resources, do the following:

    • On the WebSphere Server Administrative Console, in the left navigation pane, click Resources > JMS Providers > Default messaging. The Default Messaging Provider configuration page appears. Click JMS queue connection factory.

    • Click New. The New JMS Queue connection factory configuration page appears.



    • In the Administration section, enter EISJMSQueueConnectionFactory as the Name and JNDI Name.

    • Select SISBUS as the Bus name.

    • Specify InboundBasicMessaging in the Target inbound transport chain field.

    • In the Provider End Points field enter:

      <host name>:<port no. for Basic Endpoint address>, <host name>:<port no. for secure endpoint address>:BootstrapSecureMessaging

      For example, localhost:7276, localhost:7286:BootstrapSecureMessaging

      Here the port number 7276 and 7286 are the default SIB Endpoint Address and Endpoint Secure Address respectively.

      Please note that to view all port numbers configured in your server, go to Application > Servers > server1 > Ports.

    • Select Bus Member Name as the Target Type.

    • Click Save in the Messages section at the top

    • Return to the Default Messaging Provider configuration page, and in the Destinations section, click JMS queue.

    • Click New and add the following queue entries:
       

      Name JNDI Name Bus Name Queue Name
      EISJobController-QueueQ EISJobController-Queue SISBUS JCQueue
      EISMultiplexService-QueueQ EISMultiplexService-Queue SISBUS MSQueue
      EISOutboundQueueQ EISOutboundQueue SISBUS OBQueue
      EISReleaseService-QueueQ EISReleaseService-Queue SISBUS RSQueue
      housekeepQueueQ housekeepQueue SISBUS HKQueue


  19. To activate JMS Activation Specification, do the following:

    • Go to Default messaging provider > JMS activation specification and add the following entries:
       
      Name JNDI Name Dest JNDI Name Bus Name
      EISHKListenerAS EISHKListenerActivationSpec housekeepQueue SISBUS
      EventDispatcherMDBAS EventDispatcherMDBActivationSpec EISJobControllerQueue SISBUS
      ReleaseServiceListenerMDBAS ReleaseServiceListenerMDBActivationSpec EISReleaseServiceQueue SISBUS
      MultiplexServiceListenerMDBAS MultiplexServiceListenerMDBActivationSpec EISMultiplexServiceQueue SISBUS





      Please note that JNDI Name for the Activation specification must be matched to the one present in the Provide listener bindings for message-driven beans. For reference, go to  Enterprise Applications > sisApp > Provide listener bindings for message-driven beans.

      Also note that the Destination JNDI Name must be matched to the Destination JMS Queue.

  20. Specify the classpath for ojdbc14.jar under Resources > JDBC Providers > Oracle JDBC Driver.

  21. Add data source for EIS under Resources > JDBC Providers > Oracle JDBC Driver > Data Sources, assuming Oracle JDBC driver is defined for XJS.




    Name: EISDataSource
    JNDI Name: EISDataSource
    Authentication alias: (use XJS database authentication definition).
    For the data source custom properties define connection details for your SRM database:
    URL: jdbc:oracle:thin:@<host>:<port>:<sid>
    driver type : thin
    databaseName : <sid>
    portNumber : <port>
    serverName : <host>
    dataSourceName : EISDataSource
    preTestSQLString : SELECT 1 FROM DUAL

  22. Restart WAS server.

  23. In order to successfully install and start the sis CIS adapter for the application interface, the following entries and paths must be configured:

    • <SIS HOME>\application\cis-src\CSVCMetadataType.xml

      • The following EISInitializer entries for serverHost and JNDIFactory must be set as follows:

        • <property name = serverHost value = iiop://trafford:2809>

        • <documentation> The URL of the application server where Sourcing Integration Services is installed. It should be of the form protocol://hostname:portnumber</documentation></property>

        • <property name = JNDIFactory value = com.ibm.websphere.naming.WsnInitialContextFactory>

        • <documentation> The implementation class of the InitialcontextFactory of the AppServer where Sourcing Integration Services is installed. For weblogic its value is set to weblogic.jndi.WLInitialContextFactory</documentation></property>

    • <SIS HOME>\application\cis-src\CSVCMetadataRMIBindings.xml

      • The path for sis adapter should be set as specified below:

        • <classPath>

          <path>.</path>

          <path><CIS HOME>\lib\jmxri.jar</path>

          <path><CIS HOME>\lib\connector.jar</path>

          <path><CIS HOME>\lib\jaxen-full.jar</path>

          <path><CIS HOME>\lib\jdom.jar</path>

          <path><CIS HOME>\lib\saxpath.jar</path>

          <path><SIS HOME>/application/lib/eisbeans_stubs.jar</path>

          <path><SIS HOME>/application/lib/eis.jar</path>

          <WAS HOME>/lib/j2ee.jar</path>

          <WAS HOME>/lib/namingclient.jar</path>

          <WAS HOME>/lib/naming.jar</path>

          <WAS HOME>/properties</path>

          <WAS HOME>/application/cis-src/lib/csvc-cis-adapter.jar</path>

          <WAS HOME>/lib/ras.jar</path>

          <WAS HOME>/lib/wsexception.jar</path>

          <WAS HOME>/lib/bootstrap.jar</path>

          <WAS HOME>/lib/emf.jar</path>

          <WAS HOME>/lib/ecutils.jar</path>

          <WAS HOME>/lib/iwsorb.jar</path>

          <WAS HOME>/lib/idl.jar</path>

          <WAS HOME>/lib/ffdc.jar</path>

          <WAS HOME>/lib/utils.jar</path>

          </classPath>

          Where

          <SIS HOME> = SIS installation directory

          <CIS HOME> = CIS installation directory

          <WAS HOME> = WAS server installation directory

  24. Copy all templates from <SIS HOME>/application/admin/configs/templates directory to <SIS HOME>/application/admin/configs directory. Please note that log.cfg, eis.cfg and eventconfig.xml files need to be modified with the appropriate values.