Configuring the environment for a custom sender or formatter

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 10, “Customizing the Sender and Formatter Processors,” for more detailed information about using the custom sender and formatter features.

StepsConfiguring an 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 the full path name to the jar file containing the customized sender processor or message formatter class or classes for the Java Classes property in EAServer’s server configuration property:

  1. Start EAServer Manager jagmgr.bat (Windows) or jagmgr (UNIX) which resides under the EAServer's installation's bin directory.

  2. Select Jaguar Manager.

  3. Select Tools | Connect

    The Login window displays.

  4. Enter the user name, password, host name, and port number to connect to your EAServer.

    By default, the user name is “jagadmin” with no password, the host name is “localhost” and the port number is 9000.

  5. Click Connect to connect to EAServer.

  6. Select Servers to expand the folder.

  7. Right-click Jaguar and select Server Properties. The Server Properties window displays.

  8. Select the Java Classes tab.

  9. Click Add to add the SenderProcessor/Formatter jar file. A row is added to the Java Classes.

  10. Enter the full path to the jar file containing the sender processor/message formatter classes.

    For example, at the command line, enter:

  11. Click OK to save the value.

  12. To effect the changes, restart your application server.

StepsConfiguring a WebLogic for a custom sender processor or custom formatter

To configure your environment if you are running RepConnector on WebLogic Server:

  1. Verify that the CLASSPATH variable setting in the repra_env.bat (for Windows) or repra_env.sh (for UNIX) includes the full path of the jar file containing the customized sender processor or message formatter classes.

  2. To effect the changes, restart your Weblogic Server.