10/15

5 Configuring an Application Server

This chapter provides procedures for configuring an Oracle WebLogic Server, including installing a database driver, creating JDBC data resources, creating JMS resources, and setting up a user.

This chapter includes the following section:

• Configuring the Oracle WebLogic Server

Configuring the Oracle WebLogic Server

Before using your Oracle WebLogic Server, you must prepare it to host your Master Person Index (MPI) Application or your IHE Profiles Application, using the following procedures:

• Configuring the HL7 v2 Server

• Configure the audit client. For information, see To Build an IHE Profiles Application Project.

• Creating JDBC Data Resources for an IHE Profile Application Project

• Creating JMS Resources for an IHE Profile Application Project

• Setting Up the User

Configuring the HL7 v2 Server

1. After building an IHE Profiles Application project, unzip hl7v2.zip to a directory of your choice (for example, your OHMPI installation directory).

2. Set the OHMPI_IHE_HL7V2_HOME environment variable to the unzipped hl7v2 directory from the previous step.

   To set the OHMPI_IHE_HL7V2_HOME environment variable, update the setDomainenv script file.

   • For Windows, open the <domain_home>/bin/setDomainenv.bat file and add the following command line:

     set OHMPI_IHE_HL7V2_HOME=<your HL7v2 Server root path>

   • For Linux, open the <domain_home>/bin/setDomainenv.sh file and add the following command line:

     export OHMPI_IHE_HL7V2_HOME=<your HL7v2 Server root path>

   Note:

   If you have used a colon in the property, you need to escape it with \\.

   For example:

   <property_ABC>=C\:\\hl7v2Client

   rather than

   <property_ABC>=C:\hl7v2Client

3. Follow the existing instructions to configure and deploy the IHE Profiles Application to the WebLogic Server.

   Note:

   For rest of the HL7 v2 server configuration and the SSL configuration for the application server, see Configuring an IHE Profiles Application Project.

Creating JDBC Data Resources for an IHE Profile Application Project

This section provides instructions for creating the JDBC data resources and defining the JDBC connections for an IHE Profile Application Project.

To Create JDBC Data Resources for an IHE Profiles Application Project for Oracle

1. Start and stop the Oracle WebLogic Server. For instructions, see Oracle Fusion Middleware Online Documentation 12c Release 1 (12.1.2).

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 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. It is here that you will create a new JDBC Data Source.

6. In the Name field, type mpi_application_nameDataSource.

   The name you enter here will propagate elsewhere, and it must be the mpi application name that you have already created (for example, PatientDataSource).

7. In the JNDI Name field, type jdbc/mpi_application_nameDataSource.

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

8. From the Database Type drop-down list, select the appropriate database type. For example, Oracle.

9. Click Next.

10. From the Database Driver drop-down list, select the appropriate driver. For example, Oracle's Driver (Thin XA) for Instance Connections; Versions: 9.0.1 and later.

11. Click Next.

    Transaction Options appear on the page.

12. Click Next.

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

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

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

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

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

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

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

19. Click Next.

    The Settings for PatientDataSource page appears in the right panel.

20. Click Test Configuration, and if successful click Next.

    Note:

    If it fails, check the above steps.

    Select Targets appear 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.

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

    Note:

    If you do not select a target, the data source will be created but not deployed. You will need to deploy the data source at a later time.

22. Repeat the above steps to create jdbc/PatientSequenceDataSource.

23. Repeat the above steps to create jdbc/PIXDomainLUDataSource.

24. Repeat the above steps to create jdbc/PIMPendingLinksDataSource.

Creating JMS Resources for an IHE Profile Application Project

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 a:

• 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 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 the name for your new JMS Server.

   Note:

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

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.

   Note:

   The default server instance is exampleServer.

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. 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 (for example, mpi_applicationNameJMSModule).

   Note:

   Again, remain consistent to the name chosen for the JDBC Data Source and the JMS Server (in the previous examples the key word was "Patient," making this name PatientJMSModule).

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.

   Note:

   Retain the default, examplesServer.

6. Click Next.

7. 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 JMS Module (in the example, PatientJMSModule) from the table of JMS Modules.

   The Settings for PatientJMSModule 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, select Connection Factory and click Next.

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

5. In the Name field, type PatientOutBoundSender.

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

7. Make sure 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 select JMS Modules.

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

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

3. Click New, select Topic, and then click Next.

   If you are deploying on a Clustered environment, select DistributedTopic.

   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_nameTopic (for example, PatientTopic).

5. Set jms/PatientTopic 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, Patient Topic) and click Create a New Subdeployment.

7. In the Subdeployment Name field, type mpi_application_nameTopic (for example, PatientTopic), and click OK.

8. In the Targets table of JMS Servers, select mpi_application_nameJMSServer (for example, PatientJMSServer).

9. Click Finish.

To Create PixUpdateNotificationTopic

1. 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.

2. In the Name field, under JMS Destination Properties, type nameTopic (for example, PixUpdateNotificationTopic).

3. Set jms/PixUpdateNotificationTopic 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.

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

5. In the Subdeployment Name field, type nameTopic (for example, PixUpdateNotificationTopic), and click OK.

6. In the Targets table of JMS Servers, select nameJMSServer (for example, PatientJMSServer).

7. Click Finish.

Setting Up the User

In this step you create the MasterIndex.Admin and Administrator groups, and then create a new user within the two groups.

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

2. In the table on the Summary of Security Realms panel, click myrealm, which is the name of the realm.

   The Settings for myrealm panel appears.

3. Click 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 Administrator and click OK.

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

9. In the Users table, click New.

10. Type a name and a password for the new user you are creating and click OK.

11. Select User Group.

12. To add the two groups you created to the user you created, from the Available list, drag MasterIndex.Admin to the Chosen list, and then drag Administrator to the Chosen list.

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

    Note:

    See Oracle Healthcare Master Person Index User's Guide.