Salesforce

Command Line Requester (Magic xpi 3.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Command Line Requester (Magic xpi 3.x)

The Command Line Requester is a requester management program that allows for:

  • Managing the Magic Request Broker and the Magic xpi projects* (to start and stop the MRB or Magic xpi projects)

  • Querying the Magic Request Broker regarding the status of specific requests that were issued to Magic xpi projects.

  • Querying the Magic Request Broker regarding the status of the Magic xpi projects.

*Note: When you run Magic xpi in multi-project mode, the Magic xpi project will be called IFSProjectName; otherwise, it will be IFS.

The Command Line Requester is activated by selecting the mgrqcmdl.exe file.

The Command Line Interface

The Magic Request Broker can be queried by using the Command Line requester. The Command Line requester is the mgrqcmdl.exe program, which can be run in a DOS-Prompt window. The Command Line requester uses the Mgreq.ini file to determine the address of the Magic Request Broker to which it communicates.

The full syntax tree for using the Command Line requester can be viewed by using the MGRQCMDL command without parameters.

Examples

  • To view the running Magic xpi projects that are available for service to the MRB, use the command:
    mgrqcmdl -query=rt

  • To load an additional Magic xpi project, use the command:
    mgrqcmdl -exe=AppName


    where AppName is the name of an entry in the [APPLICATIONS LIST] section of the Mgrb.ini file

  • To stop any Magic xpi project, use the command:
    mgrqcmdl - terminate=Address - timeout


    where Address is the MRB internal Magic xpi project’s host and port number (you can get this information from the query command result)

Note:

When using the command line, the application will only be loaded once, even if the mgrb.ini entry referred to here is set to load more than once.

When the Magic xpi project is instructed to terminate, it terminates gracefully without any new contexts being opened in the terminating project. Requests for a new context are directed to other available engines. If another engine cannot be found, the request is rejected. The terminating project continues to process existing contexts, and will terminate after the last context is properly closed or after the set timeout has passed.

When the timeout value equals zero, the server waits indefinitely to terminate. The timeout default value is zero.

Related Topics

How Do I Monitor Running Threads in Magic xpi Projects?

Reference
Attachment 
Attachment