The SIMULIA Execution Engine database employs a reliable asynchronous messaging infrastructure that is based on the JMS (Java Message Service) standard, which allows its application components to create, send, receive, and read messages. When a SIMULIA Execution Engine message is received from a JMS topic, the SIMULIA Execution Engine Server (J2EE) uses a credential map, also known as the J2EE RunAs Security model, to obtain the security identity (user name and password) used when establishing the JMS connection. This credential mapping occurs only once, and the JMS server uses the established security identity to retrieve all messages. The WebLogic SIMULIA Execution Engine application deployment descriptor has already been preconfigured with the seeadmin user, whose valid security identity (user name and password) must be known within the target security realm of the user authentication registry (such as LDAP). The seeadmin user is the assigned J2EE RunAs user, and its existence is required for the SIMULIA Execution Engine asynchronous messaging infrastructure to function properly. An additional requirement must also be adhered to when creating the seeadmin user. The user must either belong to the fiperuser global security role or be a member of your user authentication registry (such as LDAP) group that is mapped to the fiperuser global security role. For more information on configuring these settings, see Configuring Client Authentication. For further and detailed assistance on implementing these user security settings, especially with regard to working with your local user authentication registry, contact your local system administrator or WebLogic administrator. | ||||||||