Create and configure WebLogic domain 12c
- In a command shell, go to <Middleware_Home>/wlserver/common/bin. For example:
/u01/app/oracle/product/Middleware12c/oracle_common/common/bin
- Execute the following command:
$ ./config.sh
Note: If you get a permission error, change permissions on config.sh to chmod u+x config.sh.
The Fusion Middleware Configuration Wizard is launched.
- Select Create a new domain and specify the domain location, for example:
/u01/app/oracle/product/Middleware12c/user_projects/domains/empirica
where empirica is the domain name.
- Click Next.
The Templates page appears.
- Select Create Domain Using Product Templates.
- From the Available Templates list, select the following templates:
- Basic WebLogic Server Domain - 12.2.1.3.0 [wlserver]
- Oracle Enterprise Manager - 12.2.1.3.0 [em]
- Oracle WSM Policy Manager - 12.2.1.3 [oracle_common]
- Oracle JRF - 12.2.1.3.0 [oracle_common]
- WebLogic Coherence Cluster Extension - 12.2.1.3.0 [wlserver]
- Click Next.
The Application Location page appears.
- Check the Domain name, Domain location, and Application location.
- Click Next.
The Administrator Account page appears.
- Enter a user name and password for WebLogic administration.
Note: You will use these credentials to administer the WebLogic instance.
- Click Next.
The Domain Mode and JDK page appears.
- Select Production and check the JDK location.
- Click Next.
The Database Configuration Type page appears.
- Select RCU Data.
- Enter the database connection details as follows:
- Vendor—Select Oracle.
- Driver—Select the Oracle thin driver for service connections.
- DBMS/Service—Use the service name for your database.
- Host Name—Use your database host name.
- Port—Specify the port number for the Oracle database service.
- Schema Owner—Enter a value such as EMPIRICA_STB.
- Schema Password—Enter the password that you used when you created the schema in Install Oracle Fusion Middleware Repository Creation Utility (RCU) and create repositories.
- Click Get RCU Configuration, then click Next.
The JDBC Component Schema page appears.
- Select all checkboxes and click Next.
The JDBC Component Schema Test page appears.
- Click Next.
- After all connections have been tested successfully, click Next.
The Advanced Configuration page appears.
- Select the following checkboxes:
- Administration Server
- Node Manager
- Topology
- Deployments and Services
- Click Next.
The Administration Server page appears.
- Select Enable SSL and specify 7002 for SSL Listen Port.
- Click Next.
The Node Manager page appears.
- Select Per Domain Default Location and enter node manager credentials.
Note: Keep the node manager credentials for future reference.
- Click Next.
The Managed Servers page appears.
- Click Add and create a server with the following details:
- Server Name—SignalServer
- Listen Address—<the full name of the application server>
- Listen Port—7003
- Enable SSL—<selected>
- SSL Listen Port—7004
- Server Groups—Unspecified
- Click Add and create a server with the following details:
- Server Name—TopicsServer
- Listen Address—<the full name of the application server>
- Listen Port—7005
- Enable SSL—<selected>
- SSL Listen Port—7006
- Server Groups—Unspecified
- Click Next.
The Clusters page appears.
- Click Next.
The Coherence Clusters page appears.
- Click Next.
The Machines page appears.
- Select the Unix Machine tab.
- Click Add and create a machine with the following details:
- Name—SignalMachine
- Node Manager Listen Address—<the full name of the application server>
- Node Manager Listen Port—5556
- Click Next.
The Assign Servers to Machines page appears.
- From the Servers list, select SignalServer and TopicsServer and move them to the SignalMachine in the Machines list.
- Click Next.
The Virtual Targets page appears.
- Click Next.
The Partitions page appears.
- Click Next.
The Deployments Targeting page appears.
- To assign a deployment to the AdminServer, perform the following:
- In the list of Target Servers on the right, select AdminServer.
- If not already listed under AdminServer / AppDeployment on the right, select the wsm-pm AppDeployment on the left and move it to the AdminServer target to augment the AppDeployment list.
- If not already listed under AdminServer / Library on the right, select the oracle.wsm.idmrest.sharedlib Library on the left and move it to the AdminServer target to augment the Library list.
- To assign a deployment to the SignalServer, perform the following:
- In the list of Target Servers on the right, select SignalServer.
- Assign the wsm-pm application to the server.
- Assign the oracle.wsm.idmrest.sharedlib library to the server.
- To assign a deployment to the TopicsServer, repeat the sequence of actions in the previous step.
- Click Next.
The Services Targeting page appears.
- If not already listed, add the following services to the SignalServer:
- From JDBCSystemResource—mds-owsm
- From the Startup Class directory—JRF Startup Class
- If not already listed, repeat the sequence of actions in the previous step to add the same services to the TopicsServer.
- Click Next.
The Configuration Summary page appears.
- Click Create.
The Configuration Progress page appears.
- Click Next.
The End of Configuration page appears.
- Click Finish.