About Configuring WebLogic

This section describes the configuration of WebLogic 12c with Oracle 11g Release 2 to run the SIMULIA Execution Engine.

The configuration procedures in this section assume that you created a user called seeadmin to control the configuration of the SIMULIA Execution Engine and that you installed the SIMULIA Execution Engine in the default installation directory. For more information, see Installing the SIMULIA Execution Engine Server.

About the seeadmin User

To configure the SIMULIA Execution Engine, you need to have a user called seeadmin, and this user must possess certain characteristics within your environment.

This user must be known within the target security realm of the user authentication registry. These security settings must be implemented or the SIMULIA Execution Engine deployment will fail. The remaining procedures in this section assume that you created the seeadmin user and have preconfigured the necessary security settings. If you create a user with a different name or use an existing user with a different name, with the proper security settings, keep this in mind when user information is presented.

For information on creating this user (on Windows systems) and for more details on the necessary preconfigured security settings, see Creating the seeadmin User on Windows.

For more information on creating this user in a Linux environment, contact your system administrator.

Deploying the SIMULIA Execution Engine in a Single-Server Standalone Configuration

You can deploy the SIMULIA Execution Engine application in a single-server, standalone configuration in which only the WebLogic Administration Server is used. For this option, you perform the following steps:

  1. Create the WebLogic domain using the administration server template provided in your SIMULIA Execution Engine installation. See Creating the WebLogic Domain Using the SIMULIA Execution Engine Administration Server Template.
  2. Edit the WebLogic environment file, as described in Editing the Environment File.
  3. Start the WebLogic Administration Server and access the WebLogic Administration Console through a web browser. See Starting the Administration Server.
  4. Configure client authentication for the SIMULIA Execution Engine within WebLogic, using an LDAP server. See Configuring Client Authentication.
  5. Deploy the Java EAR file, as described in Deploying the SIMULIA Execution Engine EAR File.
  6. Deploy any additional SIMULIA Execution Engine applications desired, such as the WebTop, WebDashboard, or Federation application. See Deploying the WebTop, WebDashboard, or Federation Applications.
  7. Configure the WebTop, WebDashboard, or Federation applications, as needed. See Configuring the WebTop and WebDashboard Applications.
  8. Stop and restart WebLogic as described in Stopping the SIMULIA Execution Engine Server, to force WebLogic and the SIMULIA Execution Engine to recognize the configuration changes.
  9. Configure the connection profile for the SIMULIA Execution Engine, as described in Configuring the Connection Profile.
  10. Preload the basic system metamodels for Isight and the SIMULIA Execution Engine, as described in Publishing to the Library.

Deploying the SIMULIA Execution Engine Using Multiple Servers

Alternatively, you can deploy the SIMULIA Execution Engine application and its web client UIs in multiple WebLogic servers, using WebLogic Managed Servers for each application. For this option, you perform the following steps:

  1. Create the WebLogic domain using the administration server template provided in your SIMULIA Execution Engine installation. See Creating the WebLogic Domain Using the SIMULIA Execution Engine Administration Server Template.
  2. Edit the WebLogic environment file, as described in Editing the Environment File.
  3. Start the WebLogic administration server and access the WebLogic Administration Console through a web browser. See Starting the Administration Server.
  4. Configure client authentication for the SIMULIA Execution Engine within WebLogic, using an LDAP server. See Configuring Client Authentication.
  5. Define a managed server for SIMULIA Execution Engine within the WebLogic Administration Server. See Creating a Managed Server Using the ServerTemplate.
  6. For a multiple-server domain, you must create a WebLogic domain on the computers that will host the managed servers. See Creating WebLogic Domains for Remote Managed Servers.
  7. Start the managed server for the SIMULIA Execution Engine, as described in Starting the Managed Servers.
  8. Deploy the Java EAR file, as described in Deploying the SIMULIA Execution Engine EAR File.
  9. Deploy any additional SIMULIA Execution Engine applications desired, such as the WebTop, WebDashboard, or Federation application. See Deploying the WebTop, WebDashboard, or Federation Applications.
  10. Configure the WebTop, WebDashboard, or Federation applications, as needed. See Configuring the WebTop and WebDashboard Applications.
  11. Stop and restart WebLogic as described in Stopping the SIMULIA Execution Engine Server, to force WebLogic and the SIMULIA Execution Engine to recognize the configuration changes.
  12. Configure the connection profile for the SIMULIA Execution Engine, as described in Configuring the Connection Profile.
  13. Preload the basic system metamodels for Isight and the SIMULIA Execution Engine, as described in Publishing to the Library.

Additional security options are available with your SIMULIA Execution Engine, including Run-As security and Access Control Lists (ACLs). For more information on these options, see Configuring Security.