VMWare - Guest operating system static IP address

1. Note the MAC of the VM
2. On the host machine open C:\ProgramData\VMware\vmnetdhcp.conf
    a. Or C:\Documents and Settings\All Users\Application Data\VMware\vmnetdhcp.conf
    b. These 2 files are auto synced or mirrored.
    c. Open the editor in Administrator mode. Eg notepad++. Otherwise you will get access denied message
3. Add a new entry at bottom of the configuration file, right before the "# End" marker. MyGuestVM is any unique name. Example below

host sunilW2008Server {
hardware ethernet 00-0C-29-05-2B-A0;
fixed-address 192.168.63.222;
}

3. Shutdown the VM and close the Workstation
4. Re-start the VMWare DHCP and NAT services for changes to take effect (From services.msc)

How to Delete Websphere Application Server Profile ?

First list all profiles on a server:

List the profile using one of these commands

• Windows: was_install_dir\bin\manageprofiles.bat –listProfiles
• UNIX/Linux: was_install_dir/bin/manageprofiles.sh –listProfiles

Remove a WebSphere Application Server profile:

Delete the profile using one of these commands:

• On Windows: was_install_dir\bin\manageprofiles.bat –delete –profileName profile
• On UNIX/Linux: was_install_dir/bin/manageprofiles.sh –delete –profileName profile

Ensure that references to the deleted profile are removed from the profile registry by running the following command:

• On Windows: was_install_dir\bin\manageprofiles.bat –validateAndUpdateRegistry
• On UNIX/Linux: was_install_dir/bin/manageprofiles.sh –validateAndUpdateRegistry

Delete the profile directory tree (if it was not deleted by the previous action).

Delete the profile Directory using one of these commands:

• On Windows: was_install_dir\profiles\rmdir /s profileDirectory
• On UNIX/Linux: was_install_dir\profiles\rm -R profileDirectory

Websphere - Windows service for Nodeagent, AppSrv creating example

Creating Service for Application Server (JVM):

WASService.exe -add ServiceNameAppSrv01 -serverName server1 -profilePath c:\IBM\WebSphere\AppServer\profiles\AppSrv01

Creating Service for Nodeagent:

WASService.exe -add ServiceNameNodeAgent01 -serverName nodeagent -profilePath c:\IBM\WebSphere\AppServer\profiles\CustomNode01

Deleting service:

WASService.exe -remove SrvNameAppSrv01

or

WASService.exe -remove ServiceNameNodeAgent01

How to Delete a Windows Service

Deleting a Service

The first thing you’ll need to do is identify the name of the service, so open up Services through the start menu or control panel, and then find the service in the list that you want to delete.

You’ll want to open up the properties by double-clicking on the service name, and then highlight the “Service name” value and copy it to the clipboard. This is what we’ll need to disable it.

You’ll need to open up a command prompt, you’ll need to right-click the command prompt and choose Run as Administrator. We’ll use the sc command to actually do the work.

The syntax used to delete a service is this:

sc delete ServiceName

If your service name has spaces in it, you’ll need to wrap the service name in quotes, like this:

sc delete “Adobe LM Service”

manageprofiles command - WAS Administration

Link to IBM Knowledge Center

Maximo and Websphere 8.5.5 - Did you forget the plug-in configuration?

You've downloaded and installed WebSphere 8.5.5, the IHS and the Plugin. You have everything up and running, Maximo deployed and want to use the web server to access Maximo or load balance to multiple JVM's, so why isn't it working? Why are you receiving "Page Not Found" errors? In most cases it's likely a key step was missed that is automated with the Middleware\Maximo install when using WebSphere 7, that step is the Plugin Configuration.

During the install of WebSphere 8.5.5, you may of only installed the Application Server, HTTP Server and the Plug-in files, however you also need to install the WebSphere Customization Toolbox which contains the configuration tool for the web server plug-in. Below we will go over the install and how to configure your your Plugin.

Configuring your WebSphere Plug-in for Maximo

1. The first step if you haven't already is to install the WebSphere Customization Toolbox, you can do this using the Installation Manager and the package is contained in the WebSphere Supplemental Repositories.

Configuring the WebSphere Application Servers to start when the nodeagent starts

WebSphere Application Servers

Configuring the WebSphere Application Servers to start when the nodeagent starts


1. Log into the Integrated Solutions Console.
2. Navigate to Servers > Server Types > WebSphere application servers.

Hiding Classifications And Making it Unavailable In Maximo

The following is an attempt to make classification invisible and not usable in the future.

1. Create a new user-defined field OBSOLETE for CLASSSTRUCTURE/

Go to Database Configurations – bring up object CLASSSTRUCTURE:
Switch to Attributes tab and click New Row and enter OBSOLETE as the following example:

Configure the database. Log out and log back in.

Creating a Windows service for the node agent

In a network deployment configuration, you can create the node agent as a Windows service to make WebSphere® Application Server nodes easier to start and manage.

About this task

Create the node agent as a Windows service so that the node agent starts automatically when the server is rebooted. An activated node agent communicates with the cell Deployment Manager to manage the set of servers on the node.

If you do not create the node agent as a service, you must run the startNode command manually. For example: <was_home>/profiles/<profile_name>/startNode.bat.

Procedure

1. Open a command prompt window.
2. Change the directory to <was_home>\bin. For example: type cd c:\Program Files\IBM\WebSphere\AppServer\bin
3. Type the following WASService command with the following parameters (case-sensitive, without the line breaks):

   WASService -add <profile_name>_nodeagent -serverName nodeagent -profilePath 
   "<was_home>\profiles\<profile_name>" -wasHome 
   "<was_home>" -logRoot 
   "<was_home>\profiles\<profile_name>\logs\nodeagent" -logFile 
   "<was_home>\profiles\<profile_name>\logs\nodeagent\startServer.log" 
   -restart true
   -startType automatic

   Where

   <was_home>

   Specifies the directory where WebSphere Application Server is installed. For example: C:\Program Files\IBM\WebSphere\AppServer

   <profile_name>

   Specifies the name of the custom node profile in Windows service. For example: Custom01.

   Example (with sample values)
   WASService -add Custom01_nodeagent -serverName nodeagent -profilePath "c:\Program Files\IBM\WebSphere\AppServer\profiles\Custom01" -wasHome"c:\Program Files\IBM\WebSphere\AppServer" -logRoot "C:\Program Files\IBM\WebSphere\AppServer\profiles\Custom01\logs\nodeagent" -logFile"C:\Program Files\IBM\WebSphere\AppServer\profiles\Custom01\logs\nodeagent\startServer.log" -restart true -startType automatic
4. Press Enter. For example: The last line of the screen is displayed.

   IBM WebSphere Application Server V7.0 - Custom01_nodeagent service successfully 
   added.

5. Close the command prompt.
6. Verify that the service is added to Windows services.
   1. Click Start > Run. Type services.msc.
   2. Verify that the node agent service is displayed. For example:IBM WebSphere Application Server v7.0 - Custom01_nodeagent.
7. Optional: If you have additional nodes, repeat this task for other nodes in your cluster. For example: Custom02.

Results

You added the node agent service to the list of Windows services.

Using WASServiceCmd to create Windows services for WebSphere Application Servers

http://goo.gl/YWuX5t

SWF

Overview of the usability enhancements in Maximo Asset Management V7.6

Youtube Video: Overview of the usability enhancements in Maximo Asset Management V7.6

Configuring the usability enhancements in Maximo Asset Management V7.6

Youtube Video: Configuring the usability enhancements in Maximo Asset Management V7.6

Maximo Reporting Documentation

Link: Maximo Reporting Documentation - Wiki

Maximo Integration Framework (MIF). Which Components to Use?

How do I determine which integration components to use for my integration scenario?

This is a common question for those who are not familiar with the I-F.  Reasons for choosing the use of certain I-F components is often decided based on one or more of the following:

1. The integration capabilities of the application being integrated to Maximo
2. The integration skills of the developers who will implement the integration
3. The need to have the integration processing occur in a synchronous or asynchronous manner
4. What level of error management is required and what level is supported by the external application
5. Do integration messages need to process based on events (ie. approval of a Work Order)
6. Does the integration need to operate in a batch or real-time (near) mode.
7. Is the I-F being used to support implementation data loading
8. Will the integration be deployed using a common ESB layer within your enterprise

The above list is not intended to be all-inclusive, but it should give you an idea of the types of things to consider when planning integration with Maximo.  Keep in mind, large integration deployments could involve many systems and require different integration components to be used for different external applications.