ActiveMatrix Admin not able to start after migrating database to another server.Changing Database parameters is not supported for 2.0.1. This support will be available in 2.1.For 2.0.1, the procedure below can be applied.
Article ID: KB0091239
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Service Grid | - |
| Not Applicable | - |
Description
Resolution:
1) Unbind all Management Daemons (no need to uninstall nodes to do that).
2) Stop each Admin server instance.
3) Copy all tables, constaints, rules, defaults from one database to another.
(even in AMSG 2.1, this is a manual step; our software will not do this automatically)
4) Modify following administrator xml file on each and every Admin server instance:
4.1) Run <tibco-home>\amxadministrator\2.0\bin\passwordobfuscator.exe -p <new-database-user> <new-database-password>
The output is an encrypted password that you must use in the "password" attribute in the XML in
the step below.
4.2) Edit <tibco-home>\amxadministrator\data\<amx>\<admin>\config\server-config.xml
Update the DB parameters in this section of the XML:
-------------
<configuration-persistence use="db">
<persistence type="file"/>
<persistence type="db">
<property name="driver" value="org.hsqldb.jdbcDriver"/>
<property name="url" value="jdbc:hsqldb:hsql://SAPTE-DT2:1234/amx"/>
<property name="user" value="sa"/>
<property name="password" value="/HXP429XtI0="/>
<property name="mask" value="true"/>
<property name="algo-name" value="BlowFish"/>
<property name="maxConnections" value="5"/>
<property name="loginTimeout" value="30000"/>
<property name="tablename" value="amxadm_amx_hsql"/>
</persistence>
</configuration-persistence>
--------------
5) Modify following administrator xml file on any one (but only one) Admin server instance.
This step is only applicable if you are using Database Realm pointing to the database that needs
to be moved.
5.1) Run <tibco-home>\amxadministrator\2.0\bin\passwordobfuscator.exe <new-database-password>
The output is an encrypted password that you must use in the "password" attribute in the XML in
the step below.
Note that the arguments to passwordobfuscator are different than step 4.1.
5.2) Edit <tibco-home>\amxadministrator\data\<amx>\<admin>\config\security-config.xml
Update the DB parameters in this section of the XML:
<realm>
<realm-name>system</realm-name>
<user-manager>
<init-options>
<entry>
<name>url</name>
<value>jdbc:hsqldb:hsql://SAPTE-DT2:1234/amx</value>
</entry>
.....
.....
</user-manager>
</realm>
<login-module-configuration>
<realm-name>system</realm-name>
<config-entry>
<options>
<entry>
<name>hibernate.connection.url</name>
<value>jdbc:hsqldb:hsql://SAPTE-DT2:1234/amx</value>
</entry>
.....
.....
</options>
</config-entry>
</login-module-configuration>
5.3) Run <tibco-home>\amxadministrator\2.0\bin\amx_admin.bat -uploadconfig
Running with '-uploadconfig' parameter is needed only one time.
6) Modify following xml file on each and every AMX Node that was installed:
6.1) Run <tibco-home>\amxadministrator\2.0\bin\passwordobfuscator.exe -p <new-database-user> <new-database-password>
The output is an encrypted password that you must use in the "password" attribute in the XML in
the step below.
6.2) Edit <tibco-home>\amx\data\<environment>\<node>\config\server-config.xml
Update the DB parameters in this section of the XML:
-------------
<configuration-persistence use="db">
<persistence type="file"/>
<persistence type="db">
<property name="driver" value="org.hsqldb.jdbcDriver"/>
<property name="url" value="jdbc:hsqldb:hsql://SAPTE-DT2:1234/amx"/>
<property name="user" value="sa"/>
<property name="password" value="/HXP429XtI0="/>
<property name="mask" value="true"/>
<property name="algo-name" value="BlowFish"/>
<property name="maxConnections" value="5"/>
<property name="loginTimeout" value="30000"/>
<property name="tablename" value="amxadm_amx_hsql"/>
</persistence>
</configuration-persistence>
--------------
7) Restart Admin servers and AMX nodes.
Discover and rebind all the MDs. Rebind will push new DB parameters from Admin
to all the MDs.
1) Unbind all Management Daemons (no need to uninstall nodes to do that).
2) Stop each Admin server instance.
3) Copy all tables, constaints, rules, defaults from one database to another.
(even in AMSG 2.1, this is a manual step; our software will not do this automatically)
4) Modify following administrator xml file on each and every Admin server instance:
4.1) Run <tibco-home>\amxadministrator\2.0\bin\passwordobfuscator.exe -p <new-database-user> <new-database-password>
The output is an encrypted password that you must use in the "password" attribute in the XML in
the step below.
4.2) Edit <tibco-home>\amxadministrator\data\<amx>\<admin>\config\server-config.xml
Update the DB parameters in this section of the XML:
-------------
<configuration-persistence use="db">
<persistence type="file"/>
<persistence type="db">
<property name="driver" value="org.hsqldb.jdbcDriver"/>
<property name="url" value="jdbc:hsqldb:hsql://SAPTE-DT2:1234/amx"/>
<property name="user" value="sa"/>
<property name="password" value="/HXP429XtI0="/>
<property name="mask" value="true"/>
<property name="algo-name" value="BlowFish"/>
<property name="maxConnections" value="5"/>
<property name="loginTimeout" value="30000"/>
<property name="tablename" value="amxadm_amx_hsql"/>
</persistence>
</configuration-persistence>
--------------
5) Modify following administrator xml file on any one (but only one) Admin server instance.
This step is only applicable if you are using Database Realm pointing to the database that needs
to be moved.
5.1) Run <tibco-home>\amxadministrator\2.0\bin\passwordobfuscator.exe <new-database-password>
The output is an encrypted password that you must use in the "password" attribute in the XML in
the step below.
Note that the arguments to passwordobfuscator are different than step 4.1.
5.2) Edit <tibco-home>\amxadministrator\data\<amx>\<admin>\config\security-config.xml
Update the DB parameters in this section of the XML:
<realm>
<realm-name>system</realm-name>
<user-manager>
<init-options>
<entry>
<name>url</name>
<value>jdbc:hsqldb:hsql://SAPTE-DT2:1234/amx</value>
</entry>
.....
.....
</user-manager>
</realm>
<login-module-configuration>
<realm-name>system</realm-name>
<config-entry>
<options>
<entry>
<name>hibernate.connection.url</name>
<value>jdbc:hsqldb:hsql://SAPTE-DT2:1234/amx</value>
</entry>
.....
.....
</options>
</config-entry>
</login-module-configuration>
5.3) Run <tibco-home>\amxadministrator\2.0\bin\amx_admin.bat -uploadconfig
Running with '-uploadconfig' parameter is needed only one time.
6) Modify following xml file on each and every AMX Node that was installed:
6.1) Run <tibco-home>\amxadministrator\2.0\bin\passwordobfuscator.exe -p <new-database-user> <new-database-password>
The output is an encrypted password that you must use in the "password" attribute in the XML in
the step below.
6.2) Edit <tibco-home>\amx\data\<environment>\<node>\config\server-config.xml
Update the DB parameters in this section of the XML:
-------------
<configuration-persistence use="db">
<persistence type="file"/>
<persistence type="db">
<property name="driver" value="org.hsqldb.jdbcDriver"/>
<property name="url" value="jdbc:hsqldb:hsql://SAPTE-DT2:1234/amx"/>
<property name="user" value="sa"/>
<property name="password" value="/HXP429XtI0="/>
<property name="mask" value="true"/>
<property name="algo-name" value="BlowFish"/>
<property name="maxConnections" value="5"/>
<property name="loginTimeout" value="30000"/>
<property name="tablename" value="amxadm_amx_hsql"/>
</persistence>
</configuration-persistence>
--------------
7) Restart Admin servers and AMX nodes.
Discover and rebind all the MDs. Rebind will push new DB parameters from Admin
to all the MDs.
Issue/Introduction
ActiveMatrix Admin not able to start after migrating database to another server.Changing Database parameters is not supported for 2.0.1. This support will be available in 2.1.For 2.0.1, the procedure below can be applied.
Feedback
Yes
No
Powered by
