how can i point rhythmyx to a different jdbc database repository

Rhythmyx Technical Discussion
1

initially i thought there was only a couple of files i had to change but even after changing the jdbc database connection details in

$ vi rxconfig/Installer/rxrepository.properties
$ vi rxconfig/Workflow/rxworkflow.properties

i still get errors and exceptions and rhythmyx fails to start !

DatabasePool
07/03/08 16:44:
An exception occurred attempting to establish a connection to : oracle:thin:@localhost:1521:rhythmyx. java.sql.SQLException: [1] null:

i have now discovered there are over 167 other files with 1000 hard coded references to the jdbc database repository

$ grep -l driver ObjectStore/* | wc
185 185 6114

has anyone writen any awk/sed scripts that i could use to change all these ?

and are there any other hard coded jdbc database connection strings i need to change ?

2

Hi Clive

Which version of Rhythmyx are you on. It differ between 5.x and 6.x

If 5 then use the application RhythmyxServerPropertiesEditor.exe found in the root.

If 6 then update the file:
Rhythmyx\AppServer\server\rx\deploy\rx-ds.xml

username and password in this file:
Rhythmyx\AppServer\server\rx\conf\login-config.xml

Cheers
James

3

we are using 5.7 and i have tried both

$ ./RxPropertiesEditor.sh /Rhythmyx

and

$ ./RhythmyxServerPropertiesEditor.sh /Rhythmyx -convert

/Rhythmyx /Rhythmyx
*** Starting conversion of installation rooted at: /RxPub/rx/Rhythmyx ***
keepExternal=false
Unexpected exception in main
java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64
at com.percussion.util.PSBase64Decoder.decode(Unknown Source)
at com.percussion.util.PSCryptographer.decrypt(Unknown Source)
at com.percussion.server.PSServerPropertiesDialog.Ã00000(Unknown Source)
at com.percussion.server.PSServerPropertiesDialog.o00000(Unknown Source)
at com.percussion.server.PSServerPropertiesDialog.main(Unknown Source)
/Rhythmyx

4

THANKS final solution is

$ vi rxconfig/Server/server.properties

and edit

serverName=@remotehosthost:1521:rhythmyx
loggerClassname=net.sourceforge.jtds.jdbc.Driver
driverType=jtds:sqlserver
databaseName=rhythmyx
loginId=rhythmyx
loginPw=1DB71DB71DB71DB71DB71DB7

as appropriate

then

$ ./RhythmyxServerPropertiesEditor.bin -convert

5

you can also run

$ ./RhythmyxServerPropertiesEditor.bin

which will display a GUI allowing you to enter the new database connection values

6

if you are using the GUI loggerClassname is displayed as Driver Class Name

if you are editing server.properties manually you may also need to set
schemaname=my-ms-sql-schema-name

and set
suppressSearchFieldOverrides=false

7

So, for version 6.x, how do I point my rhythmyx to a different database repository?

8

Hi Creig

You can either edit the below files:

The server and datasource name in this file
Rhythmyx\AppServer\server\rx\deploy\rx-ds.xml

username and password in this file:
Rhythmyx\AppServer\server\rx\conf\login-config.xml

or

open the /rxroot/serveradminstrator.exe and select the datasource tab

then edit the RhythmyxData JNDI configuration to point at the new server.

Both will require you to stop and restart the Rhythmyx service.

Cheers
James

9

For version 6.x, it is recommended that you use the Rhythmyx Server Administrator to make this change. There are several files that need to be modified (server-beans.xml is another, for example), and the password which is stored in the login-config.xml is actually encrypted, so you cannot edit it there.

In the Server Administrator, you can configure an new JNDI Datasource and Datasource Connection and then set the new Connection as the repository, save the changes, and restart the server.

In the case where you cannot use the Server Administrator (you must be able to run the Rhythmyx server still pointing to the old repository db while you configure the new repository), please contact Technical Support for assistance in making the manual changes required.

10

Thanks for the help on this topic. I posted my method here:

http://forum.percussion.com/showthread.php?831-Cloning-cms-db-and-filesystem-procedure.&p=18692#post18692