Step 3: Create an MFS J2C Java Bean based on the selected MFS source file

When you create an MFS SOA service, you must import operation(s) based on the selected MFS source files and specify the necessary configuration parameters, such as Message Output Descriptors (MOD) and publishing properties, such as JNDI name.

About this task

Operation names are created by appending "Run" to the Message Input Descriptor (MID) from the MFS source file.

Tip: In the following step, you must press the > button for each MFS source file that you selected.

This task begins on the Object Discovery and Selection page. To generate one or more MFS services based on the selected MFS source files you previously imported:

Object Discovery and Selection page

Procedure

  1. On the Object Discovery and Selection page, in the Objects discovered by query pane, select the operation that you want to create as a service. Click the > button to add the operation to the Objects to be imported pane. Click Next. The Configuration Parameters for your_object_name page opens.
    The configuration parameters setting page for the selected object.
    Important: Verify that the device type selected is the correct one for your MFS source file. You can pull down and chose other device types. The default device type might not be correct.
    You can add more MOD names, if needed:
    1. Click Add. The Add Value page opens.
      The Add Value page
    2. Select any additional MOD files, and click OK.
    Confirm the rest of the parameters on the Configuration Parameters page and click OK.
  2. Set the configuration parameters and click OK. If a MID name has no associated MOD name, DFSMO2 is the default MOD name of the MID. The Object Discovery and Selection page shows the chosen operation added into the Objects to be imported pane.
    The Object Discovery and Selection page shows the chosen operation added into the Objects to be Imported pane.
  3. Click Next. The Java Bean Creation and Deployment Configuration page opens.Java Bean Creation and Deployment Configuration page
  4. Click New to create a new project in which the J2C Java™ bean will be generated. Depending on the type of project you choose to create, fill in the required fields, such as the project name. Click Finish to create the project.
  5. Back to the Java Bean Creation and Deployment Configuration page, the project name is filled in.
  6. Enter the package name, interface name, implementation name, and JNDI lookup name.
    Important: You must use the same JNDI name that you will use in the WebSphere® Application Server Connection Factory.
  7. Determine the connection properties to use.
    Option Description
    Managed Connection (recommended)

    If you use the Managed Connection (recommended), WebSphere Application Server manages the connection, specified by the JNDI name, for you. The benefit of selecting Managed Connection is that you can change the connection information without affecting the generated application as long as the JNDI name stays the same.

    Non-managed connection

    If you use the Non-managed connection, Rational® Application Developer sets up the connection when you specify hostname, port number, and data store name.

    Managed Connection (recommended) and Non-managed connection

    If you check both choices, the Managed Connection is executed first. If the JNDI name cannot be found, the non-managed connection parameters is used.

    Tips:
    • You can ignore the Generate Command Bean option.
    • You can select the Click to launch J2C deployment wizard checkbox to immediately start the wizard.
  8. Click Finish.

Results

The J2C Java bean(s), input and output data binding files, as well as the XML schema file(s) are generated.

Feedback