IBM Maximo: Rebuilding and Deploying maximo.ear

In this video you can see how to rebuild and deploy maximo.ear for IBM Smart Cloud Control Desk 7.5.1

Changing configured database, password, server names in Maximo v7

The installation properties are maintained in the Maximo database, and the maximo.properties file. These are required for fixpack installations, and other product installations. Over time passwords may change, hostnames/ip-addresses or database names may change. In order to update these values, follow these instructions:

1. Update the \ibm\SMP\maximo\applications\maximo\properties\maximo.properties file on the Admin Workstation to change the IP-Address/Hostname for either the database server or the webserver. Also to update the password
a. Delete the file named maximo.properties
b. Rename the file named maximo.properties_orig to maximo.properties (this is an unencrypted file)
c. Edit the maximo.properties file and update the hostname/IP-address for the database server.
d. If necessary, update the password for the user to access the database
e. Save the file
Note: The file will be automatically re-encrypted when you install a fixpack or other product. If this is not an immediate activity, you can run encryptproperties.bat file located in C:\ibm\smp\maximo\tools\maximo directory against the file to encrypt it.
2. Update the \ibm\SMP\etc\install.properties file on the Admin Workstation to change the IP-Address/Hostname for either the database server or the webserver.
3. Update the values in the maximo database to change the IP-Address/Hostname for a variety of servers, or to update passwords.
a. Connect to the maximo database using your favorite SQL editor utility.
b. Query the maxpropvalue table, and find the key you need to edit. For example, WAS.DeploymentManagerHostName is the key for the hostname or IP address of the WebSphere machine.
c. Create a query to update that value to the new value, and run the query.
d. Repeat for any passwords, ip addresses etc that need to be updated.
4. Rebuild and redeploy the EAR files.

Maximo bind variables

We use bind variables a lot in maximo. We are familiar with relationships like “LOCATION=:LOCATION and SITEID=:SITEID”, and conditions like “:CLASS='INCIDENT'”. “:LOCATION”, “:CLASS” are maximo bind variable. They are resolved to the actual value of the specified attribute of the current business object. Current business object means the object that the expression is evaluated against. Depending on the context, it is the parent object that the relationship is defined on, or the object a condition is evaluated against.

Less familiar to us, is that there is an additional set of bind variables that are not resolved to the values of attributes, instead, have their own special meanings and can also be used in maximo expressions.

:&OWNER&

It represents the MBO object that is the owner of the current MBO. This is always used with combination to field name or relationship name. Such as :&OWNER&.ATTR1 or:&OWNER&.RELATIONSHIP2.ATTR2. It is used when you need to get to a value of an object on the owner MBO or through one or multiple relationship from the owner MBO. This comes extremely handy if the current record has not been saved to the database and you need to get its value or its related value.

Maximo Post Install configuration

Login to maximo console http://localhost/maximo/ui using administrator privileges and perform the following steps.

1. Create an organization with Site:

• Create Currency codes:
• Goto Financial->Currency codes.
• Click on New row.
• Enter a name (ex:- USD).
• Enter description (ex:- United States Dollar).
• Save.

DB2: Восстановление бэкапа базы в существующую базу с другим именем

Предположим мы сняли резервную копию с базы, которая называлась DB2Z, в результате получив файл с таким именем: DB2Z.0.DB2_06.NODE0000.CATN0000.20100930232346.001

Замечаем закономерность, что первая часть имени файла совпдает с алиасом базы данных. На самом деле так и есть. Однако неверно думать, что для того чтобы восстановить резервную копию в существующую базу данных с другим именем, достаточно переименовать файл резервной копии. Имя файла резервной копии следует воспринимать просто как подсказку о том, что она была:
• Получена с базы данных с таким-то алиасом
• Числовое представление типа резервной копии такое-то (0 для полной копии базы, 3 для копии табличного пространства, 4 для копии полученной с помощью LOAD)
• База данных обслуживалась экземпляром (instance) DB2 с таким-то именем
• Копия содержит такой-то узел базы данных (всегда NODE0000 для однораздельных БД)
• Номер каталога узла (всегда CATN0000 для однораздельных баз)
• Время снятия резервной копии
• Номер образа