8 Performing Post-Installation Configurations

This section discusses post-installation configurations for the Study, Subject, and Visit Synch: Siebel Clinical - Oracle Clinical. The section includes:

• Section 8.1, "Creating a User in Oracle WebLogic Server"

• Section 8.2, "Configuring Session Pool Manager"

• Section 8.3, "Configuring the Oracle Clinical RAC Data Source"

8.1 Creating a User in Oracle WebLogic Server

As part of this integration, Siebel Clinical writes messages to a JMS queue on the SOA server. Ensure that the user you choose for connecting Siebel to the SOA server exists in the Oracle WebLogic server. For example, sadmin user is the default admin user of Siebel.

To create a user:

1. Navigate to the WebLogic console.

2. Under Domain Structure of soa_domain, select Security Realms, and then myrealm.

3. Select the Users and Groups tab, and then the Users tab.

4. Click New.

5. In the Name field, enter sadmin as the provider name.

6. In the Password field, enter password provided during configuration of the corresponding Siebel Workflow.

7. In the Provider list, select the default authentication provider for the user.

8. Click OK.

8.2 Configuring Session Pool Manager

This integration uses the Session Pool Manger utility. Configure Session Pool Manager after you install the PIP. For information on how to configure Session Pool Manager for your integration environment and needs, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide.

8.3 Configuring the Oracle Clinical RAC Data Source

To configure the OC data source if the OC database is RAC, perform the following:

For the UpdateClinicalStudyOCDS Data Source:

1. Navigate to the WebLogic console.

2. Under Domain Structure of soa_domain, select Services, and then Data Sources.

3. On the Configuration page, select UpdateClinicalStudyOCDS.

4. Click Delete.

5. Click New and select the Multi Data Sources option.

6. In the Create a New JDBC Multi Data Source screen, name the datasource as UpdateClinicalStudyOCDS.

7. In the JNDI Name column, enter jdbc/UpdateClinicalStudyOC.

   Note:

   Do not change any other default values.

8. Click Next.

9. Select the SOA server and click Next.

10. Retain the default, Non-XA Driver, and click Next.

11. Click Create New Data Source.

12. In the Create Screen, name the Data source as UpdateClinicalStudyOCDS-rac0.

    where, rac0 is the first RAC node and the number should be incremented for each node.

13. In the JNDI Name column, enter jdbc/UpdateClinicalStudyOC-rac0.

    where, rac0 is the first RAC node and the number should be incremented for each node.

    Note:

    Do not change any other default values.

14. Click Next.

15. Enter Oracle as the database type. For the driver type, enter Oracle Driver (Thin) for RAC server-Instance connection Version 10, 11.

16. Deselect Supports Global Transactions and click Next.

17. Click Next and enter the database name, host name, and port of your Oracle Clinical database Instance. You must enter the user name as rxc and password for this user.

18. Click Next.

19. Test the configuration and click Next.

20. Select your SOA server as the target. For example, soa_server1.

21. Click Finish.

    The Data Source is created and deployed on the target server.

22. Repeat steps 11 to 21 for each node of the RAC instance.

For the OracleClinicalCoreDS Data Source:

1. Delete the existing OracleClinicalCoreDS using the steps 2 to 4 of the For the UpdateClinicalStudyOCDS Data Source section.

2. Click New and select the Multi Data Sources option.

3. In the Create a New JDBC Multi Data Source screen, name the datasource as OracleClinicalCoreDS.

4. In the JNDI Name column, enter jdbc/OracleClinicalCoreDS.

   Note:

   Do not change any other default values.

5. Click Next.

6. Select the SOA server and click Next.

7. Retain the default, Non-XA Driver, and click Next.

8. Click Create New Data Source.

9. In the Create Screen, name the datasource as OracleClinicalCoreDS-rac0.

   where, rac0 is the first RAC node and the number should be incremented for each node.

10. In the JNDI Name column, enter jdbc/OracleClinicalCoreDS-rac0.

    where, rac0 is the first RAC node and the number should be incremented for each node.

    Note:

    Do not change any other default values.

11. Click Next.

12. Enter Oracle as the database type. For the driver type, enter Oracle Driver (Thin) for RAC server-Instance connection Version 10, 11.

13. Deselect Supports Global Transactions and click Next.

14. Click Next and enter the database name, host name, and port of your Oracle Clinical database Instance. You must enter the user name as rxc and password for this user.

15. Click Next.

16. Test the configuration and click Next.

17. Select your SOA server as the target. For example, soa_server1.

18. Click Finish.

    The Data Source is created and deployed on the target server.

19. Repeat steps 8 to 18 for each node of the RAC instance.