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 queue information and message type
When the service component is MDB (WS-R), you must acquire both the queue information and service type of the service component from the developer. You use the acquired information when defining a service adapter.
The following types of information must be acquired:
- Queue name
- Destination address (if network communication between an adapter and a service component is used)
- User name and password for the basic authentication (if network communication between an adapter and a service component is used, and the basic authentication is used)
- Message type
(2) Service component message format
In the case of MDB (WS-R), you need to create and set up a message format of 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 DB 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.
(4) Specifying invocation
You can specify the method to invoke a service component to be used. You can choose either remote or local invocation. If you choose remote invocation, specify the number of maximum messages. Also, set a basic authentication as required.
(5) Specifying the maximum message count
If you specify remote invocation as a service component invocation method, you can specify the number of messages that can be processed at the same time, with a number changed from the initial value. You can set a value in a range from 1 to 65535.
(6) Specifying the basic authentication
If you specify remote invocation as a service component invocation method, and when user authentication is required in MDB (WS-R) message transfer, the basic authentication (user name and password) settings will be needed.
To define an adapter for MDB (WS-R):
- 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, specify the queue name acquired in 3.3.3(1) Acquiring queue information and message type.
- 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
- Execute steps 7 to 10, and then proceed to step 11.
- When not specifying a message format
- Proceed to step 11.
- 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 Application Scopes 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 15. to 17. and then proceed to step 18.
- When the Use check box of the standard message is not checked
- Proceed to step 18.
- 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.
- Click the Service adapter definition (details) tab.
- From the JMS Message Type drop-down list, choose a JMS message type.
- Choose the service component invocation method in Invocation Setting.
- When you choose the Remote Invocation radio button
- Proceed to step 21.
- When you choose the Local Invocation radio button
- Proceed to step 29.
- In The number of the maximum messages, specify the number of messages the service component can send.
- In Destination URL, enter the destination address acquired in 3.3.3(1) Acquiring queue information and message type.
- Depending on whether the service component requires user authentication, perform either of the following operations:
- When user authentication is required
- Execute steps 24 to 26, and then proceed to step 27.
- When user authentication is not required
- Proceed to step 27.
- Choose the Use check box for the basic authentication.
- In the user name and password columns, enter a user name and password necessary for the basic authentication.
- In the Password (Re-enter) column, enter the same password as that entered in the password column.
- Enter the transmit queue creation destination RD area as required.
- Choose the Sequence guarantee check box as and when required.
- 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.