Release Notes

Summary of enhancements, fixes, and open issues.
The following sections describe the enhancements, fixed issues, and known issues in Workload Automation Agent for SAP Version 12.0.00. You will also find instructions for installing the patch, as well as licensing information for third-party products used with the Workload Automation Agents.
Enhancements
This release contains no new enhancements.
Fixed Issues
This release includes the following fixed issue.
DE460796: SAP Agent support for Latest JCO 3.0.20 / 3.1.2
11.5 or previous release customers cannot use JCo libraries 3.0.20 / 3.1.2 or above. This is because the SAP Agent fails to login to SAP system with below error "Error: failed to connect to SAP. <com.sap.conn.jco.JCoException: (101) JCO_ERROR_CONFIGURATION: Configuration of destination ED1:001:EN:SUPERUSER is incorrect: Parameter message server host ('jco.client.mshost') is missing>" With the R12 release, customers can use the latest jco libraries. SAP Agent is certified with JCo libraries 3.0.20 / 3.1.2.
Known Issues
This release includes the following known issues.
Unable to Start 32-Bit Agent on Windows after Installing SAP Agent
(Valid on Windows) After you install the WA Agent for SAP on Windows, the following error occurs when you try to start the agent:
Error: failed to connect to SAP. <JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [C:\Program Files\CA\WA Agent R11.3\sapjcorfc.dll: Can't find dependent libraries]. ...
To correct this problem, add the msvcr71.dll and msvcp71.dll files to the agent installation directory. For information about obtaining these DLL files from Microsoft, go to the following site:
Unable to Start Agent on HP-UX after Installing SAP Agent
(Valid on HP-UX)
After you install the WA Agent for SAP on HP-UX, the following error occurs when you try to start the agent:
Error: failed to connect to SAP. <JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [/CA/WA_Agent_R11_3/libsapjcorfc.so: Cannot map text for library</CA/WA_Agent_R11_3/libsapjcorfc.so>: mmap(0x0, 0x3ee5d0, 0x5, 0x41, 94, 0x0) returns Permission denied.]. ...
To correct this problem, run the following command on your HP-UX system:
chmod 775 *rfc*.sl
Wrong State Reported for an SAP BW Process Chain
(Valid on UNIX and Windows) The agent can report an SAP Business Warehouse (BW) process chain as failed even though it is marked as completed by SAP. Under some conditions, SAP can mark a process chain as failed (red) and then continue processing it. The agent considers the reported process chain failure as the final state.
To correct this problem, apply the following SAP notes:
  • 1460640 - Correction: Synchronous run turns red during log refresh
  • 1396417 - Correction: Status "Red" if request does not exist yet
If the problem continues after applying the SAP notes, please investigate the problem with SAP before contacting Broadcom Support.
Download and Install the Patch
To download and install the patch, follow these steps:
Download the patch file from http://casupport.broadcom.com.
Copy it to a temporary location, and uncompress it. For information about the commands to run, refer to the following examples for UNIX and Windows. (In the commands below,
patch_ID
represents the number of the patch, which starts with either a T or RO.)
UNIX Example
mkdir /tmp/
patch_ID
cd /tmp/
patch_ID
uncompress <patch_ID.tar.Z | tar xvf -
Windows Example
mkdir C:\temp\
patch_ID
cd C:\temp\
patch_ID
CAZIPXP -u
patch_ID
.caz
Apply the patch by running one of the following commands, based on your platform, from the temporary directory you created in step 1. (In the commands below,
patch_ID
represents the number of the patch, which starts with either a T or RO.)
UNIX
PluginInstaller /tmp/
patch_ID
/sap.cfg <
agent directory
>
Windows
PluginInstaller C:\temp\
patch_ID
\sap.cfg <
agent directory
>