Use this dialog to define the following supporting components required for a native connector:
A native connector business service to which an CASP application can
make a request (this is the Native
Connector BS shown in Figure
1).
Note: the Business Element Profile and Client Profile fields below appear only when you are creating a native connector; they do not appear when you are modifying a native connector.
Business Element Profile
The business element profile you want to use for the automatically-generated native connector business service set and the command server business service set.The profile you select should at least have the transport layer (either MQSeries or MSMQ) defined and the Queue Name value set to False on the Propagate tab. Transport-specific profiles are typically seeded into the CASP directory at installation time that meet these requirements. You can use these samples to create customized profiles for your site.
The resulting automatically-generated business service sets are named as follows:
The native connector business service, business component, and business element are created with the Name you entered on the Identification tab.
The command server business service, business component, and business element are created based on the Name you entered on the Identification tab with Comm appended to it.
Therefore, if you entered CREDIT on the Identification tab Name field, two business service sets are created; one called CREDIT that comprises one business component called CREDIT, which contains one business element called CREDIT; one called CREDITComm, that comprises a business component and business element also called CREDITComm.
Client Profile
The client profile you want CASP to use when creating the connector client. The connector client sends CASP requests to the native application;The native application then sends its response back to this client.The client profile you select should at least have the transport layer defined. Transport-specific profiles are typically seeded into the CASP directory at installation time that meet this requirement.
EMS Service
(Optional) The name of the EMS business service to which the connector can send errors. For more information on the EMS business service and CASP error management, refer to the CASP Diagnosis Guide.Persistent Message Processing (checkbox)
When checked, indicates that in-progress connector data is maintained in the connector internal work queue even if the transport (typically MQSeries), the connector, or both fail.Display Diagnostic Messages (checkbox)
When checked, specifies that detailed diagnostic messages are displayed in the command window where the connector is running. Typically, you would use this if you need to debug your connector configuration.