Creating and configuring the WebLogic domain
- In a command shell, go to <Middleware_Home>/wlserver/common/bin. For example:
/u01/app/oracle/product/weblogic12c/Middleware/wlserver/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/weblogic12c/Middleware/user_projects/domains/empirica
where empirica is the domain name.
- Click Next.
The Templates page appears.
- Select Create Domain Using Product Templates.
- From the Template Categories drop-down list, select All Templates.
- From the Available Templates list, select the following templates:
- Basic WebLogic Server Domain - 12.1.3.0 [wlserver]
- 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]
- Click Next.
The Application Location page appears.
- Check the Domain name, Domain location, and Application location.
- Click Next.
The Administrator Account page appears.
- Type 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:
- 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—Type a value such as EMPIRICA_STB.
- Schema Password—Type the password that you used when you created the schema in Installing Oracle Fusion Middleware Repository Creation Utility (RCU) and creating repositories.
- Click Get RCU Configuration.
- Click Next.
The JDBC Component Schema page appears.
- Select all checkboxes.
- Click Next.
The JDBC Component Schema Test page appears.
- After all connections have been tested successfully, click Next.
The Advanced Configuration page appears.
- Select the following checkboxes:
- Administration Server
- Node Manager
- Managed Servers, Clusters and Coherence
- Deployments and Services
- Click Next.
The Administration Server page appears.
- Select Enable SSL.
- Specify SSL Listen Port 7002.
- Click Next.
The Node Manager page appears.
- Specify the domain 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 Machines list.
- Click Next.
The Deployments Targeting page appears.
- Assign a deployment to the AdminServer:
- In the list of Target Servers on the right, select AdminServer.
- If not already listed under AdminServer on the right, select the following Applications on the left and move them to the AdminServer target to augment the list of Applications:
- wsil-wls#12.1.3.0.0
- wsm-pm
- Assign a deployment to the SignalServer:
- In the list of Target Servers on the right, select SignalServer.
- Make sure only the following options appear on the right, under Application:
- wsil-wls#12.1.3.0.0
- wsm-pm
- Repeat step 40 for TopicsServer.
- If not already listed, add the following classes to SignalServer.
- From the Startup Class directory:
- JPS Startup Class
- JPS Startup Post-Activation Class
- JRF Startup Class
- From the JDBC System Resource directory, all services.
- From the Startup Class directory:
- Repeat step 42 for TopicsServer.
- Click Next.
The Configuration Summary page appears.
- Click Create.
The Configuration Progress page appears.
When the configuration is complete, a message appears stating that the domain has been created.
- Click Next.
The Configuration Success page appears.
- Click Finish.
Copyright © 2002, 2017 Oracle and/or its affiliates. All rights reserved.