PM81765: Need clarifications for the permissions requirement for starting a remote WebSphere Application Server instance

Rational Application Developer for WebSphere Software 9.0
Rational Software Architect 9.0
Rational Software Architect for WebSphere Software 9.0
Rational Software Architect 8.5.5
Rational Software Architect for WebSphere Software 8.5.5
Rational Application Developer for WebSphere Software 8.5.5
Rational Software Architect Fix Pack 1 (8.5.5.1) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 1 (8.5.5.1) for 8.5.5
Rational Application Developer for WebSphere Software Fix Pack 1 (8.5.5.1) for 8.5.5
Rational Software Architect Fix Pack 2 (8.5.5.2) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 2 (8.5.5.2) for 8.5.5
Rational Software Architect Fix Pack 3 (8.5.5.3) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 3 (8.5.5.3) for 8.5.5
Rational Application Developer for WebSphere Software Fix Pack 2 (8.5.5.2) for 8.5.5
Rational Software Architect Fix Pack 4 (8.5.5.4) for 8.5.5
Rational Software Architect for WebSphere Software Fix Pack 4 (8.5.5.4) for 8.5.5
Rational Application Developer for WebSphere Software Fix Pack 3 (8.5.5.3) for 8.5.5

APAR status

• Closed as documentation error.

Error description

• Abstract:
  
  Attempts to start a remote WebSphere Application Server from
  Rational Application Developer might result in failure if you do
  not have the correct privileges.
  
  Problem:
  
  The server administrator has assigned start server and stop
  server authority to developer users. A developer logs on to the
  Linux machine with his user id and perform a super user command.
  He can start and stop the server without issue.
  
  When the developer uses the same user id to start the WebSphere
  Application Server remotely inside Rational Application
  Developer, the operation fails.
  
  The reason is the developer is only given start and stop server
  authority, but they require full access to the remote WebSphere
  Application Server profile, especially on Linux, Windows 7 or
  Windows Server.
  
  The documentation for starting a remote WebSphere Application
  Server needs to explicitly state that the user for working with
  the remote server instance needs full privileges to the profile
  being used.
  
  Local fix:
  
  You can start and stop the WebSphere Application Server on the
  remote machine directly using the required user id.  The server
  status will automatically be synchronized with the remote server
  in the Rational Application Server workbench.
  

Local fix

Problem summary

• In the product documentation under Starting a remote WebSphere
  Application Server point 7.
  This graphic is a Linux icon. On Linux:
  /opt/<install_directory>/profiles/<profileName>
  Remember: On Linux, using /opt/ assumes you have root
  authority. If you are not a root user create or use an empty
  directory in a location where you do have write access.
  This has to be improved and clarified.
  

Problem conclusion

• In the 'Starting a remote WebSphere Application Server' help
  topic, the 'Restriction' in step #7 has been replaced with the
  following text:
  'Important: You must have full access to the WebSphere Applicati
  on Server (and the paths) on Linux systems, with read, write,
  and execute authority. It is not sufficient to have authority
  to start and stop the server, or read and write access to
  specific files.'
  The fix for this APAR is included in Rational Application
  Developer v8.5.5.
  

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