Maximo 7.5.0.5 on Windows Server 2012

Goal: 
Install Maximo 7.5.0.5 on Windows Server 2012. 

Problem:
When looking at the Platform Matrix (dated 31 October 2013, check this link for the most recent version: http://www-01.ibm.com/support/docview.wss?uid=swg27014419), Windows 2012 is supported for Maximo from version 7.5.0.3 and up.

But wait! as it turns out, it states it runs on 'Support only'  So you will have to figure it out for yourself how to get it running.
And on top of that, Windows 2012 is even supported as Admin Workstation...

Here is a part of the Matrix:

So be very aware of this comment! I had me fooled... :(

But hey, if we can get the Websphere running with Maximo 7.5.0.5, we have support. :)

Notes for this document:
Servername:  MYWINDOWS2012SERVER, or masked in screenshots because it is a company server and the client his server.
Database: Oracle 11g2
User: Local Admin (Make sure you have the permissions you need!)


Solution:
I got it running in the end. I ran into a few issues and will show you how I solved them below. 

First I started of like I normally would, run the launchpad64.exe as an administrator.

Then choose "Install Product" and then click "Middleware"
Choose you Language, accept the License Agreement and set your Workspace. (I used D:\ibm\tivoli\mwi\workspace)
  
After clicking 'Next' I got the following message:

To get more details on this, open the mwi.log from D:\ibm\tivoli\mwi\workspace\MYWINDOWS2012SERVER
This is part of the log:

com.ibm.ac.si.install.InstallFailedException: 
at com.ibm.ac.si.install.SIInstaller.initialize(SIInstaller.java:2598)
at com.ibm.ac.si.install.SIInstaller.<init>(SIInstaller.java:2319)
at com.ibm.ac.si.install.SIInstaller.install(SIInstaller.java:876)
at com.ibm.ac.si.install.BootstrapApplication.performInstallOperation(BootstrapApplication.java:330)
at com.ibm.ac.si.install.BootstrapApplication.performOperation(BootstrapApplication.java:190)
at com.ibm.ismp.mwi.BootstrapDeploymentEngine.execute(BootstrapDeploymentEngine.java:134)
at com.installshield.wizard.RunnableWizardBeanContext.run(Unknown Source)
Caused by: com.ibm.ac.si.install.UnrecognizedOSException: ACUINI0045E The current OS is unrecognized by this application: Name = Windows Server 2008 ; Architecture = amd64 ; Version = 6.2 build 9200 
at com.ibm.ac.si.install.SIInstaller.validateSupportedOS(SIInstaller.java:2751)
at com.ibm.ac.si.install.SIInstaller.initialize(SIInstaller.java:2400)
... 6 more
(Thu Dec 12 14:48:28 CET 2013) DefaultVariableProxy [FINEST]: setValue[variable:deploymentEngineDeployed, newValue:false, oldValue:false, source:com.ibm.ismp.mwi.BootstrapDeploymentEngine]
(Thu Dec 12 14:48:28 CET 2013) DefaultVariableProxy [FINEST]: setValue[variable:deploymentEngineErrorMessage, newValue:CTGIN9077E: Deployment Engine is not functioning properly. Please delete the DE folder in MWI workspace and restart the MWI installer., oldValue:CTGIN9077E: Deployment Engine is not functioning properly. Please delete the DE folder in MWI workspace and restart the MWI installer., source:com.ibm.ismp.mwi.BootstrapDeploymentEngine]
(Thu Dec 12 14:48:28 CET 2013) com.ibm.ismp.mwi.Lathe [FINEST]: INSTALL_GENERAL_FAILURE
(Thu Dec 12 14:48:28 CET 2013) com.ibm.ismp.mwi.Lathe [SEVERE]: 
(Thu Dec 12 14:48:28 CET 2013) com.ibm.ismp.mwi.Lathe [SEVERE]: D:\ibm\tivoli\mwi\workspace\MYWINDOWS2012SERVER\DE\acsi\jre\copyright (The system cannot find the path specified.)
java.io.FileNotFoundException: D:\ibm\tivoli\mwi\workspace\MYWINDOWS2012SERVER\DE\acsi\jre\copyright (The system cannot find the path specified.)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at com.ibm.ismp.mwi.BootstrapDeploymentEngine.copyFile(BootstrapDeploymentEngine.java:334)
at com.ibm.ismp.mwi.BootstrapDeploymentEngine.execute(BootstrapDeploymentEngine.java:163)
at com.installshield.wizard.RunnableWizardBeanContext.run(Unknown Source)
(Thu Dec 12 14:48:28 CET 2013) com.ibm.ismp.mwi.Lathe [SEVERE]: D:\ibm\tivoli\mwi\workspace\MYWINDOWS2012SERVER\DE\acsi\jre\notices.txt (The system cannot find the path specified.)
java.io.FileNotFoundException: D:\ibm\tivoli\mwi\workspace\MYWINDOWS2012SERVER\DE\acsi\jre\notices.txt (The system cannot find the path specified.)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at com.ibm.ismp.mwi.BootstrapDeploymentEngine.copyFile(BootstrapDeploymentEngine.java:334)
at com.ibm.ismp.mwi.BootstrapDeploymentEngine.execute(BootstrapDeploymentEngine.java:166)

at com.installshield.wizard.RunnableWizardBeanContext.run(Unknown Source)


Seems to me that there is a problem writing/accessing files. Also there is a line that the OS is not recognized...

First I closed all the windows, and opened an explorer.
I browse to the IBM_MAM_V7.5.0_Launchpad\Install\MWI directory and right click the mwi-AMD64.exe file and choose 'Properties' 

Set the Compatibility on 'Windows 7' and check the 'Run this program as an administrator' 

Next I 'Googled' and found this page: http://www-01.ibm.com/support/docview.wss?uid=swg21650567

I used some part of it for my solution.

Open a dosbox as an Administrator.
Browse to the IBM_MAM_V7.5.0_Launchpad\Install\MWI directory and run:
mwi-AMD64.exe -V dependencyChecks=false

This is case-sensitive!

The installShield will now start. Choose your language, accept the License agreement, set you workspace, click Next and behold, it runs! :)

I'll install the J2EE Server only

I use the default settings and set the installation locations to the D:-partition using default paths in all the next screens. I suppose you can choose what you like, but this is the configuration I tested.

When you reach the screen with the option to Deploy the plan, hold on for a sec. We need to change something.

Open a explorer and go to the D:\ibm\tivoli\mwi\workspace\<hostname>\deploymentPlan\MachinePlan_<hostname>\MachinePlan_<hostname>.xml 

Open this xml with a editor like Notepad++. Make sure you run Notepad++ as an administrator!

Update the value of the below two properties to "true" :

<property value="true" name="suppress.step_00001_MWI_7.1_Prereqs"/>
<property value="true" name="suppress.step_00002_DiskSpace_Check"/> 

Save the file.

Go back to the screen that is still open en click on [Next] to deploy the plan. A summary list of the plan will be displayed next, click the [Deploy] button to start.

Ok, so that was Websphere, you could now install Maximo on a supported Admin Workstation and deploy the ear file here. When you use Maximo 7.5.0.3 or higher IBM will support it.

But hey, they are not giving away Servers and Admin workstations for free, so it would be nice if we could use this Windows 2012 server as Admin Workstation.
I want to try this for the Test environment, and if it can be done without to much 'quick and dirty' solutions and Maximo can be patched and all, this would be a useful test environment.



Maximo 7.5.0.0 installation
Again I started of like I normally would, run the launchpad64.exe as an administrator. Click on the "Install Product"  option on the left, and choose "Maximo Asset Management"  

The Install Anywhere dialog shows and shows the " Preparing to install". When done the following error appears:

I close all the windows, and open an explorer.
Browse to the IBM_MAM_V7.5.0_Launchpad\Install\MAM directory and right click the install_win64.exe file and choose 'Properties' 

Set the Compatibility on 'Windows 7' and check the 'Run this program as an administrator' 

Open a dosbox as Administrator and browse to IBM_MAM_V7.5.0_Launchpad\Install\MAM directory and run: install_win64.exe

The Install Anywhere dialog shows up again and now the error is not displayed.I choose a language and click [Next]

I click through the screens like I normally would when installing Maximo.

At the "Run Configuration Step" check all three boxes.

After a few minutes the installer is done.

Now to finish the installation we open a dosbox as and Administrator.
Navigate to D:\ibm\SMP\scripts\  and run taskRunner.bat CONTINUE STOPONERROR

Eventually the taskRunner will stop with a message we can also find in the D:\ibm\SMP\logs\CTGInstallTrace00.log

CTGIN0219I: Deploying process solution installation package D:\IBM\SMP\pmp\process_automation_engine_7.5.0.0.zip.

StandardError: CTGIN0143E: An action error ocurred during the processing of a deployment operation. Action identifier: "null". Action display name: "Create Package Log Directory".

Dec 16, 2013 11:12:37 AM com.ibm.tivoli.ccmdb.install.foundation.config.pmp.ACfgProcessManagerPackageConfig Result from install PSI
FINE: NOTE ^CTGIN0005E: The deployment of D:\IBM\SMP\pmp\MAM.zip failed. The error text is CTGIN0143E: An action error ocurred during the processing of a deployment operation. Action identifier: "null". Action display name: "Create Package Log Directory"..^n^

Dec 16, 2013 11:12:37 AM com.ibm.tivoli.ccmdb.install.foundation.config.pmp.ACfgProcessManagerPackageConfig runConfigurationStep

Seems like issues with file rights again...

Next I check the D:\ibm\SMP\CTG_DE\acsi\logs\<USER_NAME>\de_trace.log

There i get:

at com.ibm.ac.si.cm.TouchPointTask.workQueueError(TouchPointTask.java:1688)
at com.ibm.ac.si.cm.TouchPointTask.run(TouchPointTask.java:949)
at java.lang.Thread.run(Thread.java:736)
Caused by: com.ibm.ac.common.hosts.CreationFailedException: 
at com.ibm.ac.tp.basehost.AbstractHosts.createHostedResource(AbstractHosts.java:234)
at com.ibm.ac.si.cm.CreateCommand.execute(CreateCommand.java:122)
at com.ibm.ac.si.cm.TouchPointController.callTouchPoint(TouchPointController.java:287)
at com.ibm.ac.si.cm.TouchPointTask.run(TouchPointTask.java:815)
... 1 more
Caused by: com.ibm.ac.tp.basehost.ActionErrorException: action_processor_failure, action=addDirectory, actionId=null
at com.ibm.ac.tp.basehost.ActionHandler.createException(ActionHandler.java:779)
at com.ibm.ac.tp.basehost.ActionHandler.handleGeneralException(ActionHandler.java:1084)
at com.ibm.ac.tp.basehost.ActionHandler.handlePhase(ActionHandler.java:308)
at com.ibm.ac.tp.basehost.ActionProcessor.handleAction(ActionProcessor.java:258)
at com.ibm.ac.tp.basehost.ActionProcessor.run(ActionProcessor.java:122)
at com.ibm.ac.tp.basehost.AbstractHosts.createHostedResource(AbstractHosts.java:218)
... 4 more
Caused by: com.ibm.ac.si.ap.service.variable.VariableNotDeclaredException: ACUASI0132E Variable has not been declared or has no default value assigned: PkgLogDirectory
at com.ibm.ac.si.ap.service.variable.impl.VariableContextImpl.getValue(VariableContextImpl.java:258)
at com.ibm.ac.si.ap.service.variable.impl.VariableContextImpl.getReplacementValue(VariableContextImpl.java:371)
at com.ibm.ac.si.ap.service.variable.impl.VariableContextImpl.evaluateRecursive(VariableContextImpl.java:335)
at com.ibm.ac.si.ap.service.variable.impl.VariableContextImpl.evaluate(VariableContextImpl.java:303)
at com.ibm.ac.si.ap.action.VariableServiceHelper.resolveVariable(VariableServiceHelper.java:64)
at com.ibm.ac.si.ap.action.file.PathElements.getResolvedName(PathElements.java:152)
at com.ibm.ac.si.ap.action.file.PathElements.getResolvedFile(PathElements.java:176)
at com.ibm.ac.si.ap.action.AddDirectoryAction.installEmptyDirectory(AddDirectoryAction.java:489)
at com.ibm.ac.si.ap.action.AddDirectoryAction.install(AddDirectoryAction.java:81)
at com.ibm.ac.tp.basehost.InstallActionHandler.handlePhaseAction(InstallActionHandler.java:103)
at com.ibm.ac.tp.basehost.ActionHandler.handlePhase(ActionHandler.java:244)

... 7 more

A variable named PkgLogDirectory has no default value...

This must be somewhere in the MAM.zip package. This package can be found in D:\ibm\SMP\pmp

First create a backup of the MAM.zip file, then open the MAM.zip and go to the META-INF directory. There we find a file named "packageIU.xml"

Important is to not extract the zip and zip it again after you edited the file. But keep the zip in tact and just handle it like it was a folder.

Copy that file to the Desktop

Open a Notepad++ as administrator 

This is important, all files edited for Maximo, also files that we edit later on for rebuilding, need to be edited as administrator, not as the logged-in user, even if that user is local administrator.

We change two variables here. Because when we only change the PkgLogDirectory the taskRunner wants a default for the ModuleInstallDir.
Below are lines of code i used. I commented out the the original lines.

        <!-- This variable stores the location of any module/package specific -->
        <!-- files or code. This may or may not be used depending on the      -->
        <!-- specific package.                                                -->
<variable name="ModuleInstallDir">
           <parameter defaultValue="d:\IBM\smp\solutions\installedApps\MAM75_Package"/>
  <!--
           <derivedVariable>
                <expression condition="$(windows_TypeCheck)">$(CCMDBInstallLocation)\solutions\installedApps\$(PkgShortName)</expression>
           </derivedVariable> -->
        </variable>

        
        <!-- The path to the directory the contains the logs for this specific -->
        <!-- package. This is used if the package install writes to its own    -->
        <!-- specific install logs.                                            -->
        <variable name="PkgLogDirectory">
            <parameter defaultValue="d:\IBM\smp\solutions\logs\MAM75_Package"/>
            <!--<derivedVariable>
                <expression condition="$(windows_TypeCheck)">$(CCMDBInstallLocation)\solutions\logs\$(PkgShortName)</expression>
            </derivedVariable> -->

        </variable>

Essentially we comment out the existing line and add out own line. Instead of a Derived variable we use a defaultValue variable here.
Here again the line in a screenshot.

Next copy the MAM.zip to the desktop and open it, go to the META-INF directory and copy the 'packageIU.xml" here and replace the existing file. 
We cannot use the MAM.zip in the original directory because then the file is not placed in the zip with the right permissions.

Now copy the MAM.zip from the desktop back to the D:\ibm\SMP\pmp overwriting the existing MAM.zip

Again open a dosbox as and Administrator.
Navigate to D:\ibm\SMP\scripts\ and run "taskRunner.bat CONTINUE STOPONERROR"

and, whohoooo, all efforts are not in vain, the taskRunner continues.

After a while the taskRunner is finished.

Go to D:\ibm\SMP\bin and run "solutionInstaller.bat -action showinstalled -type all" to check the installation;

As a test if all configuration is correct I will install patch 7.5.0.5. If this installs without any problems the configuration must be good.


Install 7.5.0.5

Open the 7.5.0.5-TIV-MAM-FP0005 directory and change the properties of the install_win64.exe so it runs in Windows 7 compatibility mode

Next I open a dosbox as an Administrator and navigate to the 7.5.0.5 patch directory and run the "install_win64.exe"

Now click through the screens like you normally would when installing a patch

At the end I get :

CTGIN2225E: Deployment of application MAXIMO failed.

WASX7023E: Error creating "SOAP" connection to host "MYWINDOWS2012SERVER"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException: com.ibm.websphere.management.exception.ConnectorNotAvailableException: ADMC0016E: The system cannot create a SOAP connector to connect to host  at port 8879.
WASX7213I: This scripting client is not connected to a server process; please refer to the log file D:\IBM\SMP\wasclient\logs\wsadmin.traceout for additional information.
WASX8011W: AdminTask object is not available.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[install, MAXIMO, ctgNode01, MXServer, D:/IBM/SMP/maximo/deployment/default/maximo.ear, maximo_host, webserver1]"
Admin objects not loaded. Connection to Websphere is bad
Sleeping and retrying
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

WASX7023E: Error creating "SOAP" connection to host "MYWINDOWS2012SERVER"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException: com.ibm.websphere.management.exception.ConnectorNotAvailableException: ADMC0016E: The system cannot create a SOAP connector to connect to host MYWINDOWS2012SERVER at port 8879.
WASX7213I: This scripting client is not connected to a server process; please refer to the log file D:\IBM\SMP\wasclient\logs\wsadmin.traceout for additional information.
WASX8011W: AdminTask object is not available.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[install, MAXIMO, ctgNode01, MXServer, D:/IBM/SMP/maximo/deployment/default/maximo.ear, maximo_host, webserver1]"
Admin objects not loaded. Connection to Websphere is bad
Sleeping and retrying
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

WASX7023E: Error creating "SOAP" connection to host "MYWINDOWS2012SERVER"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException: com.ibm.websphere.management.exception.ConnectorNotAvailableException: ADMC0016E: The system cannot create a SOAP connector to connect to host MYWINDOWS2012SERVER at port 8879.
WASX7213I: This scripting client is not connected to a server process; please refer to the log file D:\IBM\SMP\wasclient\logs\wsadmin.traceout for additional information.
WASX8011W: AdminTask object is not available.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[install, MAXIMO, ctgNode01, MXServer, D:/IBM/SMP/maximo/deployment/default/maximo.ear, maximo_host, webserver1]"

Admin objects not loaded. Connection to Websphere is bad

Could be that Maximo cannot be installed in Websphere through the installer. When I run the "solutioninstaller -action showinstalled -type all" it shows that the Maximo patch is installed.

When trying to go to the Websphere Integrated Solutions Console the page cannot be displayed. I decide to reboot the server first.

Next I did a rebuild and I installed the Maximo application. Maximo is running now :)


So there you have it, Websphere and Maximo on Windows Server 2012.


GNZ

Installation of application MAXIMO failed.

Problem:
I changed some class files to alter the functionality of Maximo. I did a rebuild of the ear file. I 'Uninstalled' the MAXIMO application from websphere.

I Installed MAXIMO again, but the serer did not respond. So i should have waited, but I started a new install of MAXIMO. Now the system is giving met the following error:

"A composition unit with name MAXIMO already exists. Select a different application name.

ADMA5011I: The cleanup of the temp directory for application MAXIMO is complete

ADMA5014E: The installation of application MAXIMO failed.

Used environment: 
Windows 2008 r2 server, 64 bit
Websphere 7.0.0.15
Maximo 7.5.0.5


The Solution:
(Note that all paths mentioned below could be different on your system depending the path where you installed Websphere)

• Stop the MXServer

• Stop the Maximo services;
• IBMWAS70Service - ctgCellManager01
• IBMWAS70Service - nodeagent

• Deleted the "MAXIMO" Directory deleted from:
• D:\IBM\WebSphere\AppServer\profiles\ctgDmgr01\config\cells\ctgCell01\blas
• D:\IBM\WebSphere\AppServer\profiles\ctgDmgr01\config\cells\ctgCell01\cus

• Delete the "MAXIMO.ear" from:
• D:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\config\cells\ctgCell01\applications
• D:\IBM\WebSphere\AppServer\profiles\ctgDmgr01\config\cells\ctgCell01\applications

• Delete all files in the following directories:
• D:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\temp
• D:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\wstemp
• D:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\config\temp

• D:\IBM\WebSphere\AppServer\profiles\ctgDmgr01\temp
• D:\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp
• D:\IBM\WebSphere\AppServer\profiles\ctgDmgr01\config\temp

• Start the Maximo services;
• IBMWAS70Service - ctgCellManager01
• IBMWAS70Service - nodeagent

• Install MAXIMO, all should go well now.

Create a Lookup with table domain in Maximo 7.5.0.5

Goal:
To use a lookup in the Labor application on workorders with a custom created field.

Example:
For each Qualification linked to a Labor we want to record a workorder number. It must be an existing workorder number so the user must select this number from a lookup. The workorder cannot be in status ‘WAPPR’ assigning it.

How to:

Step 1 - Create Table domain

Go the Domains application (located in Sytem Configuration -> Platform Configuration) and click on the 'Add New Domain' button at the bottom right and choose ‘Add New Table Domain’

In the ‘Validation Where Clause’ we state that the entered Workorder number (Will be stored in GNZ_LQWONUM, look below in this post for the configuration of this field) is compared to the workorder number in the workorder table.

WONUM=:GNZ_LQWONUM

In the list the user will get we only want to show workorders that do not have the status WAPPR. Therefor we we fill in the ‘List Where Clause’

STATUS<>'WAPPR'

Click [OK] and click on the Save icon in the Domains application

Step 2 - Create a Lookup

Now we need to create the lookup which will show the values of the table domain. Go to the Application Designer application (located in System Configuraion -> Platform Configuration) and in the ‘Select Action’ menu choose ‘Export System XML’

Click on the export arrow behind the LOOKUPS rows

Make sure your browser allows popups so the LOOKUPS.XML can be showed by Maximo. Or maybe your browser wants to save the file directly, if so, do so. 

Otherwise, safe the opened LOOKUPS.XML to a location where you can easily locate it again (e.g. desktop)

Now we open the LOOKUPS.XML for editing. (I use Notepad++)

Scroll all the way down and add the following table: 

<table id="GNZ_WONUM" inputmode="readonly" selectmode="single">
<tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="GNZ_WONUM_lookup_tablebody">
<tablecol dataattribute="wonum" id="GNZ_WONUM_lookup_tablebody_col_2" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
<tablecol dataattribute="description" id="GNZ_WONUM_lookup_tablebody_col_3" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
<tablecol dataattribute="reportdate" id="GNZ_WONUM_lookup_tablebody_col_4" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
<tablecol dataattribute="siteid" id="GNZ_WONUM_lookup_tablebody_col_5" mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true" type="link"/>
</tablebody>
</table>

Essentially I copy-pasted the existing 'workorder' table in the LOOKUPS.XML and changed the 'workorder' names to 'GNZ_WONUM'

Save the LOOKUPS.XML and in Maximo go to the Application Designer.

Click on the 'Import Application Definition' icon. 

Browse to the modified LOOKUPS.XML and import it.

Step 3 - Configure the (Object) Database Attribute

Next we add a database attribute on the Labor - Qualification in which we store the workorder number.

Open the 'Database Configuration' application (located in System Configuration -> Platform Configuration) and in there open the LABORQUAL object and go to the 'Attributes' tab.
In the bottom right click the [New Row]  button

Fill in the attribute like in the screenshot below

I use the 'Same as Object' and 'Same as Attribute' fields so the 'Type' and 'Length' will always be able to store Work Order numbers. When the WORKORDER.WONUM field should be modified, this field is modified automically.

Click on the Save icon and go back to the 'List' tab. Do an empty search and the LABORQUAL obejct will come out on top with the status 'To Be Changed' 

In the 'Select Action' menu choose 'Manage Admin Mode' and click on the [Turn Admin Mode ON] button.

Wait until the Admin mode is on and click [Close]

Now in the 'Select Action' menu choose 'Apply Configuration Changes' 
Check the 'Do you have a current backup?' box and click on the [Start Configuring the Database] 

When completed, click on the [OK]  button.
Choose 'Manage Admin Mode' again from the 'Select Action' menu and turn admin mode off.

Step 4 - Configure the MAXLOOKUPMAP

Open the LABORQUAL Object again and go to the Attributes tab.
At the far right of the GNZ_LQWONUM field, click on the 'Edit Lookup Map' icon.

Fill in the information required to link the fields:

Click [OK]  when done and make sure to save the Object.

Login to the Websphere Integrated Solution Console and restart the 'MXServer' 

Step 5 - Configure the field in Application Designer

Open the Application Designer application. and open the LABOR application.

Go to the Qualification tab and make a copy of the Certificate# field. Edit the properties of the field to match them as in the screenshot below.

Save the Application.

Now for the check if everything works.
Go to the Labor application and open an Active labor.

Go to the Qualifications tab. Add a new row and check the Work Order field with the lookup:

GNZ.

Install the Maximo Scheduler 7.5.2 on Maximo 7.5.0.5

Goal: Install Maximo Scheduler 7.5.2 on Maximo 7.5.0.5

Example:We want to use Maximo Scheduler 7.5.2 on our Maximo 7.5.0.5 environment.

Environment:
Windwos Server 2003, SQL Server

How to:

Note; You do not need to stop the MXServer before you begin, the MXServer will however be shutdown in one of the following steps.


Run the Launchpad.exe as the same user you installed Maximo with (use the launchpad64.exe if you install on a 64 bits server)

If you run the launchpad.exe as an other user, the installer cannot find the location of the ctg_install.locations and will display an error when you click on the 'Install Product' link the left. 


ERROR: The Launchpad is unable to locate a path to Tivoli's Process Automation Engine installation. This product cannot be installed without Tivoli's Process Automation Engine. Please make sure the path is correct in the ctg_install.locations file located under your Administrator's home directory. For additional assistance please contact IBM Support.

When you use the correct user you get the following screen, there we click on the 'IBM Maximo Scheduler 7.5.2' link 

Click on [OK] in the next screen

Click on [Next]  in the 'Package Validation Results' screen

In the 'Software License Agreement' screen accept the agreement and click [Next]

Do not select any on the options in the 'Package Options' screen.

In the 'Middleware Login Information' screen you have to fill in the correct information on all three tabs (Maximo DB, WebSphere Admin, Websphere Remote) and click [Next]  when finished.

The installer will now do a 'System Check' 

When finished, review the results, and if all is good, click [Next] 

The Deployment process is now shown

Maximo will be shut down by this proces now. So it you didn't stop the MXServer, the Installer will as you see in the screenshot below by the 'Last Action' 

At the end The following error shows up: 

CTGIN0143E: An action error ocurred during the processing of a deployment operation. Action identifier: "Deploy_Maximo_Help_EAR". Action display name: "Deploy the Maximo help EAR using the WebSphere thin client".

I decide to click the [Cancel] button and to check Websphere.
I log in to Websphere Integrated Solutions Console and go to the Applications -> Application Types -> Websphere enterprise applications.
There the MAXIMO and MXIEHS are running.

I go to Maximo and it is running, i log in and check the Help -> System Information

Then i check the Help

Everything seems ok to me. Maybe the error was because of a timeout. I had this before when you let the installer do the rebuild and redeploy but the server is slow (often the case on a test virtual machine)

Next i check the Scheduler. Click on the Go To menu on Planning and Scheduling en choose 'Scheduler'

The Scheduler application is now available.

GNZ