2/24/2015

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)

2/21/2015

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”

2/18/2015

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.