Setting deployment properties and generating the service

To generate the module, which is the artifact that is deployed on IBM® Business Process Manager or WebSphere® Enterprise Service Bus, you create the module, and associate the adapter with the module.

1. Optional: To change the default operation name, use the following procedure.
   1. Click Edit Operations.
   2. In the Edit Operation Names window, select the operation you want to edit, then click Edit.
   3. In the Add/Edit properties window, type a new operation name and optional description, then click Finish.
2. Indicate whether you will use an authentication alias (instead of typing a user ID and password) to establish a connection to the JD Edwards EnterpriseOne server:
   • To specify an authentication alias, leave Specify a Java Authentication and Authorization Services (JAAS) alias security credential selected. Then, in the J2C Authentication Data Entry field, enter the name you specified in the Security section of the administrative console.
   • If you are not going to use an authentication alias, clear Specify a Java Authentication and Authorization Services (JAAS) alias security credential.
3. Select With module for use by single application to embed the adapter files in a module that is deployed to the application server, or select On server for use by multiple applications to install the adapter files as a stand-alone adapter.
   • With module for use by single application: With the adapter files embedded in the module, you can deploy the module to any application server. Use an embedded adapter when you have a single module using the adapter or if multiple modules need to run different versions of the adapter. Using an embedded adapter enables you to upgrade the adapter in a single module without the risk of destabilizing other modules by changing their adapter version.
   • On server for use by multiple applications: If you do not include the adapter files in a module, you must install them as a stand-alone adapter on each application server where you want to run the module. Use a stand-alone adapter when multiple modules can use the same version of the adapter and you want to administer the adapter in a central location. A stand-alone adapter can also reduce the resources required by running a single adapter instance for multiple modules.
4. If you selected On server for use by multiple applications in the previous step, the Connection properties list becomes active. Make one of the following selections:
   • Select Specify connection properties if you want to provide configuration information now. Then continue with step 5.
   • Select Use predefined connection properties if you want to use a connection factory configuration that already exists.

     If you decide to use predefined connection properties, you must ensure that your resource adapter name matches the name of the installed adapter, because this is how the adapter instance is associated with these properties. If you want to change the resource adapter name in the import or export, use the assembly editor in IBM Integration Designer to change the value in the import or export.

     When you select Use predefined connection properties, the JNDI Lookup Name field is displayed in place of the properties.

     1. Type a value for JNDI Lookup Name.
     2. Click Next.
     3. Go to step 9.

5. In the Connection properties section, set or change any connection properties that apply to your configuration.
   Figure 1. Service Generation and Deployment Configuration window, showing the Connection properties

   

   See Managed connection factory properties for more information about these properties.

   Properties marked with an asterisk (*) are required.

6. To set additional properties, click Advanced and expand the sections.
   • Process illegal XML characters
     1. From the Illegal XML character processing drop-down list, select one of the options that correspond to your requirement:
        • Do not validate illegal XML characters, if you want to work with the default adapter behavior.
        • Throw exception if contents in the BO contains illegal XML characters, if you want to proceed after you get an exception message, and log the illegal XML characters in the trace file, at runtime.
        • Discard all illegal XML characters and related logs, if you want the adapter to discard the illegal XML characters, and log the characters in the trace file, at runtime.
     Figure 2. Processing methods for illegal XML characters

     
   • Logging and tracing
     • If you have multiple instances of the adapter, set Adapter ID to a value that is unique for this instance.
7. Click Next.
8. Create a new module.
   1. In the Specify the Location Properties window, click New in the Module field.
   2. In the Select a Business Integration Project Type window, select Create a module project or Create a mediation module project, then click Next.
   3. In the Create a Module window, type a name for the module.
      Note: As you type the name, it is added to the workplace directory specified in the Location field.

      This is the default location. If you want to specify a different location, remove the check from Use default location and type a new location, or click Browse and select the location.

   4. Specify whether you want to open the module in the assembly diagram (for module projects) or whether you want to create a mediation flow component (for mediation module projects). By default, these choices are selected.
   5. Click Finish. The new module is created. When the creation process is finished, the New Module window closes, and the new module appears in the Module list in the Service Location Properties window.
9. In the Specify the Location Properties window, you can specify deployment properties for the new module by performing the following steps.
   1. If you want to change the default namespace, clear the Use Default Namespace check box and type a new path in the Namespace field.
   2. Specify the folder within the module where the service description should be saved by typing a name in the Folder field or by browsing for a folder.
   3. Change the name of the interface.

      The default name is JDEOutboundInterface. You can change it to a more descriptive title if you prefer.

   4. If you want to save the business objects so that they can be used by another application, click Save business objects to a library, then select a library from the list, or click New to create a new library.
   5. Type a description of the module.
10. Click Finish.