4 Configuring Your Healthcare Domain

This chapter describes how to create and configure your Healthcare domain.

Before you begin the configuration process, ensure that you have completed installing the Oracle Healthcare software in the same Oracle home as Oracle Fusion Middleware Infrastructure and Oracle SOA Suite. For more information, see Chapter 2.

By the end of this chapter, you would have created database schemas for Oracle Healthcare and configured an Oracle WebLogic domain for Healthcare with one cluster and one managed server on a single host.

This chapter contains the following sections:

4.1 Creating the Database Schemas

Before you can configure an Oracle Healthcare domain, you must install the required Oracle Healthcare schemas on a certified database for use with this release of Oracle Fusion Middleware.

Follow the instructions in Section 3.1 to install the schemas.

After you finish installing the schemas, go to Section 4.2 to continue with the domain creation and configuration.

4.2 Configuring Your Healthcare WebLogic Domain

This section provides instructions for creating a WebLogic domain by using the configuration wizard. For more information on other methods available for domain creation, see "Additional Tools for Creating, Extending, and Managing WebLogic Domains" in Creating WebLogic Domains Using the Configuration Wizard.

Creating and configuring your domain involves the following:

4.2.1 Starting the Configuration Wizard

To begin the domain configuration, navigate to the ORACLE_HOME/oracle_common/common/bin directory and start the WebLogic Server Configuration Wizard.

On UNIX operating systems:

./config.sh

On Microsoft Windows operating systems:

config.cmd

4.2.2 Navigating the Configuration Wizard Screens to Create the Domain

Follow the instructions in this section to create and configure the domain for the topology.

Note:

You can use the same procedure described in this section to extend an existing domain. If your needs do not match the instructions given in the procedure, then ensure that you make your selections accordingly, or refer to the supporting documentation for additional details.

Domain creation and configuration includes the following tasks:

Task 1   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Create a new domain.

In the Domain Location field, specify your Domain home directory. Ensure that B2B and Healthcare reside in separate domain homes.

It is recommended that you locate your Domain home in accordance with the directory structure summarized in "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware, where the Domain home is located outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or reinstall your software.

Tip:

More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Template

On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:

  • Oracle SOA Suite for healthcare integration - 12.1.3.0 [soa]]

    Selecting this template automatically selects the following as dependencies:

    • Oracle B2B - 12.1.3.0 [soa]

    • Oracle SOA Suite - 12.1.3.0 [soa]

    • Oracle Enterprise Manager - 12.1.3.0 [em]

    • Oracle Enterprise Manager - 12.1.3.0 [em]

    • Oracle WSM Policy Manager - 12.1.3.0 [oracle_common]

    • Oracle JRF - 12.1.3.0 [oracle_common]

    • WebLogic Coherence Cluster Extension - 12 1.3.0 [wlserver]

Description of healthcare_template.png follows
Description of the illustration healthcare_template.png

Tip:

For more information about the options on this screen, see "Templates" in Creating WebLogic Domains Using the Configuration Wizard.

Task 3   Selecting the Application Home Location

On the Application Location screen, select the location in which you want to store your applications associated with your domain. This location is also referred to as the Application home directory.

It is recommended that you locate your Application home in accordance with the directory structure summarized in "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware, where the Application home is located outside the Oracle home directory. This directory structure will help you avoid issues when you need to upgrade or re-install your software.

Tip:

For more information about the Application home directory see, "Choosing an Application Home" in Planning an Installation of Oracle Fusion Middleware.

For more information about the options on this screen, see "Application Location" in Creating WebLogic Domains Using the Configuration Wizard.

Task 4   Configuring the Administrator Account

On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain.

It is recommended that you make a note of the user name and password specified on this screen; you will need these credentials later to boot and connect to the domain's Administration Server.

Task 5   Specifying the Domain Mode and JDK

On the Domain Mode and JDK screen:

  • Select Production in the Domain Mode field.

  • Select the Oracle HotSpot JDK in the JDK field.

Tip:

For more information about the options on this screen, see "Domain Mode and JDK" in Creating WebLogic Domains Using the Configuration Wizard.

Task 6   Specifying the Datasource Configuration Type

Select RCU Data to activate the fields on this screen. The RCU Data option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for the schemas needed to configure the domain.

Note:

If you choose to select Manual Configuration on this screen, you will have to manually fill in the parameters for your schema on the JDBC Component Schema screen.

After selecting RCU Data, fill in the following fields:

Field Description

DBMS/Service

Enter the database DBMS name, or service name if you selected a service type driver.

Host Name

Enter the name of the server hosting the database.

Port

Enter the port number on which the database listens.

Schema Owner

Schema Password

Enter the username and password for connecting to the database's Service Table schema. This is the schema username and password that was specified for the Service Table component on the "Schema Passwords" screen in RCU (see Task 5 in Section 3.1.3).

The default username is prefix_STB, where prefix is the custom prefix that you defined in RCU.

Description of config_datasource.gif follows
Description of the illustration config_datasource.gif

Click Get RCU Configuration when you finish specifying the database connection information. The following output in the Connection Result Log indicates that the operating succeeded:

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

Tip:

For more information about the RCU Data option, see "Understanding the Service Table Schema" in Creating Schemas with the Repository Creation Utility.

For more information about the options on this screen, see "Datasource Defaults" in Creating WebLogic Domains Using the Configuration Wizard.

Task 7   Specifying JDBC Component Schema Information

Verify that the values on the JDBC Component Schema screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately.

Tip:

For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:

For more information about the options on this screen, see "JDBC Component Schema" in Creating WebLogic Domains Using the Configuration Wizard.

Task 8   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the datasource connections you have just configured.

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

Tip:

For more information about the options on this screen, see "Test Component Schema" in Creating WebLogic Domains Using the Configuration Wizard.

Task 9   Selecting Advanced Configuration

To complete the domain configuration for the topology, select the following options on the Advanced Configuration screen:

  • Administration Server

    This is required to properly configure the listen address of the Administration Server.

  • Node Manager

    This is required to configure Node Manager.

  • Managed Server, Clusters and Coherence

    This is required to configure the Healthcare Managed Server.

Task 10   Configuring the Administration Server Listen Address

On the Administration Server screen, select the drop-down list next to Listen Address and select the IP address on the host where the Administration Server will reside.

Do not use All Local Addresses.

Do not specify any server groups for the Administration Server.

Task 11   Configuring Node Manager

The Node Manager screen can be used to select the type of Node Manager you want to configure, along with the Node Manager credentials.

Select Per Domain Default Location as the Node Manager type, then specify the Node Manager credentials.

Tip:

For more information about the options on this screen, see "Node Manager" in Creating WebLogic Domains Using the Configuration Wizard.

For more information about the types of Node Manager, see "Node Manager Overview" in Administering Node Manager for Oracle WebLogic Server.

Task 12   Configuring Managed Servers

On the Managed Servers screen, create a new Managed Server named hc_server1:

  1. In the Listen Address drop-down list, select the IP address of the host on which the Managed Server will reside or use the system name or DNS name that maps to a single IP address.

    Do not use All Local Addresses.

  2. In the Server Groups drop-down list, select SOA-MGD-SVRS. This server group ensures that SOA and Oracle Web Services Manager (OWSM) services are targeted to the Managed Servers that you are creating.

    There is another server group called SOA-MGD-SVRS-ONLY that targets only SOA but not Oracle Web Services Manager (OWSM) to the server. This is typically used if you want to have Oracle Web Services Manager (OWSM) in a different server rather than with the SOA server.

    Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that are mapped to a given server group are automatically targeted to all servers that are assigned to that group. For more information, see "Application Service Groups, Server Groups, and Application Service Mappings" in Domain Template Reference.

    For more information about the high availability standard topology, see "Understanding the Fusion Middleware Standard HA Topology" in High Availability Guide.

    For more information about the next steps to prepare for high availability after your domain is configured, see Section 5.3.

These server names and will be referenced throughout this document; if you choose different names be sure to replace them as needed.

Description of hc_server.png follows
Description of the illustration hc_server.png

Tip:

For more information about the options on this screen, see "Managed Servers" in Creating WebLogic Domains Using the Configuration Wizard.

Task 13   Configuring a Cluster

Use the Clusters screen to create a new cluster:

  1. Select Add.

  2. Specify hc_cluster1 in the Cluster Name field.

  3. Leave the Cluster Address field blank.

Description of hc_cluster.gif follows
Description of the illustration hc_cluster.gif

New clusters can also be created by using the Oracle WebLogic Server Administration Console. In such cases, cluster communication (unicast or multicast) can be configured when the new cluster is created. For more information, see "Create and configure clusters" in Oracle WebLogic Server Administration Console Online Help

Tip:

For more information about the options on this screen, see "Clusters" in Creating WebLogic Domains Using the Configuration Wizard.

Task 14   Assigning Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign hc_server1 to the new cluster, hc_cluster1:

  1. In the Clusters pane, select the cluster to which you want to assign the servers; in this case, hc_cluster1.

  2. In the Servers pane, assign hc_server1 to hc_cluster1 by doing one of the following:

    • Click once on hc_server1 to select it, then click on the right arrow to move it beneath the selected cluster (hc_cluster1) in the Clusters pane.

    • Double-click on hc_server1 to move it beneath the selected cluster (hc_cluster1) in the clusters pane.

Description of hc_servers_to_cluster.gif follows
Description of the illustration hc_servers_to_cluster.gif

Tip:

For more information about the options on this screen, see "Assign Servers to Clusters" in Creating WebLogic Domains Using the Configuration Wizard.

Task 15   Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the default port number 0 as the Coherence cluster listen port.

Note:

Setting the unicast listen port to 0 creates an offset for the Managed Server port numbers. The offset is 5000, meaning the maximum allowed value that can be assigned to a Managed Server port number is 60535, instead of 65535.

See Table 5-2 for more information and next steps for configuring Coherence.

Note:

For Coherence licensing information, see "Oracle Coherence" in Licensing Information.

Task 16   Creating a New Machine

Use the Machines screen to create a new machine in the domain. A machine is required in order for the Node Manager to be able to start and stop the servers.

Tip:

If you plan to create a high availability environment and know the list of machines required for your target topology, you can follow the directions in this section to create all of the machines at this time. For more information, see "Optional Scale Out Procedure" in High Availability Guide.

  1. Click Add to create a new machine.

  2. Specify hc_machine1 in the Name field.

  3. In the Node Manager Listen Address field, select the IP address of the machine where the Managed Servers are being configured.

    You must select a specific interface and not "localhost." This allows Coherence cluster addresses to be dynamically calculated.

  4. Verify the port in the Node Manager Listen Port field.

    The port number 5556, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.

Note:

If you are extending an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.

Description of hc_machine.gif follows
Description of the illustration hc_machine.gif

Tip:

For more information about the options on this screen, see "Machines" in Creating WebLogic Domains Using the Configuration Wizard.

Task 17   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to the new machine you have just created:

  1. In the Machines pane, select the machine to which you want to assign the servers; in this case, hc_machine1.

  2. In the Servers pane, assign AdminServer to hc_machine1 by doing one of the following:

    • Click once on AdminServer to select it, then click on the right arrow to move it beneath the selected machine (hc_machine1) in the Machines pane.

    • Double-click on AdminServer to move it beneath the selected machine (hc_machine1) in the Machines pane.

  3. Repeat to assign hc_server1 to hc_machine1.

Description of hc_servers_to_machine.gif follows
Description of the illustration hc_servers_to_machine.gif

Tip:

For more information about the options on this screen, see "Assign Servers to Machines" in Creating WebLogic Domains Using the Configuration Wizard.

Task 18   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.

You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.

Domain creation will not begin until you click Create.

Tip:

For more information about the options on this screen, see "Configuration Summary" in Creating WebLogic Domains Using the Configuration Wizard.

Task 19   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen will show the following items about the domain you just configured:

  • Domain Location

  • Administration Server URL

Description of config_success.png follows
Description of the illustration config_success.png

You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.

Click Finish to dismiss the configuration wizard.

4.3 Starting the Servers

After the configuration is complete, do the following to access the tools with which you can manage your domain:

Note:

For more information on additional tools you can use to manage your domain, see "Overview of Oracle Fusion Middleware Administration Tools" in Administering Oracle Fusion Middleware.

4.3.1 Starting the Node Manager

To start your per-domain Node Manager, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, start the Node Manager as shown below, using nohup and nm.out as an example output file:

nohup ./startNodeManager.sh > $LOG_DIR/nm.out&

In the preceding command, LOG_DIR is the location of directory in which you want to store the log files.

On Windows operating systems, run:

startNodeManager.cmd

Note:

On Windows operating systems, it is recommended that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.

For more information, see "Running Node Manager as a Startup Service" in Administering Node Manager for Oracle WebLogic Server.

For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.

4.3.2 Starting the Administration Server

To start the Administration Server, go the DOMAIN_HOME/bin directory.

On UNIX operating systems, run:

./startWebLogic.sh

On Windows operating systems, run:

startWebLogic.cmd

If you have selected Production Mode on the Domain Mode and JDK screen in Task 5 (Section 4.2.2), you will be prompted for the login credentials of the Administrator user as provided on the Administrator Account screen in Task 4.

Tip:

For more information about starting the Administration Server, see "Starting and Stopping Administration Servers" in Administering Oracle Fusion Middleware.

In production mode, a boot identity file can be created to bypass the need to provide a user name and password when starting the Administration Server. For more information, see "Creating a Boot Identity File for an Administration Server" in Administering Server Startup and Shutdown for Oracle WebLogic Server.

You can verify that the Administration Server is up and running by accessing the Administration Server Console. The URL is provided on the Configuration Success screen in Task 19.

Note:

Ensure that the database hosting your product schemas is up and running and accessible by the Administration Server.

http://administration_server_host:administration_server_port/console

The default Administration Server port number is 7001.

Description of hc_admin_console.gif follows
Description of the illustration hc_admin_console.gif

For more information about how to use the Administration Console, see "Getting Started Using Oracle WebLogic Server Administration Console" in Administering Oracle Fusion Middleware.

4.3.3 Starting the Managed Servers

To start the Managed Servers:

  1. Log in to Oracle Fusion Middleware Control:

    http://administration_server_host:administration_server_port/em

    The Administration Server host and port number were in the URL on the Configuration Success screen (Task 19). The default Administration Server port number is 7001.

    The login credentials were provided on the Administrator Account screen (Task 4).

  2. From the "Target Navigation" pane, click the arrows to expand the domain until the Managed Server (hc_server1) is visible.

    Description of config_hc_servers_down.gif follows
    Description of the illustration config_hc_servers_down.gif

  3. Select the Managed Server (hc_server1).

  4. Next to the WebLogic Server menu, select Start Up.

    Description of config_hc_start_servers.gif follows
    Description of the illustration config_hc_start_servers.gif

  5. In the Target Navigation page, select your domain name to see that all the servers are up and running.

    Description of config_hc_servers_up.gif follows
    Description of the illustration config_hc_servers_up.gif

4.4 Verifying Your Configuration

To verify that your domain is configured properly, see Section 5.1. You should familiarize yourself with the tasks described in the section and perform them to verify that your domain is properly configured.