5 Configuring a Domain for Oracle SOA for Healthcare Integration
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 Installing the Oracle B2B and Healthcare Software.
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.
5.1 Creating the Database Schemas
Before you can configure an Oracle B2B and Healthcare domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.
Follow the instructions in this section to install the schemas:
5.1.1 Installing and Configuring a Certified Database
You must verify that you installed and configured a certified database, and that the database is up and running.
For more information, see Installing a Database and Database Schemas in Planning an Installation of Oracle Fusion Middleware.
5.1.2 Starting the Repository Creation Utility (RCU)
Starting RCU requires that your JDK environment variable is set correctly.
To start the Repository Creation Utility (RCU):
5.1.3 Navigating the RCU Screens to Create the Schemas
The topics in this section describe tasks for creating schemas.
5.1.3.2 Selecting a Method of Schema Creation
If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have the necessary SYSDBA privileges.
If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option generates a SQL script that you can provide to your database administrator. See Understanding System Load and Product Load in Creating Schemas with the Repository Creation Utility.
5.1.3.3 Providing Database Connection Details
Provide the database connection details for RCU to connect to your database.
Click Next to proceed, then click OK on the dialog window to confirm that connection to the database was successful.
5.1.3.4 Specifying a Custom Prefix and Selecting Schemas for Oracle B2B and Healthcare
Select Create new prefix, specify a custom prefix, then select the SOA Suite schema. This action automatically selects the following schemas as dependencies:
User Messaging Service
Metadata Services
Oracle Platform Security Services
Audit Services
Audit Services Append
Audit Services Viewer
WebLogic Services
The schema Common Infrastructure Services is also automatically created; this schema is grayed out; you cannot select or deselect it. This schema enables you to retrieve information from RCU during domain configuration. For more information, see "Understanding the Service Table Schema" in Creating Schemas with the Repository Creation Utility.
The custom prefix is used to logically group these schemas together for use in this domain only; you must create a unique set of schemas for each domain as schema sharing across domains is not supported.
Tip:
For more information about custom prefixes, see "Understanding Custom Prefixes" in Creating Schemas with the Repository Creation Utility.
For more information about how to organize your schemas in a multi-domain environment, see "Planning Your Schema Creation" in Creating Schemas with the Repository Creation Utility.
Tip:
You must make a note of the custom prefix you choose to enter here; you will need this later on during the domain creation process.
Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.
5.1.3.5 Specifying Schema Passwords
Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.
Tip:
You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.
5.1.3.6 Specifying Custom Variables
Specify the custom variables for the SOA Infrastructure schema. For the Oracle SOA Suite standard installation topology, accept both default values for the Database Profile (SMALL) and Healthcare Integration (NO).
For more information about the database profile, see Tuning Performance.
Tip:
More information about the options on this screen can be found in Custom Variables in Creating Schemas with the Repository Creation Utility.
5.2 Configuring the Oracle B2B Domain
This section provides instructions for creating a WebLogic domain using the Configuration Wizard. For more information on other methods to create domains, 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:
5.2.1 Starting the Configuration Wizard
To begin 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
5.2.2 Navigating the Configuration Wizard Screens to Create the Domain
This section describes how to create and configure the domain for the topology.
Note:
You can use this procedure to extend an existing domain. If your needs don’t match the instructions in the procedure, be sure to make your selections accordingly, or see the supporting documentation for more details.
Creating and configuring a domain includes the following tasks:
5.2.2.1 Selecting the Domain Type and Domain Home Location
This task requires you to select the Domain home directory location. The optimal place for this directory is outside the Oracle home directory.
To specify the Domain type and Domain home directory:
- On the Configuration Type screen, select Create a new domain.
- In the Domain Location field, specify your Domain home directory.
For more about other options on this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.2 Selecting the Configuration Templates for Oracle SOA Suite for Healthcare Integration
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.2.1 [soa]
Selecting this template automatically selects the following as dependencies:
Oracle B2B - 12.2.1 [soa]
Oracle SOA Suite - 12.2.1. [soa]
Oracle Enterprise Manager - 12.2.1 [em]
Oracle WSM Policy Manager - 12.2.1.0 [oracle_common]
Oracle JRF - 12.2.1 [oracle_common]
WebLogic Coherence Cluster Extension - 12 2.1 [wlserver]
Tip:
More information about the options on this screen can be found in "Templates" in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.3 Selecting the Application Home Location
On the Application Location screen, select the location to store applications associated with your domain, also known as the Application home directory.
Oracle recommends that you locate your Application home in accordance with the directory structure 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 helps avoid issues when you need to upgrade or re-install your software.
Tip:
For more about the Application home directory, see Choosing an Application Home in Planning an Installation of Oracle Fusion Middleware.
For more about options on this screen, see Application Location in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.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.
Oracle recommends that you make a note of the user name and password that you enter on this screen; you need these credentials later to boot and connect to the domain's Administration Server.
5.2.2.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 about the options on this screen, see Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.6 Specifying the Database Configuration Type
Select RCU Data to activate 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 schemas needed to configure the domain.
Note:
If you select Manual Configuration on this screen, you must manually fill in 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 entered for the Service Table component on the "Schema Passwords" screen in RCU (see Specifying Schema Passwords). The default username is |
Click Get RCU Configuration when you finish specifying the database connection information. The following output in the Connection Result Log indicates that the operation 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 other options on this screen, see Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.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:
More information about the other options on this screen can be found in JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.8 Testing the JDBC Connections
Use the JDBC Component Schema Test screen to test the data source connections you 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.
By default, the schema password for each schema component is the password you specified while creating your schemas. If you want different passwords for different schema components, manually edit them by entering the password you want in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you changed the password in and test the connection again.
Tip:
See JDBC Component Schema Test in Creating WebLogic Domains Using the Configuration Wizard for more information about other options on this screen.
5.2.2.9 Selecting Advanced Configuration
To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
Administration Server
Required to properly configure the listen address of the Administration Server.
Node Manager
Required to configure Node Manager.
Managed Server, Clusters and Coherence
Required to configure the Oracle B2B Managed Server.
5.2.2.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 of the host where the Administration Server will reside. Do not use All Local Addresses.
Do not specify any server groups for the Administration Server.
5.2.2.11 Configuring Node Manager
Use the Node Manager screen 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 Node Manager credentials.
Tip:
For more about options on this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.
For more about Node Manager types, see Node Manager Overview in Administering Node Manager for Oracle WebLogic Server.
5.2.2.12 Configuring Managed Servers for Oracle Healthcare
On the Managed Servers screen, a new Managed Server named b2b_server_1 is created:
These server names and will be referenced throughout this document; if you choose different names be sure to replace them as needed.
Tip:
More information about the options on this screen can be found in "Managed Servers" in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.13 Configuring a Cluster for Oracle Healthcare
Use the Clusters screen to create a new cluster:
- Click Add.
- Specify
hc_cluster_1in the Cluster Name field. - Leave the Cluster Address field blank.
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, see "Considerations for Choosing Unicast or Multicast" in Administering Clusters for Oracle WebLogic Server.
You can also create clusters using Fusion Middleware Control. In this case, you can configure cluster communication (unicast or multicast) when you create the new cluster. For more information, see "Create and configure clusters" in Oracle WebLogic Server Administration Console Online Help.
Tip:
For more information about options on this screen, see "Clusters" in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.14 Assigning Oracle Healthcare Managed Servers to the Cluster
Use the Assign Servers to Clusters screen to assign managed servers to the new cluster:
Description of the illustration GUID-BE2D2EF1-B35E-4A75-BE4E-2080069FECC0-default.gif
Tip:
For more about options on this screen, see"Assign Servers to Clusters" in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.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 you can assign to a Managed Server port number is 60535, instead of 65535.
See Table 6-2 for more information and next steps for configuring Coherence.
Note:
For Coherence licensing information, see Oracle Coherence in Licensing Information.
5.2.2.16 Creating a New Oracle Healthcare Machine
Use the Machines screen to create a new machine in the domain. A machine is required so that Node Manager can start and stop servers.
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.
Tip:
More information about the options on this screen can be found in "Machines" in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.17 Assigning Servers to Oracle Healthcare Machines
Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to the new machine you just created:
Description of the illustration GUID-774F523F-0010-437B-BE26-AC9BC41ABC0D-default.gif
Tip:
For more about options on this screen, see "Assign Servers to Machines" in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.18 Reviewing Your Configuration Specifications and Configuring the Domain
The Configuration Summary screen has detailed configuration information for the domain you are about to create. Review each item on the screen and verify that the information is correct.
To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane.
Domain creation does not start until you click Create.
Tip:
For more about options on this screen, see Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
5.2.2.19 Writing Down Your Domain Home and Administration Server URL
The Configuration Success screen shows the following items about the domain you just configured:
Domain Location
Administration Server URL
You must make a note of both items because you need them later; you need the domain location to access scripts that start Node Manager and Administration Server, and you need the URL to access the Administration Server.
Click Finish to dismiss the Configuration Wizard.
5.3 Starting the Servers
After 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.
5.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 this 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, Oracle recommends 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.
5.3.2 Starting the Administration Server
To start the Administration Server, go to the DOMAIN_HOME/bin directory.
On UNIX operating systems, run:
./startWebLogic.sh
On Windows operating systems, run:
startWebLogic.cmd
If you selected Production Mode on the Domain Mode and JDK screen in Specifying the Domain Mode and JDK, you see a prompt for the Administrator user login credentials as provided on the Administrator Account screen in Configuring the Administrator Account.
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 Writing Down Your Domain Home and Administration Server URL.
Note:
Make sure 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.
For more information about how to use the Administration Console, see Getting Started Using Oracle WebLogic Server Administration Console in Administering Oracle Fusion Middleware.
5.3.3 Starting the Managed Servers
To start the Managed Servers:
- The Enterprise Manager landing page lists the servers configured for this domain and displays their status (such as Running or Shutdown). For a newly configured domain, only the AdminServer(admin) will be running.
- Next to the WebLogic Server menu, select Start Up.
- On the main landing page, see that all the servers are up and running.
5.4 Verifying the Configuration
To verify that the domain is configured properly, see Performing Additional Domain Configuration Tasks. You should familiarize yourself with the tasks that this section describes and perform them to verify that your domain is properly configured.