Skip to main content
Participating Frequently
December 5, 2011
Question

cloning instances in cf9 multiuser version

  • December 5, 2011
  • 1 reply
  • 1064 views

CF9(multiuser) on Solaris 10 with the Oracle Webserver 7.

What I'm really in search of is a way to change the location of my CFIDE mapping and run CF as a different user(nobody instead of root).

Looking for a procedure to clone an instance. What I'd like to do is change location of the CFIDE dir and who the instance runs as(from root to nobody) in the new clone. In this clone I'd like to retain all data sources and config from the first instance.

Anyone done anything like this???

This topic has been closed for replies.

1 reply

Participating Frequently
December 5, 2011

Hi Keith,

Assuming that you’re running JRun on Solaris. 

Firstly: Su root

  1. Create  a new group ( cfgroup )
  2. Create  a new user(cfuser_instancename) and assign permissions for JRun, JWS7, network  monitoring client (BMC Patrol or whatever) et al… whatever
  3. Create  a new cfinstance in the Enterprise master CFIDE (note: in the CFIDE Admin  instances you won’t be able to create instances)
  4. Stop  the new instance
  5. All  the master config files live in the  JRUN_HOME/servers/cfusion/cfusion-ear/cfusion-war/WEB_INF/cfusion/lib folder
    1. Copy your neo-runtime.xml
    2. Copy your neo-datasource.xml
    3. Find and amend the CFIDE path in the neo-runtime.xml (be careful  as new instances have subtly different mapping – new instances use  cfusion.ear/cfusion.war – NOT as the original master instance.  We export  the file and use an XML editor to do this rather than vim on the server.
    4. Paste both files into  JRUN_HOME/servers/<NEWINSTANCENAME>/cfusion.ear/cfusion.war/WEB_INF/cfusion/lib
  6. Chown  on the new instance to the new cfuser_instancename/cfgroup
  7. Chmod  (664) on the new instance as your require
  8. Create  a new JWS7 instance – we use cfinstancename in JWS instance title
  9. Add  the cfuser_instancename / cfgroup to the JWS 7 admin panel for that instance
  10. Start  new cfinstance and check new cfide admin access

In the meantime, gimme a shout if you have any specific queries  on the sequence.  I’ll try and take the time out to create a tutorial for  this one and post it up somewhere.

Best,

Padz

keithalAuthor
Participating Frequently
December 5, 2011

Thanks padz. I'm going to try this but a few questions first. Step 5  talks about modifying neo-runtime.xml. I've tried this on my current instance and each and every time I restart the instance it reverts back to the previous setting for the CFIDE mapping. Do you know why this happens and why won't it happen in the procedure you posted?

Participating Frequently
December 5, 2011

Hi Keith, haven't had that problem myself on Solaris.  Sounds like mem caching or Vi is not saving/overwriting the file(s) so here's what I'd try... 

1. How many neo-runtime files ? [If you've run the instance then they'll be two:  .xml and .bak [in the WEB-INF/cfusion/lib folder].  Grab both.

2. Stop all JRun instance to make the changes.

3. Export the files to an xml editor and edit the paths in .xml and .bak [if exists]

4. Overwrite the neo-runtime files.

5. Check the owner / perms on the file(s).

6. ONLY boot the new instance.

7. Test new CFIDE instance working as expected - check logs if errors

8. If all OK, run your wsconfig details to the (new?) JWS instance

9. Reboot master instance

If the neo-runtime is still reverting to original, use the master cfusion instance CFIDE (original primary install) and delete the instance that you've created.  Reboot the server.  Start again.