HP Web-Based Enterprise Services 4.5 manual Windows Webes Issues

Overall WEBES Release Notes

1.6 WEBES Known Issues

notification.Type=SMTP LOG ISEE ACHS QSAP

5.Look for the following lines and replace them with the appropriate information, or add the lines if they do not exist: (case-sensitive)

If enabling QSAP/OSEM/CSG/PRS:

desta.QSAP=mymachine.company.com {the machine running OSEM or PRS} desta.QSAPport=2069

{the port number OSEM/PRS is listening on, 209 by default}

If enabling ACHS/SICL/DSNLink:

CA.ACHSProfile=/usr/opt/hp/svctools/specific/desta/config/profile.txt

{change this to the location appropriate for your operating system}

ccat.ACHSProfile=/usr/opt/hp/svctools/specific/desta/config/profile.txt

{change this to the location appropriate for your operating system}

CA.ACHSContact=me@mymachine.company.com

{change this to the appropriate email address}

ccat.ACHSContact=me@mymachine.company.com

{change this to the appropriate email address}

CA.ACHSRoute=SICL

{enter this verbatim}

6.Future notifications should be sent to the appropriate places. Restarting the Director or WCCProxy should not be necessary.

The problem is expected to be fixed in a future WEBES release.

1.6.2Windows WEBES Issues

1.6.2.1ClassNotFoundExceptions in Director Log

If you have previously removed WEBES, but kept your configuration information, then upon re-install choose a different combination of WEBES components (SEA and/or CCAT) or choose a different install directory for WEBES, the saved configuration data will not be valid and WEBES may fail. One possible symptom may be ClassNotFoundExceptions shown in the DESTA Director log file {installed directory}\svctools\specific\Webes\logs\director_err.txt. This problem will be fixed in a future release.

Rev. 9/8/06

Web-Based Enterprise Services Release Notes 1–15