Use this tab to define the business service that manages inbound and outbound native messages between CASP and the native application. In order for the native connector to communicate with the native application, the native application must be represented to CASP as an CASP business element. The business service you create using this tab contains the business element that represents the native application. In Figure 1, this is the Native Server Business Service. This business service comprises a single business component that comprises a single business element that is marked native.
Fixed Mode
When selected, indicates that you want to create a connector in fixed mode. This means the connector:
always communicates with the same native service
- always sends its response to the next component in the workflow using the same message format
Content-Based Mode
When selected, indicates that you want to create a connector in content-based mode. When you send a message to the native connector in content-based mode, the message contents dictate the message flow and the format required for the next component in the workflow. This deactivates the options below, and requires that you define the appropriate message formats in the CASP Metadata Repository. For more information about configuring connectors in content-based mode, refer to the CASP Administrator Directory Services User's Guide.
Always Send To This Service (radio button/pull-down menu) The business service associated with the native application programthat is, the business service to which the connector client sends messages. You can either select a business service from the pull-down menu, or let CASP create one for you by leaving this field blank and completing the Autogenerate Using This Profile radio button/pull-down menu below.
Note: If you choose to select an existing business service, that business service must comprise one business component, which comprises one business element only. That business element must be marked as native.
Autogenerate Service Using This Profile (required unless Always Send To This Service above is selected)
The profile is used to automatically generate the required business service, business component and business element that represent the native application.The resulting automatically-generated business service set is named based on the Name you entered on the Identification tab with NativeService appended to it. Therefore, if you entered CREDIT on the Identification tab Name field, a business service called CREDITNativeService is created which contains one business component called CREDITNativeService, which contains one business element called CREDITNativeService.
Reply Using This Message Descriptor (optional)
The message descriptor the native connector business element uses when sending the response from the native application to the next CASP application in the workflow. If you do not specify a message descriptor, kxcMsg00000002 is used by default.Send Datagram To Server (radio button) When selected, specifies that this connector send datagram (that is, one-way) messages to the native application.
Send Request To Server (radio button) When selected, specifies that this connector send request messages (that is, messages requiring a response) to the native application (this is the default). This also activates the Timeout section below.
Timeout
Never Expire (checkbox)
When checked, indicates the connector client should continually wait for a response from the native application; that is, the request does not time out.Expiry Interval
The number of hours, minutes, seconds, and/or milliseconds the connector client should wait for the response from the native application before timing out.