Monday's work: Migrating a Maximo server, Part Two.
Yesterday's list looks really neat, doesn't it? I revised yesterday's list of to-do's extensively, in light of what actually happened during the migration. For one, I had to keep checking where I was storing my databases. I created a diagram on my white board to keep them all straight. Listed below are the databases and instances affected by the move. The new server is called MAXNC3082.
|Maximo instance||Admin Workstation||DB Name||DB server||App Server name||WebSphere server|
|Maximo 6.2.8 (Oracle)||My Notebook||max62||MAXNC3082||max62server||MAXNC3082|
|Maximo 6.2.6 (SQL Server)||My Notebook||max62db||MAXNC0050||max62SQLserver||MAXNC3082|
|Maximo 188.8.131.52 (Oracle)||MAXNC3082||max71||MAXNC3082||max71server ||MAXNC3082|
|SmartCloud Control Desk 184.108.40.206||MAXNC0050||sccd75||MAXNC3082||sccd750server||MAXNC0050|
Oracle database server
I created three databases: max62, max71 and sccd75 using the steps in each of the three (Maximo 6.2, 7.1 and SmartCloud 7.5) installation guides. They all use the Database Configuration Assistant. They each use different memory settings, but three settings are identical.
In Advanced initialization parameters: nls_length_semantics=CHAR, open_cursors=1000, cursor_sharing=FORCE
Then, for each of them I ran the maximo schema setup using SQL*Plus. The parameters are identical between the two versions, and unchanged since Maximo 4 was released.
create tablespace maxdata datafile '<oracle_install_location>\product\<oracle_version>\dbhome_1\database\<database_name>\maxdata.dbf' size 1000M autoextend on;
create temporary tablespace maxtemp tempfile '<oracle_install_location>\product\<oracle_version>\dbhome_1\database\<database_name>\maxtemp.dbf' size 1000M autoextend on maxsize unlimited;
create user maximo identified by maximo default tablespace maxdata temporary tablespace maxtemp;
grant connect to maximo;
grant create job to maximo;
grant create trigger to maximo;
grant create session to maximo;
grant create sequence to maximo;
grant create synonym to maximo;
grant create table to maximo;
grant create view to maximo;
grant create procedure to maximo;
grant alter session to maximo;
grant execute on ctxsys.ctx_ddl to maximo;
alter user maximo quota unlimited on maxdata;
WebSphere application server
I was also not sure that my method of cloning the administrative workstation for max71server (Maximo 220.127.116.11) would work. I had to:
- Install the same version of WebSphere that I had installed on my source system on the target systemm, using the same installers, logged in as Administrator.
- Migrate the \program files\ibm\common\acsi directory from the source server, replacing the Deployment Engine I had just created
- Update the hostname.
- After copying over the \ibm\smp directory, use Reconfiguration Tool for Maximo Admin Workstations 7.1 on the target system to make sure the WebSphere connection information was correct.
Creating WebSphere application servers
Since I use this server for support purposes only, it is not necessary for all of the Maximo servers to be running. This means I don't have to worry about how much physical RAM I have.
However, in real-world installations, you have to take into account how much physical RAM you have before you start a Production server. Each Maximo web application server should have 7 GB of physical RAM per Maximo instance; see Maximo Asset Management system requirements for system requirements.
Manual steps for creating Application server may be found in the installation guide or Information Center for Maximo 7.5
The Middleware WebSphere installation creates a Web Server (webserver1), and services for Cell Manager and Node Agent.
It does not create the JMS Queues.
- Create Application Server.
- Create Virtual Host that includes the Application server's four TCP/IP ports: WC_adminhost, WC_adminhost_secure, WC_defaulthost, WC_defaulthost_secure, and port 80
- Repeat as necessary.
- Manually configure JMS queues.
- Install RMI Registry application.
- Build and deploy maximo.ear.
- Build and deploy mxiehs.ear (SmartCloud Control Desk7.5) or maximohelp.ear (Maximo 7.1).
- Start MXServer.
Wednesday: A quick Active Directory configuration?