Process of Setting Up Clinical Payments Integration

To set up the integration of clinical payments between Siebel Clinical and a third-party application, perform the following tasks:

• "Configuring Siebel Tools for Clinical Payments Integration"

• "Activating Workflows for Clinical Payments Integration"

• "Configuring the Inbound Web Service for Clinical Payments Integration"

• "Configuring Java Message Service Parameters for Clinical Payments Integration"

Configuring Siebel Tools for Clinical Payments Integration

This task describes how to create and configure Siebel Tools objects that are required for Siebel Clinical payments integration. In Siebel Tools, you can configure the status value that triggers the workflow to send the payment request to the third-party application.

This task is a step in "Process of Setting Up Clinical Payments Integration".

To configure Siebel Tools for clinical payments integration  

1. In Siebel Tools, lock the LS Clinical Payments project.

2. Select Business Component Object type in the object explorer.

3. Query for Clinical Payments.

4. Select Business Component User Property under Business Component in the object explorer.

5. Create the user properties in the following table.

   Business Component User Property Name	Value	Description
   Named Method n	"SendPayment", "INVOKESVC", "Clinical Payments", "Workflow Process Manager", "RunProcess", ' "ProcessName" ', ' "LS Clinical Payments Outbound" ', " 'Object Id' ", " [Id] "	This user property configures the LS Clinical Payments Outbound workflow.
   On Field Update Invoke n	"", "Clinical Payments", "SendPayment", "[Status] = LookupValue('FUNDRQ_STATUS','To Be Submitted') AND [Status] IS NOT NULL"	This user property sets the status trigger for the LS Clinical Payments Outbound workflow. By default, a status of To Be Submitted for a payment request triggers the LS Clinical Payments Outbound workflow to send the payment request to the third-party application. You can configure this user property to use a different Status value to trigger the LS Clinical Payments Outbound workflow.
   Status Confirmation Popup 1	"Status", "Waiting for Acknowledgement", "In Progress", "FUNDRQ_STATUS", "<optional custom status message>"	This user property adds In Progress to the values of the Status field for manual configuration. You can customize the <optional custom message> field to override the following default warning message: A payment request is in the process of being sent to the target system. Changing the status may lead to a duplicate payment request being sent in the future. Do you want to continue?
   Status Confirmation Popup 2	"Status", "Waiting for Acknowledgement", "Withdraw", "FUNDRQ_STATUS", "<optional custom message>"	This user property adds Withdraw to the values of the Status field for manual configuration.

   
   

6. Compile the locked and updated project.

   For information about compiling projects, see Developing and Deploying Siebel Business Applications.

Activating Workflows for Clinical Payments Integration

This task describes how to activate the workflows required for Siebel Clinical payments integration.

This task is a step in "Process of Setting Up Clinical Payments Integration".

To activate workflows for clinical payments integration  

1. Navigate to the Administration - Business Process screen, then the Workflow Deployment view.

2. Query for, and activate, each of the following workflows:

   • LS Clinical Payments Outbound

   • SWI LS Clinical Payments Inbound

   • LS Clinical State Validation

3. Verify that each activated workflow is added to the Active Workflow Processes view at the bottom of the screen.

Note: You perform this procedure only the first time that you want to access the integration feature for the clinical payments. The workflow remains activated.

Configuring the Inbound Web Service for Clinical Payments Integration

This task describes how to configure the SWI LS Clinical Payment Inbound Web service that is required for Siebel Clinical payments integration.

Note: It is recommended that you use HTTPS authentication. For information about configuring Secure Sockets Layer (SSL) for HTTPS authentication, see Siebel Security Guide.

This task is a step in "Process of Setting Up Clinical Payments Integration".

To configure the inbound Web service for clinical payments integration  

1. Navigate to the Administration - Web Services screen, then the Inbound Web Services view.

2. Query for the SWI LS Clinical Payment Inbound Web service.

3. On the Service Ports applet, update the Address variable to point to your Web server, and configure the Language variable.

4. Click Clear Cache on the Inbound Web Services applet.

5. Restart the Siebel Server.

Configuring Java Message Service Parameters for Clinical Payments Integration

This task describes how to configure Java Message Service parameters that are required for Siebel Clinical payments integration.

This task is a step in "Process of Setting Up Clinical Payments Integration".

To configure Java Message Service parameters for clinical payments integration  

1. Navigate to the Administration - Server Configuration screen, then the Enterprises view.

2. Select the Enterprise Server that you want to configure.

3. Navigate to the Profile Configuration view.

4. Query for the JMSParameter profile alias.

5. In the Profile Parameters list, set the parameters in the following table.

   Name	Value
   SendUsername	Set the value to the user name for the Oracle WebLogic server.
   SendPassword	Set the value to the user password for the Oracle WebLogic server.

   
   

6. Restart the Siebel Server.

7. Verify the CLASSPATH and jndi.properties configurations.

   For information about verifying the CLASSPATH and jndi.properties configurations, see Transports and Interfaces: Siebel Enterprise Application Integration