8/11

4 Configuring an Application Server

You need to configure application server resources, such as JDBC resources, JMS resources, and user accounts for the Individual/Organizational Provider MPI and the HPD Application.

Configuring Application Server Resources

Before running OHMPI with HPD Application, you must configure application server resources.

• Creating JDBC Data Resources for Individual Provider MPI Application

• Creating JDBC Data Resources for Organizational Provider MPI Application

• Creating JDBC Data Resources for HPD Application

• Creating JMS Resources for Individual Provider MPI Application

• Creating JMS Resources for Organizational MPI Provider Application

• Creating JMS Resources for HPD Application

• Creating User Accounts for Individual/Organizational MPI Application MIDM Access

Creating JDBC Data Resources for Individual Provider MPI Application

1. For instructions on how to start and stop Oracle WebLogic Server, see Oracle Fusion Middleware Online Documentation 12c Release 1 (12.1.3).

2. Launch the Oracle WebLogic Server Administration Console.

3. Log in using the default user Name (weblogic) and Password (welcome1).

   The Oracle WebLogic Administration Console appears.

4. On the left panel, under Domain Structure, expand Services, click JDBC, and then choose Data Sources.

   A Summary of JDBC Data Sources appears in the right panel.

5. To create a new JDBC Data Source, click New at the bottom of the right panel and select Generic Data Source from the drop-down list.

   Settings for a new JDBC Data Source appear in the right panel of the page. It is here that you will create a new JDBC Data Source.

6. In the Name field, type <mpi_application_name>DataSource.

   The name you enter here will propagate elsewhere, and it must be the Individual Provider MPI application name that has already been created (for example, HPDIndProviderDataSource).

7. In the JNDI Name field, type jdbc/<mpi_application_name>DataSource.

   Use the name you entered in step 6 here (for example, jdbc/HPDIndProviderDataSource).

8. In the Database Type drop-down list, choose the appropriate type (for example: Oracle) and click Next.

9. In the Database Driver drop-down list, choose the appropriate driver.

   For example, Oracle's Driver (Thin XA) for Instance Connections; Versions: 9.0.1 and later.

10. Click Next.

    Transaction Options appear on the page.

11. Click Next.

    Connection Properties appears on the Create a New JDBC Data Source panel. Use it to define the connection properties.

12. In the Database Name field, type a name for the database to which you want to connect (for example, hpd_ip).

13. In the Host Name field, type the name or the IP address of the database server (for example, localhost).

14. In the Port field, type the port on the database server that is used to connect to the database (for example, 1521).

15. In the Database User Name field, type the database account user name you want to use to create database connections (for example, hpd_ip).

16. In the Password field, type a password for your database account to use to create database connections.

17. In the Confirm Password field, re-type the password to confirm it.

18. Click Next.

    The Settings for HPDIndProviderDataSource page appears in the right panel.

19. Click Test Configuration and if successful click Next. If it fails, check the above steps.

    Select Targets appears on the Create a New JDBC Data Source page in the right panel. Here you select one or more targets to deploy the new JDBC data source.

20. In the Servers check list, select one or more target servers and click Finish.

    Note:

    If you are deploying on a Clustered environment, select the appropriate target server with the cluster environment.

21. Repeat the above steps to create jdbc/HPDIndProviderSequenceDataSource.

Creating JDBC Data Resources for Organizational Provider MPI Application

The procedure to create JDBC Data Resources for Organizational Provider MPI Application is same as procedure in Creating JDBC Data Resources for Individual Provider MPI Application. Replace HPDIndProvider by HPDOrgProvider, and replace hpd_ip by hpd_op.

Creating JDBC Data Resources for HPD Application

The procedure to create JDBC Data Resources for HPD Application is same as procedure in Creating JDBC Data Resources for Individual Provider MPI Application. Replace HPDIndProvider by HPD, and replace hpd_ip by hpd. Only HPDDataSource needs to be created. No corresponding HPDSequenceDataSource needs to be created though.

Creating JMS Resources for Individual Provider MPI Application

JMS servers act as management containers for the queues and topics in the JMS modules that are targeted to them.

The following procedure includes instructions for creating JMS resources, which includes:

• JMS Server

• JMS Module

• JMS Connection Factory in the specific JMS Module

• JMS Topic in the specific JMS Module

To Create JMS Server

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then choose JMS Servers.

   A Summary of JMS Servers appears in the right panel. It includes a table that summarizes the JMS servers that have been created in the current WebLogic Server domain.

2. In the table of previously created JMS Servers, click New.

   The Create a New JMS Server panel appears.

3. In the Name field, type the name for your new JMS Server.

   Note:

   This name already exists in the table of previously created JMS Servers (in the example, HPDIndProviderJMSServer).

4. Click Next.

   Select targets appear in the right panel under Create a New JMS Server.

5. From the Target drop-down list, select a target server instance or migratable target on which you want to deploy the JMS Server.

   If you are deploying on a Clustered environment, select the appropriate target server with the cluster environment.

6. Click Finish.

To Create JMS Module

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then choose JMS Modules.

   The JMS Modules panel appears.

2. In the JMS Modules table, click New to add a new JMS Module.

   The Create JMS System Module panel appears.

3. In the Name field, type the new JMS Module name as <mpi_application_name>JMSModule.

   Note:

   Be consistent to the name chosen for the JDBC Data Source and the JMS Server (in the previous examples the key word was HPDIndProvider, making this name HPDIndProviderJMSModule).

4. Click Next.

   Targets appear in the right panel under Create a New JMS System Module.

5. In the Servers area, select the server or cluster on which you want to deploy this JMS system module.

   If you are deploying on a Clustered environment, select the appropriate target server with the cluster environment.

   Retain the default, examplesServer.

6. Click Finish.

To Create JMS Connection Factory

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then choose JMS Modules.

2. Choose the JMS Module (for example, HPDIndProviderJMSModule) from the table of JMS Modules.

   The Settings for HPDIndProviderJMSModule page appears in the right panel.

3. In the Summary of Resources table, click New.

4. Under the Type column in the Summary of Resources table, choose Connection Factory, and click Next.

   Another panel of Create a New JMS System Module Resource appears.

5. In the Name field, type <mpi_application_name>OutBoundSender. (For example, HPDIndProviderOutBoundSender.)

6. In the JNDI Name field, type jms/<mpi_application_name>OutBoundSender. (For example, jms/HPDIndProviderOutBoundSender.)

7. Ensure that the XA Connection Factory Enabled check box is selected.

8. Click Next.

9. In the Target field, retain the default server instance, which is exampleServer, and click Finish.

   If you are deploying on a Clustered environment, select the appropriate target server with the cluster environment.

To Create JMS Topic

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then choose JMS Modules.

2. In the right panel, choose the JMS Module you created (in the example, HPDIndProviderJMSModule) from the table of JMS Modules.

   Settings for HPDIndProviderJMSModule appear in the right panel with a Summary of Resources table.

3. In the Summary of Resources table, click New, select Topic, and then click Next.

   The Create a New JMS System Module Resource panel appears on the right side of the window. Use this panel to set the properties that identify the new topic.

4. In the Name field, under JMS Destination Properties, type <mpi_application_name>Topic (for example, HPDIndProviderTopic).

5. Set jms/HPDIndProviderTopic as the JNDI Name and click Next.

   The Create a New JMS System Module Resource page appears in the right panel. Use this page to set the properties that will be used to target your new JMS system module resource.

6. In the Subdeployments drop-down list, select the topic name you just created (for example, HPDIndProviderTopic) and click Create a New Subdeployment.

7. In the Subdeployment Name field, type <mpi_application_name>Topic (for example, HPDIndProviderTopic), and click OK.

8. In the Targets table of JMS Servers, select <mpi_application_name>JMSServer (for example, HPDIndProviderJMSServer).

   If you are deploying on a Clustered environment, select the appropriate target server with the cluster environment.

9. Click Finish.

Creating JMS Resources for Organizational MPI Provider Application

The procedure to create JMS Resources for Organizational Provider MPI Application is same as procedure in Creating JMS Resources for Individual Provider MPI Application. Replace HPDIndProvider by HPDOrgProvider.

Creating JMS Resources for HPD Application

The JMS resources for the HPD application are similar to those of the MPI project, but requires some different steps.

The following procedure includes instructions for creating JMS resources for the HPD application:

• JMS Server

• JMS Module

• JMS Connection Factory

• Two JMS Queues

• Edit a Queue

To Create JMS Server

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then select JMS Servers.

   A Summary of JMS Servers appears in the right panel. It includes a table that summarizes the JMS servers that have been created in the current WebLogic Server domain.

2. In the table of previously created JMS Servers, click New.

   The Create a New JMS Server panel appears.

3. In the Name field, type HPDJMSServer as the name of your new JMS Server.

4. Click Next.

   Select targets appear in the right panel under Create a New JMS Server.

5. From the Target drop-down list, select a target server instance or migratable target on which you want to deploy the JMS Server.

   If you are deploying on a Clustered environment, select the appropriate target server with the cluster environment.

6. Click Finish.

To Create JMS Module

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then select JMS Modules.

   The JMS Modules panel appears.

2. In the JMS Modules table, click New to add a new JMS Module.

   The Create JMS System Module panel appears.

3. In the Name field, type HPDJMSModule as the new JMS Module name.

4. Click Next.

   Targets appear in the right panel under Create a New JMS System Module.

5. In the Servers area, select the server or cluster on which you want to deploy this JMS system module.

   If you are deploying on a Clustered environment, select the appropriate target server with the cluster environment.

6. Click Finish.

To Create JMS Connection Factory

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then select JMS Modules.

2. Select the HPDJMSModule JMS Module from the table of JMS Modules.

3. In the Summary of Resources table, click New.

4. Under the Type column in the Summary of Resources table, select Connection Factory, and click Next.

   Another panel of Create a New JMS System Module Resource appears.

5. In the Name field, type HPDFeedConnectionFactory.

6. In the JNDI Name field, type jms/HPDFeedConnectionFactory.

7. Ensure that the XA Connection Factory Enabled check box is selected.

8. Click Next.

9. In the Target field, retain the default server instance, and click Finish.

   If you are deploying on a clustered environment, select the appropriate target server with the cluster environment.

10. In the Summary of Resources screen, select HPDFeedConnectionFactory.

    The Settings for the HPDFeedConnectionFactory panel appears.

11. Click the Default Delivery tab.

12. Set the value of Default Unit-of-Order for Producer as System-generated.

13. Click Save.

To Create JMS Queue (HPDFeedQueue)

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then select JMS Modules.

2. Select the HPDJMSModule JMS Module from the table of JMS Modules.

3. In the Summary of Resources table, click New.

4. Under the Type column in the Summary of Resources table, select Queue, and click Next.

   Another panel of Create a New JMS System Module Resource appears.

5. In the Name field, type HPDFeedQueue.

6. In the JNDI Name field, type jms/HPDFeedQueue.

7. Click Next.

8. Click Create a New Subdeployment.

9. Accept the default subdeployment name of HPDFeedQueue.

10. Click OK.

11. From the Targets drop-down list, select HPDJMSServer.

12. Click Finish.

To Create JMS Queue (HPDFeedDeadQueue)

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then select JMS Modules.

2. Select the HPDJMSModule JMS Module from the table of JMS Modules.

3. In the Summary of Resources table, click New.

4. Under the Type column in the Summary of Resources table, select Queue, and click Next.

   Another panel of Create a New JMS System Module Resource appears.

5. In the Name field, type HPDFeedDeadQueue.

6. In the JNDI Name field, type jms/HPDFeedDeadQueue.

7. Click Next.

8. Click Create a New Subdeployment.

9. Accept the default subdeployment name of HPDFeedQueue.

10. Click OK.

11. From the Targets drop-down list, select HPDJMSServer.

12. Click Finish.

To Edit a Queue

1. On the left panel, under Domain Structure, expand Services, click Messaging, and then select JMS Modules.

2. Select the JMS Module HPDJMSModule from the table of JMS Modules.

3. In the Summary of Resources table, select HPDFeedQueue.

   The Settings for the HPDFeedQueue panel appears.

4. Click the Delivery Failure tab.

5. In the Recovery Limit field, enter 1.

6. From the Error Destination drop-down list, select HPDFeedDeadQueue.

7. Click Save.

Creating User Accounts for Individual/Organizational MPI Application MIDM Access

You create user accounts for Individual/Organizational Provider MIDM access using the WebLogic Admin Console. There are three pre-defined user groups for the MIDM, and you can define additional user groups each with different permissions. For more information about configuring user groups (roles) for MIDM, see Oracle Healthcare Master Person Index Data Manager User's Guide.

In this step, you create the MasterIndex.Admin, IndProviderAdministrator, and OrgProviderAdministrator groups, and then create two new users.

1. On the left panel, under Domain Structure, expand Services, and then choose Security Realms.

2. In the table on the Summary of Security Realms panel, click myrealm.

   The Settings for myrealm panel appears.

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

4. In the Groups table, click New.

5. In the Name field, type MasterIndex.Admin and click OK.

6. In the Groups table, click New.

7. In the Name field, type IndProviderAdministrator and click OK.

8. In the Groups table, click New.

9. In the Name field, type OrgProviderAdministrator and click OK.

10. On the Settings for myrealm panel, select Users and Groups and then Users.

11. In the Users table, click New.

12. Type a name (for example, midm_ip) and a password for the new user you are creating for the Individual Provider MPI and click OK.

13. Select User Group.

14. Drag MasterIndex.Admin and IndProviderAdministrator from the Available list to the Chosen list.

15. Type a name (for example, midm_op) and a password for the new user you are creating for the Organizational Provider MPI and click OK.

16. Select User Group.

17. Drag MasterIndex.Admin and OrgProviderAdministrator from the Available list to the Chosen list.

18. Add the user MasterIndex.WSUser and then add the MasterIndex.Admin group for it.

    For more details, see Oracle Healthcare Master Person Index User's Guide.