When running a Jython script used to configure WebSphere eXtreme Scale I got the following error: connecting to Deployment Manager… WASX7209I: Connected to process “dmgr” on node dmgrMnode using SOAP connector; The type of process is: DeploymentManager WASX7017E: Exception received while running file “/var/was/scripts/configuration_management/Config-test-wxs-aix.py”; exception information: com.ibm.bsf.BSFException: exception from Jython: Traceback (innermost last): (no code.. read more →

Some simple concepts that help with using Jython to deploy applications. When installing an application and you want to know all the options for binding resources and virtual hosts etc in your Jython script, the quickest way to learn is to record a deployment using the console. In my example I am using WebSphere Application.. read more →

When a WXS ENV was created FQDN for some DNS was wrong.  DNS entries for a catalog server  and a container  server  wrong, because the LPARS had been built at a later date to the other nodes in the cell. So when the nodes were federated, WAS recorded the results of DNS resolver on the.. read more →

When the Catalog (cat) Node04 was created, the DNS was wrong. This means that when the catalog service domain was created the DMGR did a reverse look-up to find the FQDN for the cat 04’s IP Address. At that time it got it wrong. So essentially it stored the dat04’s (WXS Container 04) hostname as.. read more →

This error occurs when you have one container server left and you stop that server and start it up quickly after stopping it. The issue is that the catalog server doesn’t know it went down yet. It can take up to 30 to 40 seconds to detect the server went down depending on your.. read more →

When a WAS cell is created to use the DMGR and NodeAgents for the catalog service, it means that often later in the cycle of the project, the environment may need to be changed to use a cluster with JVMs as the catalog service. The reason for this is that we can stop and start.. read more →

Catalog service domain: A catalog service domain (or simply domain) is one or more grids (set of containers) and their controlling catalog service. The concept of a domain is similar to a “cell” in WebSphere Application Server Network Deployment. Catalog service domains define a group of catalog servers that manage the placement of shards and.. read more →

The WebSphere eXtreme Scale web console is a useful web based application that presents run-time statistics in a visual manner. Installing and using the web console is documented in detail in another blog entry. By default the web console binds to port 7080 for HTTP and 7443 for HTTPS. In some cases it is desirable.. read more →

Problem When installing WXS 7.1 standalone on 64 bit AIX, the installer will detect a 64 bit operating system and install the 64 bit version (i.e. including a 64 bit JRE). However the web console component actually requires a 32 bit JRE, which is not installed with the product. Solution Obviously, administrators can install a.. read more →

<wxs_profile_root>/bin>xsadmin.sh -dmgr -p 10003 -placementStatus This Administrative Utility is provided as a sample only and is not to be considered a fully supported component of the WebSphere eXtreme Scale product Connecting to Catalog service at localhost:10003 Realm/Cell Name: defaultWIMFileBasedRealm User Identity: wasadmin User Password: ************Printing Placement Status for Grid – MySession, MapSet – mapSet************** <objectGrid.. read more →