We have OpManger 10 (Build 10100) installed on a Windows Server 2008 R2 server with the database in SQL 2005 on a Windows Server 2003 R2. We need to copy the setup to a new machines (both the application and database). We don't want to turn of the old setup until the new one is fully operational.

I think I am nearly there but I don’t this it is working completely well.

So far I have:

1.       1. Created a copy of the OpManager database and moved it onto a new SQL server

2.       2. Installed the same version of OpManager on a new machine and pointed it to the new database.

3.       3. Copied the User and Conf folder from old server to new one (and updated the database_params.conf) file to point to new DB)

4.       4. Copied AdventNetLicense.xml, petinfo.dat and product.dat from the OpManager/Classes to new machine.

Every time I go via a web browser to the new server it load the LoginPage.do page and advises it is initializing modules. Eventually it times out and goes into the login page. When I look at the wrapper log it looks like it never gets past the OpMananagerProcess.

Extract from the wrapper log

INFO   | jvm 1    | 2017/01/10 09:17:00 | Process : EventMgr                       [ Started ]

INFO   | jvm 1    | 2017/01/10 09:17:01 | Process : Collector                      [ Started ]

INFO   | jvm 1    | 2017/01/10 09:17:03 | Process : OpManagerProcess               [ Started ]

Shouldn’t it eventually load like this in the log (extracted from current\old server)?

INFO   | jvm 1    | 2017/01/09 13:53:29 | Process : TopoFE                         [ Started ]

INFO   | jvm 1    | 2017/01/09 13:53:29 | Process : EventFE                        [ Started ]

INFO   | jvm 1    | 2017/01/09 13:53:29 | Verifying connection with web server ... verified

INFO   | jvm 1    | 2017/01/09 13:53:29 |

INFO   | jvm 1    | 2017/01/09 13:53:29 | OpManager modules started successfully

INFO   | jvm 1    | 2017/01/09 13:53:29 |

INFO   | jvm 1    | 2017/01/09 13:53:29 | Please connect your client to the web server on port: 9090 as http://localhost:9090

What else am i missing? I am wanting to upgrade to the latest version also so not sure it that will simple fix this or not?

Thank you for your time and consideration.

Rodney