This section provides instructions for setting up the RepConnector environment so that RepConnector can load customized classes for message transformation or message destination routing.
Sybase recommends that you configure your environment before you proceed with configuring the RepConnector connection.
See Chapter 7, “Customizing the Sender and Formatter Processors,” for detailed information about using the custom sender and formatter features.
Configuring EAServer for a custom sender or formatter
processor
If you are running RepConnector on EAServer and plan to use a customized sender or formatter processor, define, in the EAServer server configuration property, the full path name to the jar file that contains the customized sender processor, the message formatter class, or the classes for the Java Classes property:
Log in to the EAServer Management Console.
On the General tab of the server property pages in the console, add the full path, along with your custom jar file, to the Java Class Path field. You can abbreviate the EAServer home directory by using “~”, for example, “~/repra/cust.jar.” See the EAServer 6.0 System Administration Guide for more information.
On the General tab of the Application.sybaserepconnector15, Class Loader page, add the full path, along with your custom jar file, to the Class Path field. You can abbreviate the EAServer home directory using “~”; for example, “~/repra/cust.jar.”
Shut down EAServer and restart it.
Configuring a WebLogic Server for a custom sender
processor or formatter
Verify that the CLASSPATH variable setting in the repra_env.bat file on Windows, or the repra_env.sh file on UNIX, includes the full path of the jar file containing the customized sender processor or message formatter classes.
On Windows:
CLASSPATH=D:\bea\repra\sample\client\sample.jar;%CLASSPATH%
On UNIX:
CLASSPATH=/work/bea/repra/sample/client/sample.jar:$CLASSPATH
Restart your WebLogic Server.
