Configure extensibility hooks on multiple middleware servers

The Middleware Extensibility Hooks are configured in the Extensibility Hooks tab in the Middleware Configuration Editor, and the hooks configurations are stored in the same folder in the file MWDBMappingsCustom.xml. The MES Middleware Server loads the Extensibility Hooks only if the hook parameters are configured in the MWDBMappingsCustom.xml file in its folder. When there is more than one Middleware Server configured to connect to the same MES database, then the end user is responsible for managing the hook configurations and keeping them in sync across all the Middleware Servers.

For example, let’s say Middleware Server 1 has a pre-hook configured for the sp_I_Uom (Uom.Add) to perform a pre-action before the actual sp_I_Uom is executed. Middleware Server 2 has a pre-hook configured for the sp_U_Job_Exec_StartBatchJobs (Job_Exec.StartJob) to perform a pre-action before the actual sp_U_Job_Exec_StartBatchJobs is executed. These two Middleware Servers are configured to connect to the same MES database, and these two are the only two hooks configured in their respective middleware directories.

The table below explains how the pre-hook commands are processed by both the Middleware Servers using the example above:

The Middleware Server 1 processes the pre-hook for sp_I_UOM before calling the sp_I_Uom stored procedure on the MES database, but does not process the pre-hook for sp_U_Job_Exec_StartBatchJobs before calling this stored procedure, because Middleware Server 1 does not know anything about the pre-hook for sp_U_Job_Exec_StartBatchJobs, since the XML file in its folder does not have any information about the hook for sp_U_Job_Exec_StartbatchJobs.

Similarly, the Middleware Server 2 processes the pre-hook for sp_U_Job_Exec_StartBatchJobs before calling the sp_U_Job_Exec_StartBatchJobs stored procedure on the MES database, but does not process the pre-hook for sp_I_UOM before calling this stored procedure.