[frs-119] How do I rename instances within FusionReactor?


Unfortunately there is no 'Rename Active Instance' function available within FusionReactor as of yet. However you can rename monitored FusionReactor instances on the Enterprise Dashboard>Manage Servers page, though.

As a workaround you can edit the reactor.conf file of the instance and change the value of the 'name' property. Also edit the /fusionreactor/etc/conf/instance/instances.xml file. Search for an XML snippet like

<void method="put">
<string>name</string>
<string>default.tomcat.int003c</string>
</void>

under the element representing your FusionReactor instance. Then change the value of the second <string> element. You need to restart the server afterwards to apply the changes. This function will be featured in a forth coming version of the software which will be made available at a later date.

You can of course rename the instance directory as well with out having to reinstall – it is just more work and you could break FR if you make a mistake. There are references to the instance directory in reactor.conf, in instances.xml and in the web descriptor (e.g. default.web.xml) of the server where FR runs. If you have two instances and want their logs to be written to the same directory you can change the names of the log files in the reactor.conf files:

Example:

crashprotection.logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
crashprotection.log
jdbc.logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
jdbc.log
logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
reactor.log
request.logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
request.log
resource.logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
resource.log

change to:

crashprotection.logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
tomcat-crashprotection.log
jdbc.logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
tomcat-jdbc.log
logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
tomcat-reactor.log
request.logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
tomcat-request.log
resource.logfile=C:\FusionReactor\instance\default.tomcat.int003c\log
tomcat-resource.log

Then edit the reactor.conf file of the other instance and change the properties above to use the same directory but different file names.

NOTE: If you change the name of the instance directory also check that the
'Request Settings->Capture Path' value (in reactor.conf this is the
'serializer.path' property) is changed accordingly.

NOTE: You could also use FRAPI to alter these properties programatically.

If you want to rename the current instance you need to make the required changes to the following two files:

fusionreactor/conf/instance/instances.xml:
——————————————


<void property="name">
<string>YOUR NEW NAME</string>
</void>
..
<void property="reactorInstanceName">
<string>YOUR NEW NAME</string>
</void>
<void property="serverInfo">
<void property="home">
<string>THE HOME DIR OF THE SERVER HOSTING THE FR INSTANCE</string>
</void>

fusionreactor/INSTANCE-NAME/conf/reactor.conf:
———————————————-

name=YOUR NEW NAME

The name of the instance directory (INSTANCE-NAME) is chosen when you create the instance during Setup or with the Instance Manager. It should not be changed afterwards.

ATTENTION: Do not use the name of an existing instance directory (with a modified instance name) as the new name for your instance! If you do so, the configuration and logs will be written to the wrong instance directory and you can destroy your active instance when removing it via the Instance Manager page.

Restart the server to make the changes appear.

Go to the Instance Manager page and add your instance to the Enterprise Dashboard (by clicking on the blue button which became active again).
Go to the Enterprise Dashboard -> Manage Servers page and remove the obsolete copy of your instance (you can add the same instance as many times as you want here).

Issue Details

Type: Technote
Issue Number: FRS-119
Components: FusionReactor Settings
Environment:
Resolution: Fixed
Last Updated: 14/Jun/07 1:55 PM
Affects Version: 2.0
Fixed Version: 2.0
Server:
Platform:
Related Issues: