Create and configure Oracle WebLogic Server domain 12c

Follow these steps to create and configure Oracle WebLogic Server domain 12c.

1. In a command shell,

   go to <Middleware_Home>/wlserver/common/bin. For example:

   /u01/app/oracle/product/Middleware12c/oracle_common/common/bin

2. 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 Oracle Fusion Middleware Configuration Wizard is launched.

3. 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.

4. Click Next.

   The Templates page appears.

5. Select Create Domain Using Product Templates.
6. From the Available Templates list, select the following templates:
   • Basic WebLogic Server Domain [wlserver]
   • Oracle Enterprise Manager [em]
   • Oracle WSM Policy Manager [oracle_common]
   • Oracle JRF [oracle_common]
   • WebLogic Coherence Cluster Extension [wlserver]
7. Click Next.

   The Application Location page appears.

8. Check the Domain name, Domain location, and Application location.
9. Click Next.

   The Administrator Account page appears.

10. Enter a user name and password for Oracle WebLogic Server administration.
11. Click Next.

    The Domain Mode and JDK page appears.

12. Select Production and check the JDK location.
13. Click Next.

    The Database Configuration Type page appears.

14. Select RCU Data.
15. 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.
16. Click Get RCU Configuration, then click Next.

    The JDBC Component Schema page appears.

17. Select all checkboxes and click Next.

    The JDBC Component Schema Test page appears.

18. Click Next.
19. After all connections have been tested successfully, click Next.

    The Advanced Configuration page appears.

20. Select the following checkboxes:
    • Administration Server
    • Node Manager
    • Topology
    • Deployments and Services
21. Click Next.

    The Administration Server page appears.

22. Select Enable SSL and specify 7002 for SSL Listen Port.
23. Click Next.

    The Node Manager page appears.

24. Select Per Domain Default Location and enter node manager credentials.

    Note:

    Keep the node manager credentials for future reference.
25. Click Next.

    The Managed Servers page appears.

26. 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
27. 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
28. Click Next.

    The Clusters page appears.

29. Click Next.

    The Server Templates page appears.

30. Click Next.

    The Coherence Clusters page appears.

31. Click Next.

    The Machines page appears.

32. Select the Unix Machine tab.
33. 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
34. Click Next.

    The Assign Servers to Machines page appears.

35. From the Servers list, select SignalServer and TopicsServer and move them to the SignalMachine in the Machines list.
36. Click Next.

    The Virtual Targets page appears.

37. Click Next.

    The Partitions page appears.

38. Click Next.

    The Deployments Targeting page appears.

39. Assign a deployment to the AdminServer:
    1. In the list of Target Servers on the right, select AdminServer.
    2. 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.
    3. 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.
40. To assign a deployment to the SignalServer, perform the following:
    1. In the list of Target Servers on the right, select SignalServer.
    2. Assign the wsm-pm application to the server.
    3. Assign the oracle.wsm.idmrest.sharedlib library to the server.
41. Repeat Step 39 for TopicsServer.
42. Click Next.

    The Services Targeting page appears.

43. If not already listed, add the following services to the SignalServer:
    • From JDBCSystemResource: mds-owsm
    • From the Startup Class directory: JRF Startup Class
44. Repeat Step 43 for TopicsServer.
45. Click Next.

    The Configuration Summary page appears.

46. Click Create.

    The Configuration Progress page appears.

    When the configuration is complete, a message appears stating that the domain has been created.

47. Click Next.

    The End of Configuration page appears.

48. Click Finish.