...
1. On computer <msg_database_computer>, create a database instance <msg_database>; see
○ Database Manager GUI, Creating a Database Instance
○ Database Manager CLI, db_create
This database instance does not have to be on the same computer as the message server.
The Synchronization Manager uses the database instance <msg_database> as a message database instance for the message server.
How large you configure the data area of this database instance to be depends on the following factors, among others: the scope of data changes, the number of database instances involved, and the amount of time synchronization messages remain on the message server before all the database instances have retrieved the changes.
For the General Database
Parameter MAXUSERTASKS, we recommend configuring a value >
50.
When you create a database instance, you define the database system administrator <sysdba_user>.
2. You create the synchronization user in the message database instance.
See Database Manager GUI, Creating/Changing/Deleting a Synchronization User
3. To configure the message server, enter the following command on the computer on which you want to run the message server:
<independent_program_path>\bin\msgserver config
This starts the interactive configuration program of the message server.
4. Depending on your system environment, the configuration program requests some or all of the following information:
1. Directory in which your Java installation is located
2. Directory in which the j2ee.jar file is located
3. Computer <msg_database_computer> on which the message database instance is located
4. Name of the message database instance <msg_database>
○ Name and password of the synchronization user
○ Administration password for the message server
You can choose this password yourself.
○ Administration port <msgsrv_admin_port> for the message server (default value: 7220), JNDI port <jndi_port> (default value: 7221), JMS port <jms_port> (default value: 7222).
If these ports are already in use on your computer, use other ports. To find out which ports are already in use, enter the following command: netstat -a
See also: