Frequently asked questions

Find answers to frequently asked questions about using Sterling™ Order Management System features.

  • Next-generation platformWhat are the general MQ information needed for configuring Agent/Integration server?

    Answer:

    Queue Connection Factory: AGENTobtain_QCF

    Initial Context Factory: File

    Provider URL: file:/opt/ssfs/jndi

    Queue Manager name: OM_QMGR

    MQ Userid: mqm

  • Next-generation platformWhat should I choose as the MQ port?

    Answer: MQ is open to connect from external systems on port 15443. This port cannot be client specific. This port is the allowed port that is opened by IBM and clients must connect to this port for any external integrations.

  • Next-generation platformWhat are the security-related details that I must be aware of?

    Answer: Access to MQ server within Sterling Order Management System environment is configured using Mutual Authentication. MQ server is secured with Digicert Signed CA certificate and Client Authentication. Client Authentication is a process by which users/clients securely access any services from a server by exchanging digital certificates. MQ is setup with Transport Layer Security 1.2.

  • Next-generation platformIs MQIPT supported?

    Answer: MQIPT is not installed in Sterling Order Management System environment and is not currently supported.

  • What is the default queue depth?

    Answer: 500000

  • What is the max message length?

    Answer: 2000000

  • What is the use case for persistent vs non-persistent queue?

    Answer: If a queue is persistent, messages will be present in the queue even after a restart or JVM crash. Otherwise, it is lost with the JVM. The queues that are used by most of the Sterling Order Management System agents need not be persistent. Even if a message is lost due to JVM crash, Sterling Order Management System can regenerate the message in the next iteration. But a message that is added directly by a user to a queue (by calling a sync service) is lost for ever. The SI has to submit it again. Similarly, when an external system adds the message to a queue, the regeneration logic is outside Sterling Order Management System. In such cases, considering the lack of regeneration possibility, IBM recommends you to use persistent queues.

    You can choose whether the queue is persistent or non-persistent in Self Service when you create a queue. By default, the queue is created as persistent. For more information about queues, see Managing queues.

  • What must be the message size?

    Answer: It is recommended to use a small message size.

  • Can I create a QMGR on Sterling Order Management System IBM MQ?

    Answer: Not supported.

  • Is IBM MQ explorer supported to test queue operations?

    Answer: IBM MQ explorer is not part of the offering.

  • What self-serve operations are supported for IBM MQ?

    Answer: See Self Service.

  • Are dead letter queues supported?

    Answer: No, dead letter queues are not supported.

  • How to check or gather IBM MQ logs?

    Answer: IBM MQ logs are maintained by IBM. If you need to collect IBM MQ logs, you must log a case with IBM® Support.

  • What message type is expected by Sterling Order Management System when a message is sent from the external system?

    Answer: Sterling Order Management System integration expects a message of type javax.jms.TextMessage from the external systems.

  • How to get the mq_key.arm file?

    Answer: You must log a case with IBM® Support.

  • Next-generation platformHow can I obtain IBM MQ certificate?

    Answer: Obtain the IBM MQ certificate from Self Service.

  • How do I import a third-party certificate to Sterling Order Management System?

    Answer: Run the Importing third-party certificates self-serve process.

  • What is the version of IBM MQ used in Sterling Order Management System?

    Answer: To view the IBM MQ version, run the Retrieving installation and version information self-serve process.

  • How do I drop a message of type javax.jms.TextMessage to IBM MQ?

    Answer: Refer to IBM MQ documentation on JMSTextMessage [Format: MQSTR, WMQConstants.MQFMT_STRING ].

  • How do I see the queue depth increasing?

    Answer: After you PUT a message to a queue, you can use the Manage queue - displayQueue self-serve process to view the changes in the queue depth.

  • How do I delete a queue that I used for testing only?

    Answer: In lower environments, once a queue is created there is no self-serve process to delete the queue. It is recommended that you create a different queue by using self-serve process instead of deleting. If you want to delete a queue in Production environment, you must log a case with IBM® Support.

  • How do I increase the queue depth, what is permitted?

    Answer: The default queue depth is 500000. The maximum permitted queue depth is 2000000.

  • How do I view a list of error codes?

    Answer: A list of error codes along with their explanations is available in the IBM MQ documentation.