Thread: Running two SM7.00 Instances on one server?

Hi Guys,

We are currently facing an issue trying to run two instances SM application server on one box. With the previous installations you had the option of Renaming the Windows Service and then referencing it in your sc.ini file. With SM7.00 installation, as you may have noticed, there is no way to rename the smservice.exe that installs. If you have an environment with two or three seperate servers this would not be an issue but because we running our QA and DEV on one box we have this problem. Upon the installation, the one will always take presidence over the other.

Please help.....

Now that the console is no longer used, and since the service starts the server, what if you talked to your Windows Sys Admin about renaming the service. A quick Google shows that this may be possible with some "Windows Resource Kit" or something like that - there may be third party apps that will due it as well (I'm guessing it is a registry mod).

This is all a guess though, I've never tried it as I have separate virtual environments that I do my dev work in.

What you can do is the following:

- copy the everything below the directory level of the installation folder to a new instance folder. so if your installation folder is 'C:\Program Files\Peregrine\ServiceCenter\6.2.2\Server' then copy the 'Server' folder with everything in it to a 'C:\Program Files\Peregrine\ServiceCenter\6.2.2\Server_1' folder
- in the 'Server_1\RUN' directory you modify the sc.ini so that the parameter 'ntservice:' says 'ntservice:ServiceCenter_1'. Save the sc.ini
- open a command prompt and change to the 'C:\Program Files\Peregrine\ServiceCenter\6.2.2\Server_1\RUN' folder
- type the following command 'scservice -install'. this will create a new service called 'servicecenter_1'

Now you will have 2 seperate instances running on one box. You can create as many as you like by repeating the steps above.

Replace "C:\Program Files\Peregrine\ServiceCenter\6.2.2\Server\sc.ini" in above text with "C:\Program Files\HP\Service Manager 7.00\Server\RUN\sm.ini" and it will work.

If there is no ntservice defined SM will use the default.