In addition to the following info, there are also hardcode server name 
references in remedy workflow objects (those are currently in your database) 
you would also need to take care of them as well.
Better option would be:

Export ARsystem tablespace with expdp or whatever you think is better.
Restore that on proposed remedy database server
Run remedy installer pointing towards the newly restored database server
Install rest of the application components one by one.
Whenever and wherever require remedy application installer will just lay down 
the libraries and binaries instead of touching the actual database objects, 
however this does not mean it won't remove the hardcode references , installer 
will take care of that as well.

This can be good approach in my opinion.


From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of laurent matheo
Sent: Friday, April 05, 2013 4:13 PM
To: arslist@ARSLIST.ORG
Subject: Re: Replicating ARS Installation on Linux

**
Hi :)

I'm not sure it'll be that easy.

You also have a "/etc/arsystem/servername/" folder with "armonitor.conf" file 
for example.
Then when you install ARS there are some manual steps to be applied if you 
don't install on root, for example some files to be copied, declaring RPC ports 
in "/etc/rpc/", check the "installation guides" for a complete list.
You also have a lot of places where the server name is written, in files like 
ar.conf, all the "pluginsrv_config.xml" files, but also in database and some 
forms (attached files, reports...).

If you just copy the files like this I doubt you'll be able to just start ARS.

As for tomcat I would go for a clean mid-tier installation, should take minutes.

On 05 Apr, 2013,at 11:36 AM, Nathan Brandt <nathanrbra...@gmail.com> wrote:
**
Hello,

I installed ARS 7.6.04 on a RHEL 5.3 on top of Oracle.
Tomcat was installed at /opt/apache and ARS (with all the applications) was 
installed at /opt/bmc. I want to replicate this setup on a different machine. 
Just wanted to know if following would work

1. Using expdp take dump of ARADMIN schema on existing machine
2. tar zip /opt/bmc and /opt/apache folders on existing machine
3. Install Oracle on another machine say machine2
4. Using impdp restore ARADMIN schema on machine2
5. restore folders /opt/bmc and /opt/apache on machine2
6. Change ar.conf file to point to correct database
7. Change license key

Has anyone tried this approach?

~ Nathan
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to