Sending Events to a Remote WebLogic JMS Server

When an event is triggered, the P6 Event Notification system sends the event message to a message queue. If you are using a remote JMS server, then you must configure the local and remote servers to receive these notifications.

The following procedure should be used when the queue is on a different domain than P6. For information about setting up other JMS-based servers, see the vendor documentation.

Note: If you are configuring the WebLogic messaging queue in a cluster, ensure that you have targetted the JMS server to a migratable target. See: Targeting the JMS Server to a Migratable Target

To send events to a remote WebLogic JMS server:

  1. Start the WebLogic Configuration Wizard.
  2. In the wizard, create a WebLogic domain on the remote server to which you will be sending the events. See Creating a WebLogic Domain on a Remote or Local Server.
    • Note: Rename the WebLogic administration server to a name that is different from the name you used to deploy the P6 application. For example, RemoteAdminServer.
  3. Start the new server and launch the WebLogic Administration Console. The new server will act as the remote server.
  4. In the WebLogic Administration Console:
    1. Create a WebLogic message queue.
      1. Create a new JMS server. See Creating a JMS Server and Persistence Store.
      2. Create a JMS module. See Creating a JMS Module.
      3. Create a connection factory. See Creating a JMS Connection Factory.
      4. Create a new queue or topic. See Creating a JMS Message Queue and Subdeployment to see how to create a queue.

        Note: Create a queue to deliver a message to a specific group of users. Create a topic to distribute a message amongst several users.

    2. Configure the trust relationship on the remote server. See Configuring a Trust Relationship.
  5. Create a WebLogic domain on the local server from which the events will be sent. See Creating a WebLogic Domain on a Remote or Local Server.
  6. Start the local server and launch the WebLogic Administration Console.
  7. In the WebLogic Administration Console:
    1. Target the JMS Server to a migratable target. See Targeting the JMS Server to a Migratable Target
    2. Create a new JMS server. See Creating a JMS Server and Persistence Store.
    3. Create a JMS module. See Creating a JMS Module.
    4. Create a foreign server. See Creating a Foreign JMS Server.
    5. Configure the trust relationship on the local server. You must use the same credentials that were used on the remote server. See Configuring a Trust Relationship.
  8. Restart both Weblogic Administration Console servers (restart the domains, not the machines).
  9. If it is not already installed, install P6 EPPM Web Services or P6 on the local server.
  10. Launch P6 to configure message queue settings and event notification options. See Configuring Eventing in the Primavera P6 Administrator. The values you enter in the Directory Service and Eventing sections of the P6 Application Settings Eventing page should be the the Local JNDI names of the Destination and the Connection Factory in the Foreign JMS Server.


Legal Notices | Your Privacy Rights
Copyright © 1999, 2020

Last Published Monday, September 27, 2021