User Exits

You can create, edit, or delete User Exits using Sterling B2B Integrator.

You can add User Exits using:

UI
APIs - For more information on REST APIs, see B2B REST APIs available in Sterling B2B Integrator.

The User Exits are stored in a database, which ensures maintainability across releases. No backup is required during an upgrade.

For UI, the User Exits are uploaded and deployed on all the nodes, whereas for APIs, they are uploaded and deployed only on specific nodes.

Important: You cannot delete the installed User Exits. You can delete User Exits in Installation Pending or Failed states only.

Note: The user exits that are saved is applicable to all the nodes in a cluster. For the user exits to take effect, you must restart Sterling B2B Integrator . Upon restarting ASI or Adapter Container node, the following dynamic classpath files are updated with the respective <dynamic class path file name>.in files.

dynamicclasspath.cfg
APPDynamicclasspath.cfg
AGENTDynamicclasspath.cfg
dynamic_os.sh