FSM-Integration

FSM was originally called ‘Metrix’, and MPM stands for ‘Metrix Perform Method’.  MPMs are defined by a combination of metadata and C#.Net code and can be implemented in any .Net language compiled assembly.  Out of the box, there are numerous MPMs.  You can think of an MPM as an ‘RPC’ or ‘Remote Procedure Call’.  An MPM is a function the FSM server can perform, such as repricing a request, generating PM tasks, replenishing stock, posting a shipment, etc.  Each MPM has a name, and will accept various data as parameters.  MPM calls are made via XML messages to FSM.  See pages 14 and 32 in the attached document for explanation and examples of invoking an MPM.

You can also get parameter details for MPMs by going to Menu->Studio->Tools->XML Schemas, choose ‘Perform’ for Message Type and select the MPM you want to work with under Table Name.  Select the checkbox labeled ‘Return XML Example instead of Schema’ to see an example of the XML message to invoke the MPM.

The Perform Messages report mentioned in the attached document, and the Studio tool mentioned above will both only show MPMs which have metadata definitions.  There are numerous (nearly 70 to my knowledge) hard-coded baseline MPMs for which there is no metadata definition.  In order to get details about these, you either need to look at FSM source code, or perform user actions in the FSM client which invoke the MPM you’re interested in and then look in the XML log (JSON communication log if Web Client).  Some common built-in MPMs (not defined in metadata) are:

perform_fetch_global_code_table_values
perform_get_database_info
perform_get_server_info
perform_get_server_info_extended
perform_test_server

@Lee Pinchbeck is right.  This gets very complicated very quickly.  I hope I’ve helped answer your essential question.  MPMs are an intrinsic part of FSM, and you need to know the basics of what they do and how they are used in order to administer FSM and configure it to its maximum potential.