This section describes how to use the iSeries ODA in Business Object Designer to generate business object definitions. For information on launching and using Business Object Designer, see IBM WebSphere Business Integration Adapters Business Object Development Guide.
You can start the iSeries ODA using one of the following scripts:
You select, configure, and run the iSeries ODA using Business Object Designer. Business Object Designer locates each ODA by the name specified in the AGENTNAME variable of each script or batch file.
Business Object Designer provides a wizard that guides you through the steps to generate a business object definition using the ODA.
You must first select the ODA agent.
Figure 15. Select Agent window
After you click Next on the Select Agent window, the Business Object Wizard - Step 2 of 6 - Configure Agent window opens.
Figure 16. Configure Agent window
The properties you set on this screen are described in Table 5. You can save all the values you enter on this screen to a profile. Instead of retyping the property data the next time you run the ODA, you simply select a profile from the drop-down menu and re-use the saved values. You can save multiple profiles, each with a different set of specified values.
Table 7. Configure Agent properties
Property name | Default value | Type | Description |
---|---|---|---|
iSeriesHostName |
| String | (required) The iSeries host machine name. |
iSeriesUserName |
| String | (required) The User name used to connect to the iSeries machine. |
iSeriesPassword |
| String | (required) The Password used for connecting to the iSeries machine. |
iSeriesFilePath | /QSYS.LIB/ | String | Absolute IFS path to the select source. |
iSeriesODAOption |
| String | The type of resource to access on iSeries. Currently there are 2 options: RPGMBR and DTAQ. Based on this selection, the source files are accessed to create corresponding business object definitions |
TraceFileName | None | String | The name of the trace message file. |
TraceLevel | 5 | Integer | (required) The tracing level (from 0 to 5) for the agent. |
MessageFile | None | String | (required) The name of the message file that contains all the messages displayed by the ODA. If you do not correctly specify the name of the message file, the ODA will run without messages. |
Use the New and Save buttons in the Profiles group box any time you want the ODA to create a new profile. When you use the ODA again, you can select an existing profile. Type the value of each property, as defined in Table 7.
Whenever any required field is left blank or during any error, (for example an invalid username), a pop up message is displayed with the corresponding error message.
The Business Object Wizard - Step 3 of 6 - Select Source window opens, as illustrated in Figure 17.
This screen lists either the *.MBR for RPG source files or *.DTAQ files for data queues, where users can select the names of those files. The file type is decided by the iSeriesODAOption Agent property. The IFS Directories are represented as expandable tree nodes while the source names (MBRs and DTAQ) are shown as leaf nodes. You can select more than one source (leaf nodes only) either in the same IFS directory or in different IFS directories. Use this screen to select any number of source files for which the ODA will generate business object definitions.
Figure 17. Select Source window
The Business Object Wizard - Step 4 of 6 - Confirm source nodes for business object definitions window opens. It shows the object(s) you selected.
Figure 18. Confirm source node window
Click Back to make changes or Next to confirm that the list is correct. The Business Object Wizard - Step 5 of 6 - Generating business objects... window opens with a message stating that the wizard is generating the business objects.
After you confirm your node sources, the iSeries ODA generates the business objects. The Business Object Wizard - Step 6 of 6 - Saving business object definitions... window opens.