PH05192: CONTINUATION OF CORRECTIONS TO THE DOCUMENTATION IN THE KNOWLEDGE CENTERS FOR IBM WEBSPHERE APPLICATION SERVER V8.5.5

APAR status

• Closed as documentation error.

Error description

• This APAR is a continuation of APAR APAR PI94535. It addresses
  issues that customers encountered with IBM WebSphere Application
  Server Version V8.5. These issues were resolved as
  knowledge center updates for March, 2018.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  This APAR provides a cumulative list of     *
  *                  the documentation issues for                *
  *                  March, 2018 that affect users of IBM        *
  *                  WebSphere Application Server Version 8.5.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Knowledge Centers for WebSphere     *
  *                      Application Server Version 8.5 need     *
  *                      to reflect customer enhancement         *
  *                      requests received in problem            *
  *                      management records (PMRs). These        *
  *                      enhancements can include fixing         *
  *                      technical inaccuracies or clarifying    *
  *                      vague information.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  See the Problem conclusion section for a description of the
  issues, which are described in customer PMRs, and the
  documentation change or changes that will address these issues.
  

Problem conclusion

• Note: We update our knowledge centers regularly. The
  following Version 8.5 modifications will be available in the
  March, 2018 update to the Knowledge Centers. To access the
  latest on-line documentation, go to the product library page at
  http://www.ibm.com/software/webservers/appserv/library and
  select the version and product that is appropriate for your
  WebSphere Application Server environment.
  
  The following Version 8.5 issues will be addressed:
  
  ID: 785995
  Problem: There is a requirement to know which high
  availability (HA) deployment manager was in active or standby
  state when deploying an application - and also to know to
  deploy the application via the ODR and not by the HA deployment
  manager. Additionally there was a need to get the
  active/standby status using a wsadmin script. Current topics
  in the knowledge center were incomplete in fulfilling this
  requirement.
  
  Resolution: Two existing topics were updated and one NEW topic
  was created to resolve this documentation problem.
  (1) Topic, The high availability deployment manager, was updated
  with a NOTE on how to access the admin console via the ODR.
  The update is as follows:
  NOTE: After the HA deployment manager is set up, you do not
  access the administrative console on the deployment manager
  system but through the ODRs. As an example, use:
  
  If computer C is odr1, then access the administrative console
  as follows:
  
  http://odr1:port number/admin
  where port number is the port number configured by the value,
  WC_adminhost_secure or WC_adminhost.
  
  instead of
  
  http://dmgr1:port number/admin
  
  ALSO in this topic the following paragraph was added in the
  Configuration section:
  All administrative operations are performed through the
  elected active deployment manager. The standby deployment
  manager is fully initialized and ready to do work but cannot
  be used for administration. This is because the administrative
  function does not currently support multiple concurrent server
  processes writing to the same configuration. Therefore, the
  standby rejects any login and JMX requests. However, if the
  active deployment manager is stopped or fails, the HA
  deployment manager component recognizes the loss of the active
  deployment manager and dynamically switches the standby into
  active mode, so it can take over for the lost deployment
  manager.
  
  (2)Topic, Configuring a high availability deployment manager
  environment, is updated as follows:
  Under the step 2 section: To CREATE a new cell with an HA
  deployment manager configuration:
  - Step 2c adds a NOTE that reads:
  NOTE: The deployment manager profile must reside on the shared
  file system.
  - Step 2f adds the following sentence:
  You can use wsadmin or the administrative console to create
  and configure an ODR on the federated node. Computer C is now
  the ODR system.
  - Step 2g adds the following sentence:
  Computer B is the second deployment manager system and will
  serve as the standby deployment manager.
  - Step 2i is added and reads:
  Restart the deployment managers (computers A and B) and the
  ODRs (computer C).
  
  The first deployment manager that starts is the active
  deployment manager, and the other is the standby deployment
  manager. See topic, "Determine acitve and standby deployment
  managers" for more information on identifying the active and
  standby deployment managers in an HA deployment manger
  configuration.
  
  Under the step 2 section: To CONVERT an existing cell to an HA
  deployment manager configuration:
  - Step 2c adds a NOTE that reads:
  NOTE: The deployment manager profile must reside on the shared
  file system.
  - Step 2i is added and reads:
  Restart the deployment managers and ODRs.
  
  The first deployment manager that starts is the active
  deployment manager, and the other is the standby deployment
  manager. To identify the active and standby deployment
  managers in an HA deployment manger configuration, see topic,
  "Determine acitve and standby deployment managers".
  
  Also, Step 3 in the topic is removed.
  
  (3)NEW topic, Methods to determine active and standby
  deployment managers, is added and reads:
  
  Use these methods in a high availability (HA) deployment
  manager environment to determine what deployment manager is
  active or in standby mode.
  Before you begin
  
  Privileges for the high availability (HA) deployment manager
  differ, depending on the various roles. Roles include monitor,
  operator, configurator, and administrator. If you are a user
  with either a monitor or a configurator role, you can only
  view the HA deployment manager information. If you have the
  role of operator or administrator, you have all the privileges
  for the HA deployment manager.
  
  File sharing is typically accomplished by installing the
  deployment manager on the shared file system. Sharing the
  entire installation is not mandatory, and an alternative is to
  locate only the deployment manager profiles on the shared file
  system. In the scenarios that are described in this topic, is
  installed on the shared file system. For scenarios in which
  only the deployment manager configuration repository and
  workspace reside on the Network Attached Storage (NAS), read
  about the xd_hadmgrAdd command.
  About these methods
  Methods
  
      These methods use the following topology for the HA
  deployment manager environment:
      Computer name  Processes
      A  Deployment manager
      B  Standby deployment manager
      C  Node agent and on demand router
      Method 1 - Use wsadmin
  
      With a HA deployment manager configuration, run wsadmin
  scripts. Invoke wsadmin against the ODRs
  JMX_SOAP_PROXY_ADDRESS. ODR (computer C) shows the active
  deployment manager that is proxied to (computer A). An example
  of this command is as follows:
      <WAS_HOME>/wsadmin.sh -lang jython -conntype SOAP -host
  
      <ODR_JMX_SOAP_PROXY_ADDRESS_HOST_VALUE> -port
  
      <ODR_JMX_SOAP_PROXY_ADDRESS_PORT_VALUE> -user <adminUser>
  -password
      <adminPasswd> -f </path/to/client/script.py>
  
      Method 2 - use the administrative console of the ODR
  (computer C) -
  
      If computer C is odr1, then access the administrative
  console as follows:
  
      http://odr1:port number/admin
      where port number is the port number configured by the
  value, WC_adminhost_secure or WC_adminhost.
  
      Click System administration > Deployment manager > All
  deployment managers to view and manage the configured
  deployment managers in your environment. There should be an
  indicator that shows which deployment manager is active
  (computer A) and which is in standby mode (computer B).
      Method 3 - Check the deployment manager systemout.log to
  determine which server is in active mode and which is in
  standby mode.
  
      Examine the deployment manager systemout.log on either
  Dmgr node. Locate the following messages to determine whether
  the Dmgr is in active or standby mode.
      XHAD0001I: The Deployment Manager process is in standby
  mode.
  
      Explanation: An informational message that indicates that
  this Deployment Manager process is in standby mode.
  
      Action: None
      XHAD0002I: The Deployment Manager process is in active
  mode.
  
      Explanation: An informational message that indicates that
  this Deployment Manager process is in active mode.
  
      Action: None
      Results
      You have identified the active deployment manager and the
  deployment manager in standby mode.
      What to do next
  
      You can continue to manage the deployment managers in the
  administrative console. Click System administration >
  Deployment manager > All deployment managers to view and
  manage the configured deployment managers in your environment.
  
      If you need to remove a high availability deployment
  manager from the cell, use the command line utility to remove
  the function. For more information about removing the high
  availability deployment manager from the cell, read about the
  xd_hadmgrRemove command.
  
  This knowledge center update also applies to level V9.0
  
  ------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels