HD83832: Need to update the documentation regarding 3 Orbix configuration.

APAR status

• Closed as documentation error.

Error description

• Need to update the documentation regarding 3
  Orbix configuration.
  .
  This is inrelation with
  DETAILED DESCRIPTION:
  To activate Single sign on three different orbix
  configurations are
  made, all according to the online documentation,
  (Installation &
  Deployment->Deploying ENOVIA Applications-
  >Deploying Webtop and
  Wintop Applications->Deploying the Web
  Application in an Application
  Server->Configuring Single Sign-On->Activating
  Single Sign-On.):
  .
  Orbix: for batchusers (not SSO) Port: 16000
  Orbix2: SSO for Webtop (LCA Nav) Port: 16300
  Orbix3: SSO for Wintop (VPM Nav) Port: 16600
  .
  When a user is logging on to VPMNav and tries to
  access the vault a
  process for the third orbix process is automatically
  starting up
  That results in problems to save files in the Enovia
  vault. User got
  this error message when trying to save a product
  into the Enovia vault:
  Error An error occured during save sequence. Save
  aborted.
  Warning Cannot update document's data in ENOVIA
  V5 VPM Server.
  .
  Customer Implementation:
  1. One vault defined on the orbix port 16000. The
  VaultClient.properties
  file is configured to port 16000
  2. One orbix port, 16300, defined for SSO in
  Wintop applications i.e.
  VPMNav and LCA classic
  3. One orbix port, 16600, defined for SSO in
  Webtop applications i.e.
  LCANav
  .
  Customer Problem: When you tries to save
  automatically aniother Vault
  Process getting started.
  .
  OJH has anlayse this Issue and found that it is
  limitation on AIX.So As
  per OJH following restriction should be updated in
  the documentation.
  Here is the limitation description :
  .
  Operating System: AIX.
  The Orbix connection from an ENOVIA App Server
  launched by an Orbix
  Daemon A to a Vault Server fails if the Vault
  Server is running on the
  same machine and has not been launched by the
  same Orbix Daemon A.
  .
  By-pass:
  It is recommended to deploy the Vault Server on a
  dedicated machine
  which is not shared with the ENOVIA App Servers.
  If it is not possible to have a dedicated machine,
  then the same Orbix
  daemon has to be used for ENOVIA App Server
  and the Vault Server
  

Local fix

Problem summary

• Need to update the documentation regarding 3
  Orbix configuration.
  .
  This is inrelation with
  DETAILED DESCRIPTION:
  To activate Single sign on three different orbix
  configurations are
  made, all according to the online documentation,
  (Installation &
  Deployment->Deploying ENOVIA Applications-
  >Deploying Webtop and
  Wintop Applications->Deploying the Web
  Application in an Application
  Server->Configuring Single Sign-On->Activating
  Single Sign-On.):
  .
  Orbix: for batchusers (not SSO) Port: 16000
  Orbix2: SSO for Webtop (LCA Nav) Port: 16300
  Orbix3: SSO for Wintop (VPM Nav) Port: 16600
  .
  When a user is logging on to VPMNav and tries to
  access the vault a
  process for the third orbix process is automatically
  starting up
  That results in problems to save files in the Enovia
  vault. User got
  this error message when trying to save a product
  into the Enovia vault:
  Error An error occured during save sequence. Save
  aborted.
  Warning Cannot update document's data in ENOVIA
  V5 VPM Server.
  .
  Customer Implementation:
  1. One vault defined on the orbix port 16000. The
  VaultClient.properties
  file is configured to port 16000
  2. One orbix port, 16300, defined for SSO in
  Wintop applications i.e.
  VPMNav and LCA classic
  3. One orbix port, 16600, defined for SSO in
  Webtop applications i.e.
  LCANav
  .
  Customer Problem: When you tries to save
  automatically aniother Vault
  Process getting started.
  .
  OJH has anlayse this Issue and found that it is
  limitation on AIX.So As
  per OJH following restriction should be updated in
  the documentation.
  Here is the limitation description :
  .
  Operating System: AIX.
  The Orbix connection from an ENOVIA App Server
  launched by an Orbix
  Daemon A to a Vault Server fails if the Vault
  Server is running on the
  same machine and has not been launched by the
  same Orbix Daemon A.
  .
  By-pass:
  It is recommended to deploy the Vault Server on a
  dedicated machine
  which is not shared with the ENOVIA App Servers.
  If it is not possible to have a dedicated machine,
  then the same Orbix
  daemon has to be used for ENOVIA App Server
  and the Vault Server
  

Problem conclusion

• THIS MODIFICATION WILL BE INCLUDED IN THE DOCUMENTATION
  DELIVERED WITH I-PLM Collaborative Innovation VERSION V5R20
  Additional Closure Information:
  THIS MODIFICATION WILL BE INCLUDED IN THE
  DOCUMENTATION DELIVERED WITH ENOVIA
  VERSION 5 RELEASE 20 GA LEVEL.
  Additional Closure Information:
  Documentation Reference:
  .
  Installation and Deployment Guide;
  Getting Started
  Setting Up Vault Servers and Clients
  Installing the Vault Server Manually
  .
  Following Note has been documented Now;
  Note about Orbix On AIX
  -----------------------------
  The Orbix connection from an ENOVIA App Server
  launched by an Orbix Daemon A to a Vault Server
  fails if the Vault Server is running on the same
  machine and has not been launched by the same
  Orbix Daemon A.The recommended by-pass is to
  deploy the VaultServer on a dedicated machine
  which is not sharedwith the ENOVIA App Servers. If
  it is not possibleto have a dedicated machine, then
  the same Orbix daemon has to be used for ENOVIA
  App Serverand the Vault Server.It has also been
  added to the chapter"ActivatingSingle Sign-On",
  section "Enabling Wintop andWebtop Applications to
  Share the Same ENOVIA V5 Server".
  

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