Creating and configuring the WebLogic domain
The Empirica Signal application requires a WebLogic domain that includes Enterprise Manager and is configured for Web Service security. You can either create a new WebLogic domain or extend an existing WebLogic domain. This procedure describes how to create a new WebLogic domain.
Use the same user account that you used when you installed WebLogic.
- In a command shell, type the following command:
$ cd /u01/app/oracle/product/Middleware/wlserver_10.3/common/bin
- Type the following command:
$ ./config.sh &
The Welcome page appears.
- Select Create a new WebLogic domain, and click Next.
The Select Domain Source page appears.
- Select Generate a domain configured automatically to support the following products, and select the following products:
- Oracle Enterprise Manager - 11.1.1.0 [oracle_common]
- Oracle WSM Policy Manager - 11.1.1.0 [oracle_common]
- Oracle JRF - 11.1.1.0 [oracle_common]
- Click Next.
The Specify Domain Name and Location page appears.
- Type a domain name, such as empirica, and click Next.
The Configure Administrator User Name and Password page appears.
- Type a user name and password for WebLogic administration.
Note: Remember these credentials. You use them to administer the WebLogic instance.
- Click Next.
The Configure Server Start Mode and JDK page appears.
- In the WebLogic Domain Startup Mode section, select Production Mode.
- In the JDK Selection section, select Available JDKs, and then select the 1.7.x_xx JDK that is specified in the system requirements in the Empirica Signal Release Notes.
- Click Next.
The Configure JDBC Component Schema page appears.
- In the table at the bottom, select the OWSM MDS schema.
- Fill in the following fields:
- From the Driver drop-down list, select the driver for either a service or instance connection.
- For DBMS/Service, type the appropriate value for the driver you selected:
- If the name of the driver contains the words for Instance connections, type the SID.
- If the name of the driver contains the words for Service connections, type the service name.
- For Schema Owner, type a value, such as EMPIRICA_MDS.
- For Schema Password, type the password that you created when you created the schema in Installing RCU and creating repositories.
- Click Next.
The Test JDBC Component Schema page appears.
- Click Next.
The Select Optional Configuration page appears.
- Select the following options:
- Administration Server
- Managed Servers, Clusters and Machines
- Deployments and Servers
- Click Next.
The Configure the Administration Server page appears.
- Select SSL enabled, and for SSL listen port, type 7002.
- Click Next.
The Configure Managed Servers page appears.
- Click Add.
A row in the table becomes editable.
- Select SSL enabled, and fill in the fields as follows:
- Name—Type SignalServer
- Listen address—Type the fully qualified name of the application server.
- Listen port—Type 7003.
- SSL listen port—Type 7004.
- Repeat the above steps starting at step 20 to create another Managed Server named TopicsServer and set the listen ports to 7005 and 7006, respectively.
- Click Next.
The Configure Clusters page appears.
- Click Next.
The Configure Machines page appears.
- Select the Unix Machine tab.
- Click Add.
A row in the table becomes editable.
- Fill in the fields as follows:
- Name—Type SignalMachine.
- Node manager listen address—Type the fully qualified name of the application server.
- Node manager listen port—Type 5556, if the value is not already present.
- Click Next.
The Assign Servers to Machines page appears.
- In the right list of machines, select SignalMachine.
- In the left list of servers, select SignalServer, and click the right arrow button. Repeat the process to move the TopicsServer to the right as well.
- Click Next.
The Target Deployments to Clusters or Servers page appears.
- Assign deployments to the AdminServer:
- In the list of target servers on the left, select AdminServer.
- Deselect the FMW Welcome Page entry, and make sure all other entries are selected.
- Assign deployments to the SignalServer and TopicsServer:
- In the list of target servers on the left, select SignalServer.
- Deselect the FMW Welcome Page entry.
- Select the following options, if they are not already selected, and make sure all other options are not selected:
- wsil-wls
- wsm-pm
- Repeat steps a through c for the TopicsServer.
- Click Next.
The Target Services to Clusters or Servers page appears.
- In the list of target servers on the left, select SignalServer.
- In the list of services on the right, select the following services, if they are not already selected:
- JRF Startup Class
- JPS Startup Class
- JDBC, as well as all of its child options.
- Repeat steps 36 and 37 for the TopicsServer.
- Click Next.
The Configuration Summary page appears.
- Click Create.
The Creating Domain page appears.
- When progress reaches 100 percent, click Done.
The wizard closes.
- Store your WebLogic administrator credentials so that you are not prompted for your credentials when you start WebLogic:
- In the command shell, navigate to the AdminServer directory under the empirica domain. For example, navigate to the following location:
/u01/app/oracle/Middleware/user_projects/domains/empirica/servers/AdminServer/
- If the security directory does not exist, create it.
- Using a text editor, edit the boot.properties file in the security directory. This step creates the file, if it does not already exist.
- Type the following lines in the file, providing the user name and password that you created when you created and configured the WebLogic domain.
username=
<weblogic_admin_user>password=
<weblogic_admin_password> - Save the file, and close the text editor.
- In the command shell, navigate to the AdminServer directory under the empirica domain. For example, navigate to the following location:
Copyright © 2002, 2017 Oracle and/or its affiliates. All rights reserved.