uCosminexus Service Platform, Reception and Adapter Definition Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
(1) Acquiring a queue name
When the service component is MDB (DB queue), you must acquire the queue name of the service component from the developer. You use this queue name when defining a service adapter.
(2) Service component message format
In the case of MDB (DB queue), you must create and set up a message format for the service component.
For details about how to create a service component message format, see 4.3.4 Creating a Service Component Message (for MDB (WS-R or Database Queue)) in the manual Service Platform Basic Development Guide.
(3) Data transformation
If the message format of service requester and message format of service component invoked by the service adapter is different, data transformation is required.
For performing data transformation, specify the message entered from the service requester in the standard message using the Service Adapter Definition screen, and then define data transformation in the Data Transformation Definition screen.
For details about data transformation, see 6. Defining Data Transformation in the manual Service Platform Basic Development Guide.
To define an adapter for MDB (DB queue):
- Open the Service Adapter Definition screen.
For details about how to open the Service Adapter Definition screen, see 3.3.1(4) Displaying the service adapter settings screen.
- Edit Service name, Service ID, and The number of the maximum instances in the HCSC component control information as and when required.
- Specify an address for the HCSC component control information.
For Address, enter the registration-destination queue name for using a shared queue. For details about a registration-destination queue name for using a shared queue, see the manual Cosminexus Application Server Cosminexus Reliable Messaging.
- From the Operation drop-down list of the HCSC component control information, choose the operation to be edited.
- Check the contents displayed in the operation information.
- Check the Convert a system exception into a fault message check box of service component control information as and when required.
- Perform the following operations for request messages
- When specifying a message format
- Perform steps 8. to 11., and then proceed to step 12.
- When not specifying a message format
- Proceed to step 12.
- Choose the Use check box for the message.
- Specify Format ID for the message.
- Click the Browse button for the message, and specify a message format in Message format.
Note that for specifying a message format that references an external XML schema, make sure that you specify a file for the root schema. The external XML schema file referenced from the root schema is automatically imported.
For details about message formats that can be specified, see 2.6.5 Scoping of XML schema in the manual Service Platform Basic Development Guide.
- Click the Display button for the message.
The message format is displayed. Check the specified message format as and when required.
- Specify Format ID for the service component message.
- Click the Browse button for the service component message, and specify a service component message format in Message format.
- Click the Display button for the service component message.
The service component message format is displayed. Check the specified service component message format as and when required.
- Perform the following operations.
- When the Use check box of the standard message is checked
- Execute steps 16. to 18. and then proceed to 19.
- When the Use check box of the standard message is not checked
- Proceed to step 19.
- Enter the file name of the Data transformation definition.
- Click the Edit button.
The Data Transformation Definition screen is displayed.
Note that when defining the message format initially, the Choose root element dialog box appears.
If the message format is changed, a dialog box for confirming whether to reflect the change of message format is displayed. For details about the procedure of the changed message format, see 6.3.2 Procedure for defining changed message formats in the manual Service Platform Basic Development Guide.
- Map the contents of the standard message and the service component message.
- Check the definition contents, and, on the Eclipse File menu, choose Save to save the defined contents.
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.