After you have installed Oracle SOA Suite for Healthcare Integration, you can configure the domain, which you can also extend for high availability.
Refer to the following sections to create the database schemas for Oracle SOA Suite for Healthcare Integration, configure a WebLogic domain for Oracle SOA Suite for Healthcare Integration, and verify the configuration.
Creating the Database Schemas
Before you can configure an Oracle B2B and SOA Suite for Healthcare Integration domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.
Installing and Configuring a Certified Database
Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.
Starting the Repository Creation Utility
Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system.
To start the RCU:
- Verify that a certified JDK already exists on your system by running
java -versionfrom the command line. For 12c (188.8.131.52.0), the certified JDK is 1.8.0_131 and later.
- Ensure that the
JAVA_HOMEenvironment variable is set to the location of the certified JDK. For example:
setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_131
- Change to the following directory:
- Enter the following command:
Navigating the Repository Creation Utility Screens to Create Schemas
Enter required information in the RCU screens to create the database schemas.
Introducing the RCU
The Welcome screen is the first screen that appears when you start the RCU.
Selecting a Method of Schema Creation
Use the Create Repository screen to select a method to create and load component schemas into the database.
If you have the necessary permissions and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have SYSDBA privileges.
If you do not have the necessary permissions 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 give to your database administrator. See About System Load and Product Load in Creating Schemas with the Repository Creation Utility.
If the DBA has already run the SQL script for System Load, select Perform Product Load.
Providing Database Connection Details
On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.
If you are unsure of the service name for your database, you can obtain it from the
SERVICE_NAMES parameter in the initialization parameter file of the database. If the initialization parameter file does not contain the
SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the
- Database Type: Oracle Database
- Host Name: examplehost.exampledomain.com
- Port: 1521
- Service Name: Orcl.exampledomain.com
- User Name: sys
- Password: ******
- Role: SYSDBA
Click Next to proceed, then click OK in the dialog window that confirms a successful database connection.
Specifying a Custom Prefix and Selecting Schemas for Oracle B2B and Healthcare
Specify a custom prefix and database schema to automatically select Common Infrastructure Services and dependent schemas.
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
Oracle Platform Security Services
Audit Services Append
Audit Services Viewer
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. 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.
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.
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.
Specifying Schema Passwords
On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.
You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.
Specifying Custom Variables
Specify the custom variables for the SOA Infrastructure schema.
For the Oracle SOA Suite standard installation topology, set values for the Database Profile (SMALL) and Healthcare Integration (NO for B2B installation, YES for Healthcare Integration for Oracle SOA Suite).
For more information about the options on this screen, see Custom Variables in Creating Schemas with the Repository Creation Utility.
Completing Schema Creation
Navigate through the remaining RCU screens to complete schema creation.
On the Map Tablespaces screen, the Encrypt Tablespace check box appears only if you enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU. Select the Encrypt Tablespace check box if you want to encrypt all new tablespaces that the RCU creates.
When you reach the Completion Summary screen, click Close to dismiss the RCU.
Configuring the Domain
Use the Configuration Wizard to create and configure a domain.
For 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.
Starting the Configuration Wizard
Start the Configuration Wizard to begin configuring a domain.
To start the Configuration Wizard:
- Change to the following directory:
ORACLE_HOMEis your 12c (184.108.40.206.0) Oracle home.
- Enter the following command:
Navigating the Configuration Wizard Screens to Create and Configure the Domain
Enter required information in the Configuration Wizard screens to create and configure the domain for the topology.
You can use this procedure to extend an existing domain. If your needs do not match the instructions in the procedure, be sure to make your selections accordingly, or see the supporting documentation for more details.
Selecting the Domain Type and Domain Home Location
Use the Configuration Type screen to select a Domain home directory location, optimally 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 details about this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
Selecting the Configuration Templates for Oracle SOA Suite for Healthcare Integration
Use the Templates screen to select the templates you require.
On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:
Oracle SOA Suite for healthcare integration - 220.127.116.11.0 [soa]
Selecting this template automatically selects the following as dependencies:
Oracle SOA Suite
Oracle Enterprise Manager
Oracle WSM Policy Manager
WebLogic Coherence Cluster Extension
For more information about this screen, see Templates in Creating WebLogic Domains Using the Configuration Wizard.
Selecting the Application Home Location
Use the Application Location screen to 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.
For more about the Application home directory, see About the Application Home Directory.
For more information about this screen, see Application Location in Creating WebLogic Domains Using the Configuration Wizard.
Configuring the Administrator Account
Use the Administrator Account screen to 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.
Specifying the Domain Mode and JDK
Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK).
On the Domain Mode and JDK screen:
Select Production in the Domain Mode field.
Select the Oracle HotSpot JDK in the JDK field.
Specifying the Database Configuration Type
Use the Database Configuration type screen to specify details about the database and database schema.
On the Database Configuration type screen, select RCU Data. This 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.
If you select Manual Configuration on this screen, you must manually fill in parameters for your schema on the next screen.
After selecting RCU Data, specify details in the following fields:
Enter the database DBMS name, or service name if you selected a service type driver.
Enter the name of the server hosting the database.
Enter the port number on which the database listens.
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 the 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.
For more information about the schema installed when the RCU is run, see About the Service Table Schema in Creating Schemas with the Repository Creation Utility.
See Database Configuration Type in Creating WebLogic Domains Using the Configuration Wizard .
Specifying JDBC Component Schema Information
Use the JDBC Component Schema screen to verify or specify details about the database schemas.
Verify that the values populated 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.
For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:
See JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard for more details about this screen.
Testing the JDBC Connections
Use the JDBC Component Schema Test screen to test the data source connections.
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 in the previous screen (JDBC Component Schema) 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.
For more information about this screen, see JDBC Component Schema Test in Creating WebLogic Domains Using the Configuration Wizard.
Selecting Advanced Configuration
Use the Advanced Configuration screen to complete the domain configuration.
On the Advanced Configuration screen, select:
Required to properly configure the listen address of the Administration Server.
Required to configure Node Manager.
Required to configure the Oracle B2B Managed Server.
Optionally, select other available options as required for your desired installation environment. The steps in this guide describe a standard installation topology, but you may choose to follow a different path. If your installation requirements extend to additional options outside the scope of this guide, you may be presented with additional screens to configure those options. For information about all Configuration Wizard screens, see Configuration Wizard Screens in Creating WebLogic Domains Using the Configuration Wizard.
Configuring the Administration Server Listen Address
Use the Administration Server screen to select the IP address of the host.
Select the drop-down list next to Listen Address and select the IP address of the host where the Administration Server will reside, or use the system name or DNS name that maps to a single IP address. Do not use
All Local Addresses.
Do not specify any server groups for the Administration Server.
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.
For more information about 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.
Configuring Managed Servers for Oracle Healthcare
Use the Managed Servers screen to configure Managed Servers.
On the Managed Servers screen, a new Managed Server named
hc_server1 is automatically created by default.
Note:When deployed on a SOA server, the default Managed Server name is
hc_server1. In this guide,
hc_server1is used to readily identify this Managed Server.
- 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.
- In the Server Groups drop-down list, make sure that SOA-MGD-SVRS is selected. This server group ensures that SOA and Oracle Web Services Manager (OWSM) services are targeted to the Managed Servers 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. See Application Service Groups, Server Groups, and Application Service Mappings in Domain Template Reference.
- Configuring a second Managed Server is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.
Click Add and select SOA-MGD-SVRS to create a second Managed Server named
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 Preparing Your Environment for High Availability.
These server names and will be referenced throughout this document; if you choose different names be sure to replace them as needed.
For more information about this screen, see Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
Configuring a Cluster for Oracle Healthcare
Use the Clusters screen to create a new cluster.
On the Clusters screen:
- Click Add.
hc_cluster1in 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. See Create and configure clusters in Oracle WebLogic Server Administration Console Online Help.
For more information about this screen, see Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Defining Server Templates
If you are creating dynamic clusters for a high availability setup, use the Server Templates screen to define one or more server templates for domain.
For steps to create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in High Availability Guide.
Configuring Dynamic Servers
If you are creating dynamic clusters for a high availability setup, use the Dynamic Servers screen to configure the dynamic servers.
If you are not configuring a dynamic cluster, click Next to continue configuring the domain.
Note:When you create dynamic clusters, keep in mind that after you assign the Machine Name Match Expression, you do not need to create machines for your dynamic cluster.
To create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in High Availability Guide.
Assigning Oracle Healthcare Managed Servers to the Cluster
Use the Assign Servers to Clusters screen to assign Managed Servers to a new configured cluster. A configured cluster is a cluster you configure manually. You do not use this screen if you are configuring a dynamic cluster, a cluster that contains one or more generated server instances that are based on a server template.
Note:All Managed Servers of a component type in the domain must belong to that cluster. For example, Oracle SOA Suite for Healthcare Integration domains support only a single Healthcare cluster inside each domain.
See About Dynamic Clusters for more on configured cluster and dynamic cluster terms.
On the Assign Servers to Clusters screen:
- In the Clusters pane, select the cluster to which you want to assign the Managed Servers; in this case,
- In the Servers pane, assign
hc_cluster1by doing one of the following:
Click once on
hc_server1to select it, then click the right arrow to move it beneath the selected cluster (
hc_cluster1) in the Clusters pane.
hc_server1to move it beneath the selected cluster (
hc_cluster1) in the clusters pane.
- Repeat to assign
For more information about this screen, see Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Configuring Coherence Clusters
Use the Coherence Clusters screen to configure the Coherence cluster.
Leave the default port number as the Coherence cluster listen port. After configuration, the Coherence cluster is automatically added to the domain.
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
See Table 6-2 for more information and next steps for configuring Coherence.
For Coherence licensing information, see Oracle Coherence Products in Licensing Information.
Creating a New Oracle Healthcare Machine
Use the Machines screen to create new machines in the domain. A machine is required so that Node Manager can start and stop servers.
To create a new Oracle Healthcare machine so that Node Manager can start and stop servers:
- Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX), then click Add to create a new machine.
- In the Name field, specify a machine name, such as
- In the Node Manager Listen Address field, select the IP address of the machine in which the Managed Servers are being configured.
You must select a specific interface and not
localhost. This allows Coherence cluster addresses to be dynamically calculated.
- Verify the port in the Node Manager Listen Port field.
- Repeat these steps to add more machines, if required.
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.
For more information about this screen, see Machines in Creating WebLogic Domains Using the Configuration Wizard.
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.
- In the Machines pane, select the machine to which you want to assign the servers; in this case,
- In the Servers pane, assign
hc_machine1by doing one of the following:
Click once on
AdminServerto select it, then click the right arrow to move it beneath the selected machine (
hc_machine1) in the Machines pane.
AdminServerto move it beneath the selected machine (
hc_machine1) in the Machines pane.
- Repeat these steps to assign all Managed Servers to their respective machines.
For more information about this screen, see Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
If you have a WebLogic Server Multitenant (MT) environment, you use the Virtual Targets screen to add or delete virtual targets. For this installation (not a WebLogic Server MT environment), you do not enter any values; just select Next.
For details about this screen, see Virtual Targets in Creating WebLogic Domains Using the Configuration Wizard.
The Partitions screen is used to configure partitions for virtual targets in WebLogic Server Multitenant (MT) environments. Select Next without selecting any options.
For details about options on this screen, see Partitions in Creating WebLogic Domains Using the Configuration Wizard.
Reviewing Your Configuration Specifications and Configuring the Domain
The Configuration Summary screen shows 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.
For more details about options on this screen, see Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
Writing Down Your Domain Home and Administration Server URL
The End of Configuration screen shows information about the domain you just configured.
Make a note of the following items because you need them later:
Administration Server URL
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.
Starting the Servers
After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers.
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.
Starting Node Manager
Change to the following directory:
setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_131
Enter the following command:
nm.outas an example output file:
nohup ./startNodeManager.sh >
LOG_DIRis the location of directory in which you want to store the log files.
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.
See Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.
Starting the Administration Server
Go to the
Enter the following command:
If you selected Production Mode on the Domain Mode and JDK screen when you created the domain, you see a prompt for the Administrator user login credentials as provided on the Administrator Account screen.
For more information about starting the Administration Server, see Starting and Stopping Administration Server 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 boot identity files, 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 End of Configuration screen (
http://administration_server_host:administration_server_port/console). The default Administration Server port number is
Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.
For more information about how to use the Administration Console, see Getting Started Using Oracle WebLogic Server Administration Console in Administering Oracle Fusion Middleware.
Starting the Managed Servers
To start the Managed Servers:
- Sign in to Oracle Fusion Middleware Control:
The Administration Server host and port number were in the URL on the End of Configuration screen (Writing Down Your Domain Home and Administration Server URL). The default Administration Server port number is
The login credentials were provided on the Administrator Account screen (Configuring the Administrator Account).
- 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.
Select the first Managed Server.
- Next to the WebLogic Server menu, select Start Up.
- Repeat Steps 3 and 4 to start all Managed Servers.
- On the main landing page, verify that all the Managed Servers are up and running.
Verifying the Configuration
After completing all configuration steps, you can perform additional steps to verify that your domain is properly configured.
To verify that the domain is configured properly, see Performing Additional Domain Configuration Tasks.