IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > JD Edwards EnterpriseOne > Configure the module for deployment > Configure the module for inbound processing

Setting deployment properties and generating the service

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

Make sure you have configured the real-time event. The Specify the Service Generation and Deployment Properties window should be displayed.

Generate the module, which includes the adapter and configured business object. The module is the artifact you deploy on the server.

To generate the module, use the following procedure.


Procedure

  1. 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.

      Figure 1. Specify the Service Generation and Deployment Properties window, showing the Connection properties section

  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, 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.

    See Setting connection properties for the external service wizard for more information about these properties.

    Properties marked with an asterisk (*) are required.

  6. To set additional properties, click Advanced and expand the following sections:

    • Event polling configuration
    • Event delivery configuration

    • Process illegal XML characters

    • Logging and tracing properties

    The following figure shows the advanced property sections on the Service Generation and Deployment Configuration window.

    Figure 2. The Specify the Service Generation and Deployment Properties window, showing the advanced property sections after clicking the Advanced button

    See Activation specification properties and Resource adapter properties for more information about these optional properties.

    • Event polling configuration

      1. In Interval between polling periods, type the number of milliseconds that the adapter waits between polling periods. See Interval between polling periods (PollPeriod).

      2. In Maximum events in polling period, type the number of events to deliver in each polling period. See Maximum events in polling period (PollQuantity).

      3. In Retry interval if connection fails, type the number of milliseconds to wait before trying to connect after a connection failure during polling. See Time between retries in case of system connection failure (RetryInterval).

      4. In Number of times to retry the system connection, type the number of times to retry the connection before reporting a polling error. See Maximum number of retries in case of system connection failure (RetryLimit).

      5. If you want the adapter to stop if polling errors occur, select Stop the adapter when an error is encountered while polling.

        If you do not select this option, the adapter logs an exception but continues to run. See Stop the adapter when an error is encountered while polling (StopPollingOnError).

      6. You can select Retry EIS connection on startup if you want the adapter to retry an inbound connection that was not made to the JDE application when starting. Only communication failures to the JDE application are considered. See Retry EIS connection on startup (RetryConnectionOnStartup).
    • Event delivery configuration

      1. In Type of delivery, select the delivery method. The methods are described in Delivery type (DeliveryType).

      2. If you want to ensure that events are delivered only once and to only one export, select Ensure once-only delivery. This option might reduce performance but does not result in duplicate or missing event delivery. See Ensure once-only event delivery (AssuredOnceDelivery).
      3. Under Number of connections for event delivery, specify the minimum and maximum number of connections to use to deliver events. See Minimum connections (MinimumConnections) and Maximum connections (MaximumConnections).

    • 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 3. 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.

      • If you want to mask sensitive information in log and trace files (for example, if you want to avoid making customer information visible in these files) expand Logging and tracing, provide an ID for the adapter instance (or accept the default value), and select Disguise user data as "XXX" in log and trace files.

  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.

      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.

    • Calendar based scheduling

      Select the calendar based scheduling option to create calendar based polling for inbound activities.

      You can schedule your business activities, when you create a new calendar in IBM Integration Designer. The option of working with the calendar based scheduling feature is only possible with IBM Integration Designer as the tooling environment. The following figure helps you to schedule a calendar polling option.

      Figure 4. Polling based on business calendar

      You can either select a blank calendar or create a new calendar for a module or library.

      When you select a blank calendar, you will not be able to set predefined time intervals. You have to define your time intervals. When you create a calendar using a predefined template, you can define time intervals for each template.

      • To select an existing calendar for a module or library, click Browse. In the Select a Business Calendar window, you can search for existing calendar files ( *cal) in the IBM Integration Designer workspace.

        1. In the Filter by name field, type the calendar name or name pattern. The calenders matching the pattern are displayed in the Matching business calendars area.

        2. Select a calendar and click OK to return to the external service wizard.

      • To create a new calendar entry for a module or library, click New. The Create a business calendar window is displayed.

        1. In the Module or library field, click Browse to select an existing calendar module or click New to create a module for the new calendar.

        2. In the Folder field, click Browse to select an existing folder or create a new folder for the calendar.

        3. In the Name field, enter a name for the new calendar.

          • To create a non template calendar, click Finish. Or

          • To generate the calendar based on a predefined template, click Next. In the Use a template window, select the Create a calendar using one of the templates check box and click Finish.

          The new business calendar is created and available in the Business Integration view. Once you complete the wizard, you can view or modify the calendar schedules in the Business Integration view using the Business Calendar Editor. You can modify the intervals and exceptions, or add new entries for these elements. For more details about working with business calendars, see Business calendars.

      You must deploy the Business Calendar module to the same IBM BPM or WebSphere Enterprise Service Bus instance, along with the inbound application. If you do not map these two connections to the same server instance, the inbound application using the business calendar will by default, poll as there is no calendar configured.

  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 JDEInboundInterface. 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.


Results

The new module is created, configured and saved to the Business Integration perspective of IBM Integration Designer.


What to do next

Export the module as an EAR file for deployment.

Configure the module for inbound processing