Creating an import using PeopleSoft

Using the enterprise service discovery wizard, you create an import based on a PeopleSoft application. You are taken step by step through the generation of the import.

Prerequisite: You should have access to a PeopleSoft server. In this example, a module already existed though you could alternately create the module in the final page of the wizard.
You will follow the pattern you see in these steps when you create an import component for Enterprise Resource Planning (ERP) and database systems as well as systems using flat files.
  1. Right-click your module and from the pop-up menu select New > Enterprise Service Discovery. The Select an Enterprise Service Resource Adapter page opens. If you have not imported the resource adapter into your workspace, click Import Resource Adapter. Add the PeopleSoft resource adapter by specifying its path. At this time, you may also select a particular name for the connector project, a specific target server, and specify that your selection be added to a particular EAR project. Deploying or not deploying the resource adapter in the module discusses why you might want to add and later deploy your resource adapter with a module. Click Finish. If asked to change perspectives, select No.
    Importing the resource adapter
    After importing the resource adapter, you will also need to import some third party additional files to your resource adapter project and add them to the classpath of the resource adapter. For example, in the case of PeopleSoft, we added a communication library and some generated libraries that contained the top-level business objects.
  2. With your resource adapter imported into your workspace, return to the Select an Enterprise Service Resource Adapter page, select your resource adapter and click Next. You may occasionally need to wait a minute as your workspace is rebuilding in the background following the import. If you do not see your resource adapter, close the wizard, wait until the workspace has rebuilt, and then return to the enterprise service discovery wizard.
    Selecting the resource adapter
  3. The Configure Settings for Discovery Agent page opens. Complete the fields. Hover help can be found on the fields and content assistance will help you if you have entered these values before. In our PeopleSoft example, you will need to specify the component interface JAR for the resource adapter, the userid and password for the server, the server name and its port number. Were you working with another resource adapter that complied with the Enterprise Metadata Discovery specification, you would of course have different connection properties. You may optionally specify bidirectional properties if the server orientation is different from left-to-right. Show Advanced adds additional field selections for logging level and the location of the log file. Click Next.
    Initial properties page to connect to server
  4. The Find and Discover Enterprise Services page opens. Run Query queries the metadata of an EIS system and returns the objects it finds. In this case, the query applies to a PeopleSoft system. Click it to query PeopleSoft system. The business objects at the server are returned and placed in the Objects discovered by query pane. A variety of objects may be listed such as data structures and Remote Procedure Calls (RPC). Importing and selecting these objects determines the artifacts that will be represented in the component. Select the objects you want and click Add to build the collection of information you want returned. As you build your query, you may be prompted for whether you want lower level information available to you as specified in the Configuration Parameters dialog box. You may also use a filter when building a query. The button is enabled if you can use it. When completed your selected objects will be listed in the Objects to be imported pane. Click Next.
    Defining the query
  5. The Configure Objects wizard page opens. As in other pages, the properties displayed are determined by the resource adapter complying to the Enterprise Metadata Discovery specification. The following properties are displayed in the case of the PeopleSoft resource adapter. The Service Type field defaults to Outbound. Outbound is the setting required for an import component. Leave it set to outbound. The NameSpace field defaults to the namespace of the resource adapter, in this case the IBM® PeopleSoft resource adapter. You may rename the value to something more familiar to you. The Service Functions pane lists the functions available. You may add or delete these functions as you choose to refine the operations you can perform on the business objects you selected on the previous page of the wizard. In the BO Location field, enter the folder where you would like the business objects created to be placed. It is recommended that you place the business objects in a folder as otherwise it will be difficult to manage all the objects that will appear in the root. This folder and others that you can create will appear in the Physical Resources view. Click Next.
    Specifying the selection properties
  6. The Generate Artifacts page opens. You can change the module or define a new one for your import component. You can add a folder to contain your generated service files. You must name your service. In our case, we named it PurchaseOrder, as that is the type of information that would be returned. At this point you can deploy the resource adapter with the module if you wish. Deploying or not deploying the resource adapter in the module discusses why you might want to deploy your resource adapter. Note that some resource adapters must be deployed with the module. The PeopleSoft resource adapter is one that must be deployed with the module. All IBM WebSphere® Business Integration Adapters must be deployed with the module. The resource adapter name must match what is expected at the server. You can choose between two types of managed connections. The differences are discussed in Using connection properties specified on a server or using the discovered ones. If you choose Use connection properties specified on server, specify the JNDI name and J2C Authentication Data (the JAAS alias name). Should you choose Use discovered connection properties, you must fill in appropriate connection information such as userid, password, machine name, port, and national language. You may also add the J2C Authentication Data (the JAAS alias name) if one is specified at the server.
    Properties for import component
    You may also edit the operation names. You might edit them for the same reason that you named the service; the names that appear are picked from the names found at the server and may not be relevant to your service. For example, you might rename createPSOFTPoCompInterface to simply create.
    Editing operation names
    When you have completed filling in the values of the fields you want, click Finish
  7. Your service is created and added to the module. Select your business object beneath Data Types. The relationship of this business object to others appears in the references view. Right-click a business object. From the pop-up menu select Open With > Business Object Editor. It opens in the editor. Selecting an item from the business object results in seeing lower level information in the properties view. Business objects from data structures provides more details on the properties view of business objects created by the wizard.
  8. Right-click your interface beneath Interfaces. From the pop-up menu, select Open With > Interface Editor. The interface opens in the interface editor. The relationship between the interface and the service is shown in the references view.
  9. Right-click the name of service you created, from the pop-up menu select Open. The assembly editor opens with an import component icon. EIS indicates that it is created from an application on an EIS system.
    Import component
  10. Select the import component. In the properties view, more details are provided. You can add or change the names and description provided. Select Details. More details are specified including the interface name, preferred interaction style - synchronous, asynchronous, or any - and the operations. The Qualifiers tab may let you add a qualifier to the interface. A qualifier is a quality of service (QoS) addition you may be able to add to the interface; for example, a security level. However, it is determined by the creation of the service whether one or more are present and if you are permitted to add any yourself. The Event Monitor tab lets you monitor events at run time using the Common Event Infrastructure (CEI) property. For example, you might want to monitor how many times a transaction involving this service occurred. Event monitoring can be helpful in fine tuning an application. For example, if you monitored the transactions occurring it might point to a bottleneck at run time.
    Properties of the interface
  11. Select the Binding tab. The type of binding, the resource adapter, the managed connection factory class, data type and binding description are listed. The Connection section contains the managed connection factory class and its properties, the ConnectionSpec class and its properties, the authentication properties, and the administration connection properties. The Resource Adapter section contains the resource adapter name, the resource adapter class and the resource adapter bean properties.. The Method Bindings section contains the interaction information, which in our example consists of database type operations such as retrieving and updating data. Binding information fields are discussed in detail in Data bindings, function selector and generated properties.
  12. If you wish to test your component using the WebSphere test environment, see WebSphere test environment setup.
The PeopleSoft import component has been generated and you have looked at its features and properties. Compare it with creating an export component from the same PeopleSoft server.
Related concepts
Relationship of imports and exports to inbound and outbound events
Related tasks
Creating an export using PeopleSoft
Creating an import using CICS
Creating an import using IMS
Creating an import to retrieve undelivered IMS transaction output

Feedback
(C) Copyright IBM Corporation 2005, 2006. All Rights Reserved.