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 > IBM i > Configure the module for deployment > Configure the module for outbound processing > Access messages using simple or keyed IBM i data queue

Setting global properties for operations

To configure the business object, you specify information about the object (such as the operation associated with the object). For data queue, the operation names are PutQueue and GetQueue.

The Specify Composite Properties window displays the operation name for selected business objects. Configure PutQueue and GetQueue operations for the Data queue.


Procedure

  1. The Specify Composite Properties window for a Data queue business object displays the PutQueue and GetQueue operations.

    Figure 1. Specify Composite Properties window

  2. Based on your requirement, use Add to add any of these operations or Remove to remove any of these operations. If you choose to remove any of these operations, the removed operation is made available in the Add operation for you to add back.

  3. In the Business object namespace field, either accept the default namespace or type the full name of another namespace. The namespace is prepended to the business object name to keep the business object schemas logically separated. For more information about this property, see the reference topic devoted to managed connection factory properties in this documentation.

  4. Optional: In the Folder, type the relative path to the folder where the generated business objects are to be stored.

  5. Optional: In the Data encoding field, click the Select button to specify the type of character encoding to use.

  6. Select the Message content as binary check box if you use the message in binary format for the PutQueue and GetQueue operations. Selecting this option results in the business objects to put and get messages from the non keyed or keyed data queue in the binary format.

    For Keyed Data queue, with message content in binary format, the message key length must be same as the length supported by the Keyed Data queue.

  7. Click Next.


Results

You have provided information that applies to all business objects in the module.


What to do next

Continue working in the wizard. The next step is to specify deployment information to use at run time and information for saving the service as a module.

Access messages using simple or keyed IBM i data queue