Chapter 8 Setting up the Message Service

Configuring the message service

Before you use the message service to send and receive messages, configure the service and install the message service parts. Once you configure the message service, it is available to every server that you create.

Configuring the message service using the Configure Message Service wizard

You can enable the message service and configure the connection cache properties using the Configure Message Service wizard.

1. In Jaguar Manager, highlight the Message Service folder, and select File | Configure Message Service.
   
   Or, if you double-click the Message Service folder, a message box asks if you want to configure the message service. To start the wizard, select yes .
2. Select the server for which you want to configure the message service, and choose Next.
   
      The Configure Message Service wizard adds "CtsComponents/MessageService" to the com.sybase.jaguar.server.services property in the /Repository/Server/<server_name>.props file. Once you have configured the message service, you can enable it for another server either by adding this value to the server's .props file, or by using the wizard.
   
3. Enter a connection cache name or select one from the list, and choose Next.
   
   By default, the message service uses the preconfigured "JavaCache." If you change the message service cache, set it to the name of a JDBC connection cache that allows cache-by-name access.
   
   If you configure the message service to use JavaCache, start the jagdemo database using the start_sampledb (UNIX) or jagdemo.bat (Windows), which is located in the EAServer bin subdirectory.
   
      Do not use sun.jdbc.odbc.JdbcOdbcDriver as the database driver for your message service connection cache. This driver does not work correctly when accessing binary column data.If you are using a Sybase ASA or Adaptive Server Enterprise database, set these values:
   • Database Driver - com.sybase.jdbc2.jdbc.SybDriver
   • Server Name - jdbc:sybase:Tds:host:2638
   
   
4. Optionally, edit the connection cache properties, and test the connection using ping. You must have a working connection to use the message service.
5. Select Finish. A message box asks if you want to restart the server. To enable the message service, select yes .

Configuring message service database, debugging, and cluster options

1. Use a text editor to make these changes to the MessageServiceConfig.props file, located in the EAServer /Repository/Component/CtsComponents directory:
   • To enable the JCM_FORCE option for access to the connection cache, change cms.force=false to cms.force=true .
   • To enable message service debugging at server start-up, change cms.debug=false to cms.debug=true .
   • If your database server does not accept the default syntax, change the SQL commands in the XX.YYYYYY statements. If the database does not have an image type, change image to unbounded (large) binary. If the database driver cannot handle character-set conversions, change the datatype of the varchar columns in the SQL schemas to varbinary.
2. If your server is in a cluster:
   • For each server in the cluster, copy MessageServiceConfig.props to $JAGUAR/Repository/Component/CtsComponents.
   • Synchronize the cluster. See Chapter 6, "Clusters and Synchronization"
3. Restart EAServer. Message service starts automatically when you start the server.

Copyright © 2002 Sybase, Inc. All rights reserved.