Skip to main content

MSGIN

MSGIN is the name of the directory the SAP BW LSAM monitors for external events. The location of the MSGIN directory is <Configuration Directory>\SAP BW LSAM\MSGIN\ on the machine where the SAP BW LSAM is installed. Any external program or application can generate and place an ASCII file in this directory. These ASCII files must contain a valid OpCon event(s), User Login ID, and event password for the SAM to process the event(s).

note

The Configuration Directory is based on where you installed your programs. For more information, refer to File Locations in the Concepts online help.

The SAP BW LSAM watches the MSGIN directory for any text file. The SAP BW LSAM reads the file, passes the text to the SAM for processing, and finally the LSAM deletes the file. If the SAM receives an invalid event, the SAM documents the error in the SAM Critical.log file.

Placing a message into the MSGIN directory​

  1. Open an ASCII text editor (e.g., Notepad) on the Windows machine.

  2. Enter the following text:

    $JOB:RELEASE,[[$DATE]],ProdSched,ProdJob,BatchUser,EventPassword
    1. Place an OpCon User Login ID and an external event password on the end of the event. This password is not the same as the database password used to log in to the Enterprise Manager. Refer to External Events in the OpCon Events online help.
    2. The user must have the correct function privileges in OpCon for the SAM to perform the command contained in the external event.
    3. The only allowable tokens in an external event are $DATE, $TIME, and $NOW. These tokens pull values from the current system date and time.
    4. If multiple events are desired, enter a carriage return and enter another event on the next line.

  3. Save the file in the <Configuration Directory>\SAP BW LSAM\MSGIN\ directory.

  4. The SAP BW LSAM reads the file, sends the contents to the SAM, and finally deletes the file.

The SAM checks the user on the event, and then processes the command contained in the external event. If there are syntactical errors, the SAM discards the event and writes the message "Invalid Event" into the SAM Critical.log file.