Deploying and configuring for scenario 1

Scenario 1 sample application provides a configured instance of the adapter and all the necessary SCA artifacts, so you are not required to deploy the package and configure the adapter. Simply import the enterprise archive (EAR) file to your WebSphere® Integration Developer workspace using WebSphere Integration Developer.

Why and when to perform this task

Follow these steps to deploy and configure the adapter for scenario 1:

Steps for this task

  1. Uncompress the file SampleOutboundApp.ear to a directory of your choice. The CWYES_PeopleSoft.rar file and various JAR files are now listed in the directory.
  2. In WebSphere Integration Developer, create a module and assign it the same name as the EAR file without the letters "App." For example, if the EAR file is SampleOutboundApp.ear, then the module name in this case should be SampleOutbound.
  3. If the connector project is not already defined in your WebSphere Integration Developer workspace, import the latest CWYES_PeopleSoftAdapter.rar file in WebSphere Integration Developer. Importing the RAR file creates a connector project for the adapter.
  4. Establish a dependency between the connector project and the module project by doing the following:
    1. On the Project tab, right-click on the module.
    2. Select Properties > Java Build Path.
    3. Right-click on the module and select Open Dependency Editor.
    4. Select CWYES_PeopleSoft in the J2EE selection box.
    5. Select the check boxes for On Build Path and Deploy with Module.
  5. Update the Java™ build path so that it includes the PeopleSoft dependency jars psjoa.jar and psftci.jar
  6. Use any zip utility to extract the contents of the module JAR file into the module you created in Step 2. For example, extract sampleoutbound.jar into the module sampleoutbound.
  7. Refresh the module.
  8. Open the Business Integration perspective and edit the service description using the assembly editor. Do the following:
    1. For outbound only: Select "sampleoutbound" within the project "sampleoutbound." For inbound only: Select "sampleinbound" within the project "sampleinbound."
    2. For outbound: Set the Managed Connection factory and Resource adapter properties. For inbound: Set the Activation Specification and Resource adapter properties. This graphic is described in surrounding text.
    3. Set the J2C authentication alias you have created. If you have not created one, do so through the WebSphere Process Server administrative console.

      This graphic is described in surrounding text.

  9. For inbound operations: You must create the listener MDB class and then bind it in the "sampleinbound" assembly diagram. Follow these steps to do so:
    1. Open the sampleinbound assembly diagram under the sampleinbound project.
    2. Select the component without implementation task.
    3. Click the assembly diagram. "Component1" will be created.
    4. Link "PeopleSoftInboundInterface" to "Component1" you have just created.This screen capture is described in surrounding text.
    5. Right-click "Component1", and then selectGenerate Implementation > Java .
    6. Add Javacode as needed to the following methods that support outbound operations:
      emitCreateAfterImageWbiCustomerCi
      emitUpdateAfterImageWbiCustomerCi
      emitDeleteAfterImageWbiCustomerCi
      The following example shows a system.out added to methods in order to confirm entry to the listener.
      This screen capture is described in surrounding text.
  10. Go to the Projects tab and select the check box next to the Connector project you have created.
  11. Start WebSphere Process Server.
  12. After WebSphere Process Server has started, export an EAR out of the project and install the it through the administrative console.
  13. Check through the administrative console to ensure that the application has successfully started. Stop and restart the server if not.
  14. For inbound operations only: Once the application starts, check the following to ensure success: for inbound operations, testing of the sample app ends at this point.
    1. Navigate to WPS_Folder>\bi_v6\profiles\default\logs and examine the adapter trace file, PeopleSoftInboundTrace.txt to make sure it has the line ‘emit<operation>AfterImageWbiCustomerCi successful, where <operation> can be Create, Update or Delete.
    2. Examine the IBM_EVENT_TBL record to ensure that it contains events.
    3. Examine the data in the PeopleSoft EIS by checking event status through the IBM_EVENT_CI. If the transaction was successful, the status will be set to 1.
    These steps conclude testing the sample application for inbound operations.
  15. For outbound operations only: use WebSphere Integration Developer test client to test the adapter by doing the following:
    1. Ensure you are in the Business Integration Perspective. Right-click sampleoutbound project > Test > Test Module.
    2. Select the operation as needed. Naming conventions correspond to the operation functions. For example, createWbiCustomerCi is for creating the component hierarchy in the PeopleSoft EIS.
    3. Set values as needed, and set the verb for create, update, or delete operations.
    4. Click continue.
    5. Check the returned object to test the success of the operation. If retrieval is successful, you will be able to see the object in the test module. If retrieval is not successful, you will see the exception in the test module.
      This screen capture is described in surrounding text.
    These steps conclude testing the sample application for outbound operations.
Related concepts
Structure of the application package
Business object structure
Related tasks
Deploying and configuring for scenario 2

Terms of use |

Last updated: Sun Mar 12 11:24:20 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)