IBM WebSphere. IBM WebSphere Adapter for PeopleSoft Enterprise Quick Start Scenarios

Transcription

1 IBM WebSphere Adapter for PeopleSoft Enterprise Quick Start Scenarios

2 Note: Before using this information and the product it supports, read the information in the Notices section, at the end of this document. This edition applies to version 7, release 5, and modification 0 of IBM WebSphere Adapter for <adapter-name> and to all subsequent releases and modifications, until otherwise indicated in new editions. Copyright International Business Machines Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Chapter 1. Introduction...6 Learning Objectives... 6 Audience... 6 Software prerequisites... 6 Chapter 2. Preparing to test the scenarios...8 Configuration prerequisites Import the sample projects into PeopleTools Add the trigger to WBI_CUSTOMER_COMP component Create the Java API for Component Interface Create a J2C Authentication Alias in IBM Process Server Import the adapter project in the IBM Integration Designer Extracting the sample files Chapter 3. Scenario1 : Sending data to PeopleSoft Enterprise application (outbound processing)...25 Configuring the adapter for outbound processing Deploying the module to the test environment Testing the assembled adapter application Clearing the sample content Chapter 4. Scenario2 : Receiving events from PeopleSoft Enterprise application (inbound processing)...46 Configuring the adapter for inbound processing Deploying the module to the test environment Testing the assembled adapter application Clearing the sample content Chapter 5. Scenario3 : Effective Sequence number is not required for data insert (outbound processing)...73 Configuring the adapter for outbound processing Deploying the module to the test environment Testing the assembled adapter application Clearing the sample content Chapter 6. Troubleshooting Improve the IBM Process Server trace level Connection issues with PeopleSoft Enterprise application... 88

4 Chapter 7. Notices...89

5

6 Chapter 1. Introduction WebSphere Adapter for PeopleSoft Enterprise is a J2EE component compliant with the JCA 1.5 specification. It will enable bidirectional connectivity to a PeopleSoft Enterprise application. The clients can send outbound messages to the resource adapter via the Common Client Interface (CCI) defined by the JCA specification. The resource adapter will perform the appropriate operation on the data based on the content and operation specified in the interaction specification. For inbound messages, the resource adapter uses the JCA message inflow contact. It will define a message listener interface and the endpoints or the message driven beans should implement this interface. This will enable the endpoints to receive any subscribed events from the resource adapter. To gain practical knowledge in setting up and deploying the adapter, complete one or more of below tutorials. Everything you need to complete a tutorial is contained in the tutorial. Perform the prerequisite tasks, before you attempt to complete the tutorials. Each tutorial takes less than an hour to complete. Learning Objectives After completing the scenario based tutorials in this document, you should be able to perform the following tasks: 1. Create an adapter project in IBM Integration Designer. 2. Discover services and associated business objects from the Enterprise Information system (EIS), and add these services and business objects to your adapter project. 3. Create a deployable module that you can install on IBM Process Server or WebSphere Enterprise Service Bus. 4. Test the module and validate the results. Audience These scenario based tutorials are meant to help integration developers who design, assemble, test, and deploy business integration solutions. Software prerequisites Before you test these scenarios, you must install the following applications:

7 1. IBM Integration Developer version WBPM Advanced Process Manager version PeopleTools, version 8.4x

8 Chapter 2. Preparing to test the scenarios Configuration prerequisites Before you test these scenarios, you must complete the following tasks: Import the sample projects into PeopleTools Add the trigger to WBI_CUSTOMER_COMP component Create the Java(TM) API for the Component Interfaces Create a J2C authentication alias in IBM Process Server Create an adapter project in the IBM Integration Designer The detailed steps for these tasks are provided in the following sections. 2.1 Import the sample projects into PeopleTools Perform the following steps to import WBI_CUST_PROJ project into PeopleTools and build it. 1. Copy WBI_CUST_PROJ project to a temp directory (C:\Projects) on the machine where the PeopleTools runs. 2. Log on to the PeopleSoft application designer. 3. Select Tools > Copy Project > From File. 4. Browse to C:\Projects directory. From the Select Project from the List Below, double-click WBI_CUST_PROJ. 5. In the Copy From File dialog, click Copy. Wait for the operation to complete. 6. Select WBI_CUST_PROJ in the left panel, and then select Build > Project from the main menu. 7. In the Build panel, select the following check boxes: a) Create Tables b) Create Views c) Create Trigger d) Run and build script 8. Click Build, to begin to build the project.

9 9. Click Close, to exit the Build Progress dialog. 10. In the Build Log view of the application designer, check the log messages to confirm that 3 records were processed correctly. 11. Select File > Save All to save the changes. Repeat the above steps to import IBM_EVENT_V600 project into PeopleTools and build it. This project is under the directory <WID_HOME>\ ResourceAdapters\PeopleSoft_ \Scripts. Then you need to configure the user security for the Component Interfaces. 12. Log into PeopleSoft Web Client with the URL: Go to PeopleTools > Security > Permissions & Roles > Permission Lists. 14. Input PTPT1200 in the edit box of begins with and click Search. 15. Go to the Component Interfaces tab, click to add the Component Interface WBI_CUSTOMER_COMP_INTERFACE. 16. Click Edit of WBI_CUSTOMER_COMP_INTERFACE.

10 17. Select Full Access for all methods and click OK. 18. Go back to the Component Interfaces tab, click to add the Component Interface IBM_EVENT_CI. 19. Click Edit of IBM_EVENT_CI.

11 20. Select Full Access for all methods and click OK. 21. Go back to the Component Interfaces tab and press Save button to save the changes. 2.2 Add the trigger to WBI_CUSTOMER_COMP component For inbound operation, the adapter needs to retrieve the events from the IBM_EVENT_BC component. Add a trigger to WBI_CUSTOMER_COMP component, so that the events can be generated automatically when the data is created or modified against this component. Perform the following steps to add a trigger: 1. In PeopleSoft application designer, open WBI_CUST_PROJ project. 2. In the left panel, right-click on WBI_CUSTOMER_COMP and select View PeopleCode.

12 3. In the PeopleCode edit window, select SavePostChange in the right panel. 4. Input the following PeopleCode in the edit window.

13 Declare Function IBMPublishEvent PeopleCode IBM_FETCH_ID.IBM_NEXT_EVENT_ID FieldFormula; Component string &BONAME1; Component string &KEYLIST1; &BONAME1 = "WbiCustomerCompInterfaceBG"; &KEYLIST1 = "WBI_CUSTOMER.WBI_CUSTOMER_ID"; /* Check if Component Changed before calling function*/ If ComponentChanged() And %UserId <> "CW" Then /* Publish this event to the IBM WebSphere IBM_EVENT_TBL for polling */ IBMPublishEvent(&BONAME1, &KEYLIST1); End-If; 5. Select File > Save All to save the changes. Note: In the PeopleCode, the value of &BONAME1 should match the actual business object name that you generate in IBM Integration Designer while performing tutorial 2. In this sample document, the business object name is WbiCustomerCompInterfaceBG. If it is different in your scenario, modify the above PeopleSoftCode correspondingly. To ensure the trigger that was created above can work well, you need to do some initialization work. Connect to the database that the PeopleTools uses, and run the following SQL statement: $ insert into PS_IBM_FETCH_ID values(1000); $ commit; 2.3 Create the Java API for Component Interface The Component Interface API provides access to all the objects and PeopleCode methods. You can manually generate these API using the application designer, and then compile them to a PSFTCI.jar file.

14 1. In PeopleSoft application designer, open IBM_EVENT_CI Component Interface. 2. Select Build->PeopleSoft API from the main menu. 3. In the Build PeopleSoft API Bindings dialog, make sure only the Build check box under Java Classes is selected. Set the Target Directory for storing the generated Java files. In the Select API to Build list, select the following items: CompIntfc.CompIntfcPropertyInfo CompIntfc.CompIntfcPropertyInfoCollection All beginning with CompIntfc.IBM_EVENT_CI All beginning with CompIntfc.WBI_CUSTOMER_COMP_INTERFACE 4. Click OK. Check the target directory to make sure the Java files are generated correctly. 5. Copy the generated Java files to C:\Temp directory, then copy psjoa.jar file from <PeopleTools_HOME>\web\psjoa to C:\Temp directory 6. Enter directory as C:\Temp and run the following commands to build the Java files. $ javac -classpath.\psjoa.jar PeopleSoft\Generated\CompIntfc\*.java $ jar -cvf PSFTCI.jar PeopleSoft\Generated\CompIntfc\*.class

15 These two JAR files psjoa.jar and PSFTCI.jar are used by the adapter to access the PeopleSoft Enterprise application later. 2.4 Create a J2C Authentication Alias in IBM Process Server Perform the following steps to create a J2C authentication alias in IBM Process Server, which will be used by the adapter to access the PeopleSoft Enterprise application. 1. Open IBM Integration Designer and switch to Business Integration perspective. 2. Select Servers tab, right-click on IBM Process Server v7.5 and select Start. Figure 1: Start IBM Process Server

16 3. After the server starts up, right-click on IBM Process Server V7.5 and select Administration -> Run administrative console. Figure 2: Run Administrative console 4. Log on to the administrative console. 5. Select Security -> Global security. Figure 3: select Security 6. In Global security window, select Authentication -> Java Authentication and Authorization Service -> J2C authentication data.

17 Figure 4: Java Authentication and Authorization Service (JAAS) 7. Click New, to create a new alias. Figure 5: New Alias

18 8. Specify the properties with the following values as shown in the following screen capture. Property Alias User ID Password Value PSFT_Alias PS PS Figure 6: Create a New Authentication Alias with User ID, Password 9. Click Apply. 10. Click Save to save changes. Figure 7: Save JAAS Alias

19 11. Then navigate to J2C authentication data to check the alias that was created. It will be used during the later tutorials. Figure 8: Select Authentication Entries 2.5 Import the adapter project in the IBM Integration Designer To import the RAR file into the project, follow these steps: 1. Open IBM Integration Designer.

20 2. Select File -> Import. Figure 9: Import adapter with WID

21 3. In the Import window, select RAR file option and click Next. Figure 10: Import adapter RAR File 4. In the Connector Import window, do the following: In the Connector file field, click Browse to locate the folder that contains the adapter file, i.e. CWYES_PeopleSoft.rar. Leave the default values as is for the other fields. The connector module is selfnamed according to the adapter. IBM Process Server v7.5 is the expected target runtime. Click Finish.

22 Figure 11: Connector Import window prompt 5. Click No as there is no need to change to the J2EE perspective. Figure 12: Confirm Perspective Switch 6. Select Window->Open Perspective->Other->Java. Confirm that the adapter has been installed in IBM Integration Designer.

23 Figure 13: Project Explorer's view in Business Integration perspective This completes import of RAR file to adapter. Extracting the sample files Replicas of the artifacts that you create when using the external service wizard are provided as sample files for your reference. Use these files to verify that the files you create with the external service wizard are correct. Some sample files are provided under Sample folder and their detailed contents are shown as below. You can create a temp folder and extract the archives: File name Description Samples\referencefiles\Tutorial1.zip TestOutbound\ PeopleSoftOutboundInterface.import TestOutbound\ PeopleSoftOutboundInterface.wsdl TestOutbound\ WbiCustomerCompInterfaceContaine Contains the SCA import for the resource adapter. Contains the SCA wsdl file for the resource adapter Business object definition for the business object container.

24 r.xsd TestOutbound\ WbiCustomerCompInterfaceBG.xsd TestOutbound\ WbiCustomerCompInterface.xsd TestOutbound\WbiAddress.xsd TestOutbound\WbiPhone.xsd Business object definition for the business object graph. Business object definition for the Customer business object. Business object definition for the Address business object. Business object definition for the Phone business object. Samples\referencefiles\Tutorial2.zip TestInbound\ PeopleSoftInboundInterface.export TestInbound\ PeopleSoftInboundInterface.wsdl TestInbound\ WbiCustomerCompInterfaceBG.xsd TestInbound\ WbiCustomerCompInterface.xsd TestInbound\WbiAddress.xsd TestInbound\WbiPhone.xsd Contains the SCA export for the resource adapter. Contains the SCA wsdl file for the resource adapter Business object definition for the business object graph. Business object definition for the Customer business object. Business object definition for the Address business object. Business object definition for the Phone business object.

25 Chapter 3. Scenario1 : Sending data to PeopleSoft Enterprise application (outbound processing) The tutorial explains a scenario where a user wants to create a customer record in PeopleSoft Enterprise application using a SCA client. In this scenario, the user creates a SCA component which invokes a create operation to the PeopleSoft adapter. The adapter is represented as PeopleSoft outbound interface. The SCA component sends the information to the outbound interface in the form of business object. The outbound interface invokes the PeopleSoft Component Interface to create the customer record in PeopleSoft Enterprise server. The following figure represents this scenario: This scenario has two steps: 1. Send the request to PeopleSoft Enterprise server for creating a record by using PeopleSoft adapter. In this case, a customer whose customer ID is will be created. 2. After creating the record, the adapter gets the response from PeopleSoft Enterprise server and converts it to a business object which can be understood easily by the SCA component. In the SCA component, users can use response business object for further processing. Configuring the adapter for outbound processing Run the New External Service wizard to specify business objects, services, and configuration to be used in this tutorial. To generate the business objects and related artifacts, perform the following steps:

26 1. Go to the Business Integration perspective and select File->New->External Service. Figure 14: New External Service

27 2. In the Select the Service Type of Registry window, select Adapters-> PeopleSoft and click Next. Figure 15: Select the Service Type of Registry

28 3. In the Select an Adapter window, select IBM WebSphere Adapter for PeopleSoft Enterprise (IBM ) -> CWYES_PeopleSoft, and click Next. Figure 16: Select an Adapter

29 4. In the Locate the Required Files and Libraries window, use Browse to specify the location of psjoa.jar and PSFTCI.jar files and click Next. Figure 17: Locate the Required Files and Libraries

30 5. In the Select the Processing Direction window, select Outbound and click Next. Figure 18: Select the Processing Direction

31 6. In the Specify the Discovery Properties window, specify the connection properties for the external service wizard and click Next. Figure 19: Specify the Discovery Properties

32 7. In the Find Objects in the Enterprise System window, select WBI_CUSTOMER_COMP_INTERFACE and add it to the Selected Objects list. Click Next. Figure 20: Selected Objects

33 8. In the Specify Composite Properties window, accept the default settings and click Next. Figure 21: Specify Composite Properties

34 9. In the Specify the Service Generation and Deployment Properties window, select Using security properties from the managed connection factory and click Next. Figure 22: Specify the Service Generation and Deployment Properties

35 10. In the Specify the Location Properties window click New. Figure 23: Specify the Location Properties

36 11. In the Select a Business Integration Project Type window, select Module and click Next. Figure 24: Select a Business Integration Project Type

37 12. In the Create a Module window, type TestOutbound in the Module Name field and click Finish. Figure 25: Create a Module

38 13. Go back to the Specify the Location Properties window and click Finish. Figure 26: Specify the Location Properties 14. Go back to the Business Integration perspective and select File ->Save All to save the changes. Deploying the module to the test environment The result of running the external service wizard is an SCA module that contains an EIS import or export. Install this SCA module in IBM Integration Designer integration test client. 1. Add the module you created earlier to the server using the server panel in IBM Integration Designer.

39 In the Servers tab, right-click on the IBM Process Server v7.5, select Add and Remove Projects. Figure 27: Add and Remove Projects

40 2. Add the SCA module to the server. In the Add and Remove window, click Add to add TestOutboundApp project into the Configured projects list and click Finish. Figure 28: Add and Remove Projects Testing the assembled adapter application Test the assembled adapter application using the IBM Integration Designer integration test client: 1. Select the service you want to test, right-click on TestOutbound module and select Test -> Test Module.

41 Figure 29: Open Test Module 2. Populate the following values for input business objects, as shown in the following screen capture. Specify the input data as the following table shows: Property Name Component Interface Operation verb Property Value PeopleSoftOutboundInterface PeopleSoftOutboundInterface createwbicustomercompinterface Create WbiCustomerId WbiCustomerFname WbiCustomerLname Charlie Lee WbiCustomerDob

42 Figure 30: Specify input data 3. Run the service. Click Continue to run the service. Figure 31: Continue to Run

43 4. In the Select Deployment Location window, select the server instance you want to deploy the project to and click Finish. Figure 32: Select Deployment Location

44 5. Check the output of the service and check the data in the EIS to ensure it matches the expected values. Figure 33: Invoke Result Clearing the sample content Return the data to its original state. Remove the module created earlier from the IBM Process Server. Right-click on the server, and then select Add and remove projects. Choose the module and Click on Remove and then click Finish. Nothing is required to clean up after this scenario.

45

46 Chapter 4. Scenario2 : Receiving events from PeopleSoft Enterprise application (inbound processing) In this scenario, when a new customer record is created in PeopleSoft Enterprise server, the event is generated and recorded. Later, the event is polled by the adapter and transformed into business object before delivering to the subscribed SCA component. The following figure represents this scenario: 1. User adds a new customer record in PeopleSoft Enterprise server. The PeopleSoft Enterprise server will generate the corresponding event. 2. The adapter will poll for events from PeopleSoft Enterprise server periodically. The event is captured in the event table and adapter fetches it from the server. 3. Finally, the adapter will convert the event to a business object and send it to the destination SCA component. Configuring the adapter for inbound processing Run the New External Service wizard to specify business objects, services, and configuration to be used in this tutorial. To generate the business objects and related artifacts, perform the following steps:

47 1. Go to the Business Integration perspective and select File->New->External Service. Figure 34: New External Service

48 2. In the Select the Service Type of Registry window, select Adapters-> PeopleSoft and click Next. Figure 35: Select the Service Type of Registry

49 3. In the Select an Adapter window, select IBM WebSphere Adapter for PeopleSoft Enterprise (IBM ) -> CWYES_PeopleSoft, and click Next. Figure 36: Select an Adapter

50 4. In the Locate the Required Files and Libraries window, use Browse to specify the location of psjoa.jar and PSFTCI.jar files and click Next. Figure 37: Locate the Required Files and Libraries

51 5. In the Select the Processing Direction window, select Inbound and click Next. Figure 38: Select the Processing Direction

52 6. In the Specify the Discovery Properties window, specify the connection properties for the external service wizard and click Next. Figure 39: Specify the Discovery Properties

53 7. In the Find Objects in the Enterprise System window, select WBI_CUSTOMER_COMP_INTERFACE and add it to the Selected Objects list. Click Next. Figure 40: Selected Objects

54 8. In the Specify Composite Properties window, accept the default settings and click Next. Figure 41: Specify Composite Properties

55 9. In the Specify the Service Generation and Deployment Properties window, select Using security properties from the managed connection factory and click Next. Figure 42: Specify the Service Generation and Deployment Properties 10. In the Specify the Location Properties window click New.

56 Figure 43: Specify the Location Properties

57 11. In the Select a Business Integration Project Type window, select Module and click Next. Figure 44: Select a Business Integration Project Type

58 12. In the Create a Module window, type TestOutbound in the Module Name field and click Finish. Figure 45: Create a Module

59 13. Go back to the Specify the Location Properties window and click Finish. Figure 46: Specify the Location Properties 14. Go back to Business Integration perspective and drag the Java Component to the Assembly Diagram. Figure 47: Java Component Added

60 15. Add wire between PeopleSoftInboundInterface and Java Component1. Figure 48: Component Wired to Interface 16. Select File->Save All to save the changes Deploying the module to the test environment The result of running the external service wizard is an SCA module that contains an EIS import or export. Install this SCA module in IBM Integration Designer integration test client. 1. Add the module you created earlier to the server using the server panel in IBM Integration Designer. In the Servers tab, right-click on the IBM Process Server v7.5, select Add and Remove Projects. Figure 49: Add and Remove Projects

61 2. Add the SCA module to the server. In the Add and Remove window, click Add to add TestInboundApp project into the Configured projects list and click Finish. Figure 50: Add and Remove Projects Testing the assembled adapter application Test the assembled adapter application using the IBM Integration Designer integration test client: 1. Attach the integration test client to the EIS export.

62 a. In IBM Integration Designer, right-click on project TestInbound and select Test- >Attach. Figure 51: Open Test Attach b. Switch to Configurations tab and click Add. Figure 52: Add Test configuration

63 c. Select Component and Reference Emulator and click Next. Figure 53: Create new Emulator

64 d. Select Module TestInbound and click Next. Figure 54: Select a Module

65 e. Select Components and click the check box of Component1. Click Finish. Figure 55: Add Component and Reference Emulator

66 f. Switch back to Events tab and click Continue. Figure 56: Continue to Run

67 g. In the Select Deployment Location window, select the server instance you want to deploy the project to and click Finish. Figure 57: Select Deployment Location 2. Enter data in the EIS to trigger an inbound event. a. In the PeopleSoft application designer, open Component Interface WBI_CUSTOMER_COMP_INTERFACE and select Tools->Test Component Interface.

68 b. Specify WBI_CUSTOMER_ID to and click Create New.

69 c. Specify the property values as the following screen capture shows, then rightclick on WBI_CUSTOMER_COMP_INTERFACE and select Save.

70 d. Click OK, when the Save() results dialog prompts.

71 3. Check the values in the object published to the IBM Integration Designer integration test client. Figure 58: Attach result Clearing the sample content Return the data to its original state. Remove the module created earlier from the IBM Process Server. Right-click on the server, and then select Add and remove projects. Choose the module and Click on Remove and then click Finish. Nothing is required to clean up after this scenario.

72

73 Chapter 5. Scenario3 : Effective Sequence number is not required for data insert (outbound processing) wherein this scenario, a user wants to insert a new address record under an existing customer record ignoring the effective sequence number. By using different ASI setting, the new address record can be inserted in either the highest or the lowest index position. While creating artifacts using PeopleSoft Adapter, users need to set related ASI setting as explained below in section 5.2. Then the user creates a SCA component which invokes two operations - create and update using PeopleSoft Adapter. Create operation is used to create a customer record in PeopleSoft Enterprise server. Then, the same record is used for update operation. The update operation updates the record by inserting a new address record under the customer record. The response object returned at the end contains the new address record inserted ignoring the effective sequence number. The following represents this scenario: This scenario has four steps: 1. Send the request to PeopleSoft Enterprise server for creating a record with multiple children. In this case, a customer with multiple address information will be created. 2. After creating the customer record, the adapter gets the response from PeopleSoft Enterprise server and converts it to a business object. 3. Send another request to PeopleSoft Enterprise server for updating an existing record with children. In this case, a new address record will be inserted under an existing customer record. 4. The adapter gets the response business object again. From the response, you can identify the new address added in different index position according to the ASI setting.

74 Configuring the adapter for outbound processing Run the New External Service wizard to specify business objects, services, and configuration to be used in this tutorial. To generate the business objects and related artifacts, first perform steps in chapter 3. Then perform the following steps to set the related ASI to ignore effective sequence number, including IgnoreEffectiveSequence, EffectiveDate, EffectiveSequence, KeepRelations, InsAtOldestEffDtPos. For details of the usage of these ASIs, refer to the PeopleSoft user guide. 1. In Business Integration perspective, expand Data Types under TestOutbound module and click WbiCustomerCompInterface. In the right panel, right-click Wbiaddress->Properties View. Figure 59: Wbiaddress Properties

75 2. In Properties->Application Info tab, right-click PeopleSoftAttributeTypeMetadata- >New->KeepRelations. Figure 60: New KeepRelations 3. In TestOutbound > Data Types module click Wbiaddress. In the right panel, rightclick Wbiaddress -> Properties View Figure 61: WbiAddress properties

76 4. In Properties->Application Info tab, right-click PeopleSoftBusinessObjectTypeMetadata->New->IgnoreEffectiveSequence and PeopleSoftBusinessObjectTypeMetadata->New->InsAtOldestEffDtPos Figure 62: New IgnoreEffectiveSequence Figure 63: New InsAtOldestEffDtPos

77 5. In WbiAddress tab, right-click Effdt -> Properties View Figure 64: Effdt Properties 6. In Properties>Application Info tab, right-click PeopleSoftAttributeTypeMetadata>New>EffectiveDate Figure 65: New EffectiveDate

78 7. In WbiAddress tab, right-click WbiAddressId > Properties View Figure 66: Addressid Properties 8. In Properties >Application Info tab, right-click PeopleSoftAttributeTypeMetadata >New >EffectiveSequence. Figure 67: New EffectiveSequence

79 9. Select File >Save All to save the changes. Deploying the module to the test environment Perform step 1 and step 2 in section Deploying the module to the test environment in Chapter 3. Testing the assembled adapter application Test the assembled adapter application using the IBM Integration Designer integration test client: 1. Select the service you want to test, right-click TestOutbound module and select Test -> Test Module. Figure 68: Open Test Module 2. Populate the following values for input business objects, as shown in the following screen capture. Specify the input data as shown in the following table: Property Name Property Value Component PeopleSoftOutboundInterface Interface PeopleSoftOutboundInterface

80 Operation createwbicustomercompinterface WbiCustomerId WbiCustomerFname Charlie WbiCustomerLname Lee WbiAddress[0] Effdt WbiAddressId 1 WbiAddressLine1 Line1 WbiAddress[1] Effdt WbiAddressId 2 WbiAddressLine1 Line2 WbiAddress[2] Effdt WbiAddressId 3 WbiAddressLine1 Line3

81 Figure 69: Specify input data 3. Run the service. Click Continue to run the service. Figure 70: Continue to run

82 4. In the Select Deployment Location window, select the server instance you want to deploy the project to and click Finish. Figure 71: Select Deployment Location

83 5. Check the output of the service and check the data in the EIS to ensure it matches the expected values. Figure 72: Invoke result 6. Populate the following values for input business objects, as shown in the following screen capture. Specify the input data as shown in the following table : Property Name Component Interface Operation Property Value PeopleSoftOutboundInterface PeopleSoftOutboundInterface updatewbicustomercompinterface

84 WbiCustomerId WbiCustomerFname WbiCustomerLname WbiAddress[0] Effdt WbiAddressId 4 WbiAddressLine1 Line4 GetHistoryItems EditHistoryItems True True 7. Run the service. Click Continue to run the service.

85 Figure 73: input values 8. Check the output of the service and check the data in the EIS to see the child data is added at the highest(oldest) index Figure 74: final result If you add InsAtCurrentEffDtPos ASI instead of InsAtOldestEffDtPos, the child data will be added at the lowest (current) index in the previous step. Clearing the sample content

86 Return the data to its original state. Remove the module created earlier from the IBM Process Server. Right-click on the server, and then select Add and remove projects. Choose the module and Click on Remove and then click Finish. Nothing is required to clean up after this scenario.

87

88 Chapter 6. Troubleshooting If you encounter any troubles while running the above tutorials, review the following tips for resolving some common problems. 6.1 Improve the IBM Process Server trace level If you are not able to determine the cause of the error based on the exception message in the Component Test Client, you can perform the following steps to improve the IBM Process Server trace level to get more detailed adapter trace. a) Log on to IBM Process Server administrative console b) Go to Troubleshooting > Logs and Trace c) Select server1 d) Select Change Log Detail Levels e) In the Runtime tab, add setting string *=info: com.ibm.j2ca.*=all f) Click OK The trace file can be located at: <Profile Home>\logs\server1\trace.log 6.2 Connection issues with PeopleSoft Enterprise application If the Adapter meets any problems when it tries to connect to the PeopleSoft Enterprise application, you can check the following things: a) Ensure the connection properties are correct, such as host name, port number, username, and password. b) Ensure the version of psjoa.jar that the Adapter uses is exactly the same as the version of the PeopleTools that the Adapter tries to connect to. For example, the Adapter will fail to connect to PeopleSoft Enterprise application if the psjoa.jar version is 8.48 but the PeopleTools version is 8.49.

89 Chapter 7. Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication.

90 IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Department 2Z4A/SOM1 294 Route 100 Somers, NY U.S.A. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non- IBM products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. If you are viewing this information softcopy, the photographs and color illustrations may not appear. Programming interface information Programming interface information, if provided, is intended to help you create application software using this program.

91 General-use programming interfaces allow you to write application software that obtains the services of this program's tools. However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software. Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol ( or ), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A complete and current list of IBM trademarks is available on the Web at Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Screens are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.* UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. This product includes software developed by the Eclipse Project (