Let’s say you have WebSphere Application Server base installed on windows. The default installation on Windows maps the WAS profile to a Windows Service. On Windows 7 you are required to start the server in a command console that has the appropriate elevated privileges. If you open a CMD prompt as a non administrator you.. read more →

A good tip to check that your augmented WebSphere Application Server Network Deployment profile has been installed using the correct template is to check the manageprofles.sh log file. The manageprofile command line tool will log to <was_root>/logs. Below is en example of a stanza from the profile creation log.

read more →

Error: ADMU3100I: Reading configuration for server: dmgr ADMU0111E: Program exiting with error: java.io.FileNotFoundException:            /var/was/profiles/my_dmgrProf/config/cells/myhostnameCell/nodes/my_dmgrMnode/servers/dmgr/server.xml            (No such file or directory) Solution: When you created this profile using the manage profile command you used the wrong template. When creating profiles with manageprofiles.sh you need top pass the appropriate profile template. If this WebSphere Application Server.. read more →

WebSphere Application Server stores configuration data in several documents in a cascading hierarchy of directories. Most configuration documents have XML content. The configuration documents describe the available application servers, their configurations, and their contents. Hierarchy of directories of documents The cascading hierarchy of directories and the documents’ structure support multinode replication to synchronize the activities.. read more →

When creating a node manually using the Deployment Manager’s administrative console, I am able to specify the hostname of the node. However when I use the addNode.bat command to federate the new node (node02) , it picks up the deployment manages, hostname. In this example I have a vertical scaled design ie the nodes and.. read more →

[important] Part 4 in a 5 part series Part 1 Part 2 Part 3 Part 5 [/important] Part 4 – Creating a second Node profile Prerequisites: Install WAS 8 ND using the new IBM Installation Manager on a Windows platform. Create a Deployment Manager profile. Create a node profile called node01 Note: It is possible.. read more →

When federating a node to a cell using the addNode.bat or addNode.sh command you get the following error: ADMU0027E: An error occurred during federation ADMU0034E The solution is to add the profile with a unique cell name. I had created a new node profiel using the addNode command, however I had neglected to incoude the.. read more →

When running the manageprofile command line tool to create a second node for a multi node cell I got this error. How I traced the solution was to look at the logs as suggested by the INSTCONFAILIED: The profile could not be created. For more information, consult *.log file.

Browsing through the logs I.. read more →

[important] Part 3 in a 5 part series Part 1 Part 2 Part 4 Part 5 [/important] Part 3 – Creating a Node profile Prerequisites: Install WAS 8 ND using the new IBM Installation Manager on a Windows platform. Create a Deployment Manager profile. Note: It is possible to sue this guide to install on.. read more →

[important] Part 2 in a 5 part series Part 1 Part 3 Part 4 [/important] Part 2 – Creating a Deployment Manager Prerequisites: Install WAS 8 ND using the new IBM Installation Manager on a Windows platform. Note: It is possible to sue this guide to install on Linux. The installation is almost exactly the.. read more →