Creating a Calendar in Maximo

The following document will explain how to create a Calendar in Maximo

1. Go To Administration and open the Calendar Application

2. Create the Calendar by going to Insert menu.

3. Add the Organization Identifier.

4. On the Calendar Field type “TEST”

5. On the Start Date; Click on the Detail Button and select January 1, 2009 and on the End Date;
Click on the Detail Button and select December 31, 2009 and press Enter 

6. Go to Actions Define Apply/Shifts.

7. Click the Insert Row button

8. Here you need to fill out the Shift—Description—the Start Day and Days in Pattern as an example; we could use

TEST as the Shift – Test Shift as the Description—SUNDAY as the Start Day and 7 as the Days in Pattern

9. Click OK and now you need to highlight the row that we just add it and click on the Define Pattern;
10. Here you need to fill the Start Time—End Time—and this will calculate the Work Hours
11. Click OK this will bring you back the previous dialog box.

12. Click Close to exit the dialog box.

11. Now click on the Actions menu and select Define Apply/Shifts…
12. Highlight the Shift that you just created in this practice is TEST and click Apply Shifts.

Configuring a Start Center for multiple language environments In Maximo.

To configure a start center for multiple languages, complete the following steps:

1. Create 2 users. Set the language for one user to the base language (in this example, English) and the other to a non-base language (in this example, Dutch). Both users belong to maxadmin group.
2. Log in as an English (base language) user. Click Create New Template to create a new template. Name the template English template.
3. Add Favorite Applications, Result Set and KPI List to the template. Set up each portlet by adding applications, KPI, etc
4. Save the template.
5. Go to Security Groups. For the MAXADMIN group, in the Start Center Templatefield, specify the new template.
6. Save the record and log out.
7. Log in as a Dutch user. The Start Center called English Template has mixed languages, as shown in the following image. This is expected. To view the start center in Dutch, complete the following steps.
8. Click Edit Template and select English Template. This should be done by the Dutch user.
9. Click Edit for the Favorite Applications. Edit the description field. Save the record.
10. Also edit Result Set and its description fields.
11. Edit the KPI List as well. After all fields are translated, the Start Center is displayed as shown in the following image:
12. After clicking Save Template, you can see the current Start Center has not been translated yet.
13. Click Update Start Center and click Yes to re-apply the template.
14. Once it's updated, the Start Center is displayed in Dutch.
15. The English user sees the Start Center in English even after updating Start Center.
16. To see the template label in Dutch, select Change/Content Layout and modify the description field.

Deleting an Application in Maximo.

As a developer in Maximo, you end up either creating a new app (in app designer) to test something, or cloning existing apps. However, you probably noticed that there isn’t an option to delete an application. As it turns out, to delete an application in Maixmo, you have do to it from the database. Here is how.

What you will need:

·         Name of the application. This must be an all caps. In the code below, replace {MYAPP} with the name of your application.

·         Name of the module you placed your app under. In the code below, replace {MODULENAME} with the name of the module you used.

·         A tool for running SQL statements against the database.

·         DELETE rights to the following tables in the Maximo schema/database:

o    MAXAPPS

o    MAXPRESENTATION

o    SIGOPTION

o    APPLICATIONAUTH

o    MAXLABELS

o    MAXMENU

o    APPDOCTYPE

So now the fun begins. Execute the following statements:

   1:  DELETE FROM maxapps WHERE app='{MYAPP}';

   2:  DELETE FROM maxpresentation WHERE app='{MYAPP}';

   3:  DELETE FROM sigoption WHERE app='{MYAPP}';

   4:  DELETE FROM applicationauth WHERE app='{MYAPP}';

   5:  DELETE FROM maxlabels WHERE app='{MYAPP}';

   6:  DELETE FROM maxmenu WHERE moduleapp='{MYAPP}' AND

       menutype !='MODULE';

   7:  DELETE FROM maxmenu WHERE moduleapp='{MODULENAME}'

       AND elementtype='APP' AND keyvalue='{MYAPP}';

   8:  DELETE FROM appdoctype WHERE app= '{MYAPP}';

Now just stop and start the application server and the application is gone. Now wasn’t that simple. As you execute each statement, they may not find any records to delete. Also, if you added any system XMLs for your app (like lookups), then you will need to export the System XML and manually remove them and then re-import. (Or just import the copy of the system XML you should have made before you started your changes.)

Steps to Create Maximo Location hierarchy creation.

When creating a Location Hierarchy for a site in Maximo please follow the steps below:

1. When creating the new Location you must first insert the new location and the type of 'Operating', then save the record.

2. From the Select Action menu, choose Manage Systems.

3. Insert a new row and name the system what ever you like, click Done and then OK.

4. Now you must go back to the Select action menu and choose the 'Associate Systems with Location' option.

5. Then press 'New Row', then the Detail button next to the system id field and choose your system.

6. Press OK and then Save.

You have now created the new Top Level Location in the System and are now ready to continue to build your hierarchy.

Steps for 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/Linuxdb2iset -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