Alexey,

as stated before, it is not a good idea to refer
to the pdf's in /opt/sdb/programs/app/syncman/doc/
unless you know exactly what you are doing.

>We can't start sync manager from SAP's example without any 
>modifications. We always get the following error
>Removing option -A in syncman_caller.py solved the problem.

Did you modify  'MSGSERVER.xml' ?
If so, revert this file to its original state.
Then it should not be necessary to experiment with
the internals of Synchronization Manager.

Escpecially, removing the '-A' option from 
the Python caller breaks the entire 
Synchronization Manager installation.

regards,

Markus

-----Original Message-----
From: Alexey Gaidukov [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 12, 2006 2:19 AM
To: Stausberg, Markus
Cc: maxdb@lists.mysql.com
Subject: Re: sync manager documentation error

/opt/sdb/programs/app/syncman/doc/RunningTheMEssageServer.pdf
section 1.4

A password to administrate the Message Server can be set in the section 
AdminPassword or by the command
line option -msgserver_password. Alternatively the Database credentials 
and the Message Server Admin
Password can be obtained with the option -A from the SyncMan Access File.

That is all what we found about option -A.

We can't start sync manager from SAP's example without any 
modifications. We always get the following error

msgserver start
com.sap.sdb.msgServer.util.ServerException: conflicting specifications: 
database url, database user name, database password, admin password, or 
one of the ports conflicts with database key.
at com.sap.sdb.msgServer.Server.(Server.java:254)
at com.sap.sdb.msgServer.Server.main(Server.java:134)
com.sap.sdb.msgServer.util.ServerException: conflicting specifications: 
database url, database user name, database password, admin password, or 
one of the ports conflicts with database key.


Removing option -A in syncman_caller.py solved the problem.


Stausberg, Markus пишет:
> Hello Alexey,
>
> First of all,
> there  are two different approaches to configure and run the
> Synchronization Manager programs:
>
> a) using the wrapper scripts which are provided in the 
> '<independent program path>/bin' directory. This approach is documented
> in
> the MaxDB documentation (which can be read and downloaded from the
> MySQL/MaxDB website). Also, a walkthrough example can be found after
> MaxDB
> installation  in '<independent program path>/app/syncman/example' .
> Using this approach, it is not necessary to modify any of the resources
> under '<independent program path>/app/syncman'. 
>
> b) it is possible to start the syncman programs by issuing the
> java commandline (with classpath and the various options). This may be
> necessary on a machine where no MaxDB installation has taken place
> (consider e.g. a Mac where only a MySQL instance is to be synchronized)
> or 
> in a large, more complicated scenario (where e.g. the synchronization
> programs
> and their related database instances are not running on the same
> machine.)
> Running the SyncMan programs this way (i.e. the hard way) is addressed 
> in the documents you found in '<independent program
> path>/app/syncman/doc'.
>
> Yes, the latter documents should not be so easy to spot, since a) is the
> recommended 
> approach for first/most users. We will rename them, move them to a
> different location, or 
> preface the with a disclaimer in future releases. 
> Our apologies for being misleading and your inconvenience.
>
> To address the points you made:
>
> 1)
>   
>> In the  /opt/sdb/programs/app/syncman/doc/RunningTheMessageServer.pdf  
>> page number 4  in chapter 1.4.1 there is the command
>> java -classpatch .\lib\sapdbc.jar;.\lib\msgserver.jar;.\lib\j2ee.jar 
>> com.sap.sdb.msgServer.Server .\MSGSERVER.xml
>>     
>
>   
>> but it should be
>>     
>
>   
>> java -classpatch .\lib\sapdbc.jar;.\lib\msgserver.jar;.\lib\j2ee.jar 
>> com.sap.sdb.msgServer.Server -f .\MSGSERVER.xml
>>     
>
>   
>> (missing key -f).
>>     
>
> You are right, the '-f' is missing in that document.
> We will correct it, thanks for reporting.
>
> 2)
>   
>> And in the script syncman_caller.py there is wrong key -A.
>> [..some py code..]
>> With the original syncman_caller.py I always get the following error
>>     
>
>   
>> msgserver start
>> com.sap.sdb.msgServer.util.ServerException: conflicting specifications:
>>     
>
>   
>> database url, database user name, database password, admin password, or
>>     
>
>   
>> one of the ports conflicts with database key.
>>     
>
> This is most probably a result of first taking approach b), and
> modifying
> 'MSGSERVER.xml' and then switching to approach a).
>
> Please revert all modifications you made under '<independent program
> path>/app/syncman/'
> and try again. If you want to see something running as early as possible
> w/o experimenting and reading
> too much text, try the example in '<independent program
> path>/app/syncman/example'.
> (Since you now have run the wrappers before, you should take note of the
> possibility 
>  to get into configuration modus again by using the syncmanjconf program
> and the 'config' options
>  to the wrappers, cf. the example doc).
>
> regards,
>
> Markus
>
>
>   


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to