Page tree
Skip to end of metadata
Go to start of metadata

To manage messaging, you must first enable and configure the messaging system on the server. This includes:

  • Enabling the server as a listening port.
  • Starting the relevant system services and setting them to start automatically during the server boot process.
  • Adding system users and configuring their permissions.

 

 Enabling the messaging service

To enable the messaging service:

  1. Open Universal Console in a browser tab.
  2. Select Messaging. The Messaging Queue screen is displayed.
  3. Configure the queue as follows:
    • Enable on Start?: On
    • TCP Port:port_number

      • Replace port_number with the port number of the messaging server. As this tutorial is structured on a single messaging server, we will listen on the localhost loopback service. The default port number for this is 61616.
      • If you are sitting in instructor-led training with other users, your presenter will provide this information to you. If you get an error for the port number, try entering another port, with the number incremented by one. For example, 61617.
  4. Click Apply.
  5. Click Start and check that the service starts successfully.


Now that the messaging queue service is started, you can configure the system user that has permissions to access the messaging queue.

 Adding a system user and assigning them to a role

In order to access messages between Widget Ltd and Tucker Inc.’s ERP systems, you must create a user account that is common to all systems in the messaging process.

If you have downloaded the Community Edition of Universal Platform, you will not be able to create a user account. This is because the Community Edition only supports a single user. In this case, you can proceed by using the Administrator user account.


To add a user:

  1. Click Add. The User Details screen is displayed.
  2. On the General tab, configure the user as follows:
    • User Name: MessagingQueue_User
    • Email Address: mquser@null.com
    • Credential Provider: Universal Credential Provider
    • Password: Enter a password of your choice.

      Passwords cannot contain spaces but can contain special characters, such as @ and ‘.

       

  3. Click Save.

     

 

Now that you have added a user, you must assign them to a role.

Roles group permissions based on the responsibility users have in the system and determine the aspects of the system users have access to. By creating roles, you can quickly assign a set of permissions to a user, or quickly provide multiple users permissions to a task.

This role is used later in this tutorial by the messaging components to send and read messages in the queue. 

  1. Select the Roles tab.
  2. Select universal-users from the list in the Roles section.
  3. Click Add.
  4. Click Save & Close.

     

Now that you have configured the messaging service and created a common user account, the next step is to create the credentials for the user account to access the remote ERP systems.

 Connecting to remote systems

Since the ERP systems at Widget Ltd and Tucker Inc. are client systems that connect to the message queue on the server to submit or receive messages, you must create credentials for the user account to access these systems.

If you have downloaded the Community Edition of Universal Platform and you are using the Administrator account, you will still need to configure your User Credentials.


To configure credentials:

  1. Open Interface Manager in a browser tab.
  2. Select User Credentials. The User Credentials screen is displayed.
  3. Click Add and select User Credential.
  4. On the General tab, enter a name for the client connection credentials in the format: ClientLogin_User.
  5. Enter the name of the user account you created when you completed the Adding a system user and assigning them to a role task: MessagingQueue_User, in the User Name field in the User Credentials section.
  6. Enter the user’s password in the Password field.
  7. Click Save & Close.

     

Now that you have configured the messaging service and created a common user account with credentials to access client systems, the next step is to create the messaging components.

 And that's a wrap

And that’s a wrap - congratulations on completing this module! Before we finish, let’s have a quick look at what you have done:

  • No labels