Create and configure WebLogic domain 12c

Previous Topic

Next Topic

Book Contents

Create and configure WebLogic domain 12c

  1. In a command shell, go to <Middleware_Home>/wlserver/common/bin. For example:

    /u01/app/oracle/product/weblogic12c/Middleware/wlserver/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 Fusion Middleware Configuration Wizard is launched.

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

  4. Click Next.

    The Templates page appears.

  5. Select Create Domain Using Product Templates.
  6. From the Template Categories drop-down list, select All Templates.
  7. 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]
  8. Click Next.

    The Application Location page appears.

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

    The Administrator Account page appears.

  11. Enter a user name and password for WebLogic administration.

    Note: You will use these credentials to administer the WebLogic instance.

  12. Click Next.

    The Domain Mode and JDK page appears.

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

    The Database Configuration Type page appears.

  15. Select RCU Data.
  16. 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—Enter a value such as EMPIRICA_STB.
    • Schema Password—Enter the password that you used when you created the schema in Installing Oracle Fusion Middleware Repository Creation Utility (RCU) and create repositories.
  17. Click Get RCU Configuration.
  18. Click Next.

    The JDBC Component Schema page appears.

  19. Select all checkboxes.
  20. Click Next.

    The JDBC Component Schema Test page appears.

  21. After all connections have been tested successfully, click Next.

    The Advanced Configuration page appears.

  22. Select the following checkboxes:
    • Administration Server
    • Node Manager
    • Managed Servers, Clusters and Coherence
    • Deployments and Services
  23. Click Next.

    The Administration Server page appears.

  24. Select Enable SSL.
  25. Specify SSL Listen Port 7002.
  26. Click Next.

    The Node Manager page appears.

  27. Specify the domain location and enter node manager credentials.

    Note: Keep the node manager credentials for future reference.

  28. Click Next.

    The Managed Servers page appears.

  29. 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
  30. 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
  31. Click Next.

    The Clusters page appears.

  32. Click Next.

    The Coherence Clusters page appears.

  33. Click Next.

    The Machines page appears.

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

    The Assign Servers to Machines page appears.

  37. From the Servers list, select SignalServer and TopicsServer and move them to the Machines list.
  38. Click Next.

    The Deployments Targeting page appears.

  39. 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
  40. 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
  41. Repeat step 40 for TopicsServer.
  42. Click Next.
  43. 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.
  44. Repeat step 42 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 Configuration Success page appears.

  48. Click Finish.
Send Feedback