Deploying UserExit through customization UI

About this task

Follow the steps to deploy UserExit through customization UI:

Carefully create a UserExit jar file. For details, refer to User Exits.
Restart the Sterling B2B Integrator server to install the jar. This will add the entry VENDOR_JAR to properties/dynamiclcasspath.cfg and properties/dynamiclcasspathAC.cfg (for containers).

Note: You can verify this in the dynamicclasspath.cfg file in the properties folder. An entry should be present with the userexit jar file name.
You can also validate the entry in the SftpServerUserExits.xml file present in installation folder/properties/userexit folder.
```
<bean
id="com.sterlingcommerce.woodstock.userexit.services.sftpserver.interfaces.ISftpServerUserExit_OnLSC
DBeforerExecute"
class="com.sterlingcommerce.woodstock.userexit.services.sftpserver.SftpServerUserExit">
<property name="implementations">
<list>
<value> com.sftpuserexit.test.SFTPUserExitLSFile_ChangePath</value>
</list>
</property>
<property name="generalParameters">
<props>
<prop key="return.on.exception">false</prop>
</props>
</property>
</bean>
```
Note: The custom classname entry which is highlighted in bold above should be present once a successful installation is complete.

Note: UserExit from customization UI supports only one type of interface (subtype) selection. If you need multiple interfaces in single UserExit, then create respective multiple UserExits entry from the customization UI for same userexit jar by selecting different interface (subtype).