Capturing the Hostname on a Ticket

You can configure the SmartCloud Control Desk to automatically store the hostname/IP of a user's workstation (client machine or machine connection to SmartCloud Control Desk) in a ticket (Service Request, Incident or Problem) when the ticket is created by following these steps.

1.     Add new field to TICKET named CREATEDBYHOST

2.     Set the default value of CREATEDBYHOST to 127.0.0.1

3.     Create a relationship named 'CREATEDBY' on object SR (of INCIDENT, PROBLEM) with child object: PERSON
where clause: personid=:createdby)

4.     Create a crossover domain named SESSION2TKT on object MAXSESSION
from field CLIENTHOST to field CREATEDBYHOST and
validation where clause:userid=:CREATEDBY.USER.MAXSESSION.userid
list where clause:userid=:CREATEDBY.USER.MAXSESSION.userid

5.     Associate the SESSION2TKT domain with CREATEDBYHOST

6.     Save all changes and run configdb

In order to capture the hostname of the user's workstation (client machine) and not just the IP address, your web server must be configured to perform reverse DNS lookups.

To enable reverse DNS lookups in the IBM HTTP Server do the following:

1.     Edit the httpd.conf file (located in Program Files\IBM\HTTPServer\conf\httpd.conf on Windows

2.     Find the line that says: HostnameLookups off

3.     Change the line to say: HostnameLookups on

4.     Save the file and restart the web server

How to Change the Drilldown limit in Maximo

1. Go to the Application Designer application
2. Select the Action "Export System XML"
3. Highlight the line Library in the Export System XML dialog and click on the Export XML icon,.

4. Using the "save as" option, save two copies of this file. Name one of them library.xml and the other library.xml.bk, which will serve as a backup.
5. Open library.xml in a text editor
6. Find the string
7. insert maxchildren="200" directly after it.

Note: this will change the display limit for Location children to 200. You may designate another limit by selecting another numeric value.

Note: You should find only one "non commented" occurrence of the string

The changed section of the library.xml file should look like the section below. The inserted string is shown in bold:

8. Find the string
9. insert maxchildren="200" directly after it.

Note: this will change the display limit for Asset children to 200. You may designate another limit by selecting another numeric value.

Note: You should find only one “non commented” occurrence of the string

10. Save library.xml
11. On the Application Designer main tab, select the Import icon, and browse to the library.xml file that you have updated.

12. Click OK to import the file.

Changing the look and Feel of Maximo 7

To apply the new GUI skin globally to all of the applications, perform the following steps:

1. At the administrative workstation, go to the following directory:

%CCMDB_home%\applications\maximo\properties

2. Open the webclient.properties file in a text editor.

One of the key-value pairs in the webclient.properties file is the following; the pound sign (#) indicates that the webclient.skin=tivoli09 property is disabled:

#webclient.skin=tivoli09

3. To enable the webclient.skin=tivoli09 property, remove the pound sign (#) at the beginning of the line, and save the webclient.properties file.
4. Rebuild and redeploy the Maximo enterprise archive (EAR) file.

You rebuild and redeploy the Maximo EAR file from the IBM® WebSphere® Application Server. For instructions for performing this task, see the "Working with EAR files" section of the IBM Change and Configuration Management 7.1 System Administrator Guide.

After you turn on the webclient.skin=tivoli09 property and rebuild the EAR file, the product GUI will use the new skin. You can turn this property off if you want to revert to the previous skin, or if you install a CCMDB product that does not support the new skin. To do so, open the webclient.properties file, insert a pound sign before the webclient.skin=tivoli09 key-value pair, and rebuild and redeploy the Maximo EAR file.

Changing hostname of the DB2 server

1) Login as the dasadm user on UNIX/Linux or Local Administrator on Windows. Stop the DB2 Administration Server (DAS):

db2admin stop

2) Login as the instance owner on UNIX/Linux or Local Administrator on Windows. Stop the DB2 instance:

db2stop

3) Change the server's hostname. On a Windows system, a reboot is required before this change will take effect. Do not reboot the Windows Server at this time - you must make the DB2 Configuration changes first.

4) Login as user ROOT if DB2 is on UNIX/Linux and Local Administrator on Windows. Update the DB2SYSTEM registry variable while in the instance home directory:

o    UNIX/Linux
db2iset -g DB2SYSTEM= 

o    Windows 
db2set -g DB2SYSTEM=

5) Locate db2nodes.cfg in one of the following directories:

·         UNIX/Linux:
/sqllib/db2nodes.cfg

·         All Windows flavors running DB2 v8 and v9.1: 
Program Files\IBM\SQLLIB\DB2\db2nodes.cfg 

·         Windows XP and 2003 running DB2 v9.5: 
Documents and Settings\All Users\Application Data\IBM\DB2\\DB2\db2nodes.cfg

NOTE: Application Data is a hidden folder

·         Windows Vista and later operating systems: ProgramData\IBM\DB2\\DB2\db2nodes.cfg

Note that only DB2 ESE has a db2nodes.cfg. If you are running other editions (WorkGroup Server, or Personal Edition) then you can skip this step and the next.

6) In the db2nodes.cfg file change to .


7) Run the following command to list the current hostname/system name that is cataloged:

db2 list admin node directory show detail 

If there are no Admin Node Directory entries then you can skip the next 2 steps. It simply means that you haven't started the Control Center. The Admin Node Directory will get updated the next time the Control Center is started, based upon the current hostname.

8) Uncatalog the current hostname using this command:

db2 uncatalog node

9) Catalog the admin node with the new hostname using this command:

db2 catalog admin tcpip node remote system  

 can be anything you want it to be (8 characters or less). It does not relate directly to the hostname itself.

10) Update the admin configuration file using these commands:

db2 update admin cfg using DB2SYSTEM  
db2 update admin cfg using SMTP_SERVER

11) At this time, you should restart your server if running Windows. Note that if your instances are set to auto-start, you may get error messages. These will occur if you have DB2_EXTSECURITY enabled. To correct this, you will need to update the DB2_ADMINGROUP and DB2_USERSGROUP registry entries using the db2extsec command. See the 'note' at the end of this technote for more details.

12) Login as the dasadm user on UNIX/Linux or Local Administrator on Windows. Start the DB2 Administration Server (DAS):

db2admin start

13) Login as the instance owner on UNIX/Linux or Local Administrator on Windows. Start the DB2 instance:

db2start

14) In Control Center find the old hostname under the "All Systems" folder and right click, choose Remove. 

15) In Control Center add the new hostname. Right click on the "All Systems" folder and choose "Add". Click on "Discover" to locate the new hostname.

NOTE:
Starting in v9.1 FP2, DB2 supports the use of domain groups for extended security. Therefore, when you change the computer name and the computer groups DB2ADMNS and DB2USERS are local computer groups, you must update the DB2_ADMINGROUP and DB2_USERSGROUP global registries. Please see the Related URL for instructions on how to do this.

If Windows Extended Security has been enabled then you will need to tell DB2 to lookup the WIndows local groups DB2ADMNS and DB2USERS via the new hostname. For example if the hostname is changed to QASERVER then execute:

db2extsec -a QASERVER\DB2ADMNS -u QASERVER\DB2USERS