| This table lists the enhancements and fixes in interim fix version 7.0.0.4. |
| Enhancements |
| 1 | CR102956 | | Submitted Single RFC Program ID support.
|
| Symptom:SAP Adapter currently do not support Single Program ID feature.
|
| Resolution: Submitted Single RFC Program ID support has been added to the SAP Adapter(Applicable only for WPS customer) |
|
| Fixes |
| 1 | CR103046 | | BAPI Result Set: the schema will be generated incorrectly - SAPReturn will not be created for the added BAPI.
|
| Symptom:For BAPI Result Set ,the schema will be generated incorrectly - SAPReturn will not be created for the added BAPI.
. |
| Resolution: This is fixed now. |
|
| 2 | CR103048 | | Adapter EMD cannot load msvcrt.dll in the PATH on Windows2008 R2 Enterprise |
| Symptom:Adapter EMD cannot load msvcrt.dll in the PATH on Windows2008 R2 Enterprise. |
| Resolution: This is fixed now. |
|
| 3 | CR103058 | | SAP ALEPT Inbound/Outbound: Aother "sap" will be added to the BO name |
| Symptom:In Case of SAP ALEPT Inbound/Outbound. Aother "sap" will be added to the BO name when moving back and forth between screens in EMD. |
| Resolution: The problem is now fixed |
|
| 4 | CR103066 | JR37948 | The BAPI Result Set does not run the Detail-RFC although many entries from the Search-RFC are returned.
|
| Symptom: The BAPI Result Set does not run the Detail-RFC although many entries from the Search-RFC are returned. |
| Resolution: The problem is now fixed |
|
| 5 | CR100375 | JR34964 | Adapter is corrupting BCD Value in BAPI call when locale has a comma as decimal seperator |
| Symptom:Adapter is corrupting BCD Value in BAPI call when locale has a comma as decimal seperator |
| Resolution: This is fixed now. |
|
| 6 | CR103047
| | 2nd EMD run with the same RAR in same workspace will fail if missing msvcr71.dll |
| Symptom: 2nd EMD run with the same RAR in same workspace will fail if missing msvcr71.dll |
| Resolution: This is fixed now. |
|
| 7 | CR103006 | | QISS Iterative: The Configuration Properties panel is not correct |
| Symptom:QISS Iterative: The Configuration Properties panel is not correct |
| Resolution: This is fixed now. |
|
| 8 | CR103064 | JR37643 | ALE INBOUND WITH NAMESPACE SYNTAX IS THROWING EXCEPTIONS |
| Symptom: ALE INBOUND WITH NAMESPACE SYNTAX IS THROWING EXCEPTIONS |
| Resolution: This is fixed now. |
|
| 9 | CR103043 | | BAPI_BANK_GetList: Adapter will display one more bank info with non-set value" |
| Symptom: API_BANK_GetList: Adapter will display one more bank info with non-set value" |
| Resolution: This is fixed now. |
|
| 10 | CR103071 | | Optional changing parameters not listed in the Optional parameters list |
| Symptom:Optional changing parameters not listed in the Optional parameters list |
| Resolution: This is fixed now. |
|
| 11 | CR103065 | JR37652 | Unable to find the field - about bapi table fields built using field names. |
| Symptom:Unable to find the field - about bapi table fields built using field names. |
| Resolution: This is fixed now. |
|
| 12 | CR103063 | JR36753 | Event not found error logged in the websphere bi connector log: aep inbound. |
| Symptom:Event not found error logged in the websphere bi connector log: aep inbound. |
| Resolution: This is fixed now. |
|
| 13 | CR103049 | | Property "waitOnCommit" should not be applicable for for ALEPT/ALE outbound EMD. |
| Property "waitOnCommit" should not be applicable for for ALEPT/ALE outbound EMD |
| Resolution: This problem is now fixed |
|
| 14 | CR103050 | | SAPParseRecord problems when IDocs are discovered using SAP Field names (This is applicable on for RFC Program ID feature on WMB ) |
| Symptom:SAPParseRecord problems when IDocs are discovered using SAP Field names (This is applicable on for RFC Program ID feature on WMB ) |
| Resolution: This is fixed now. |
|
| 15 | CR103363 | JR39274 | ALE AUD Packet update |
| Symptom:ALE AUD Packet update dosent work correctly. |
| Resolution: This is fixed now. |
|
| 16 | CR103441 | JR39634 | Defects fixed for BAPI interface.
|
| Symptom:There are few defects fixed for the BAPI interface 1- MaxLength was incorrectly set for BAPI fields.Internal length was set instead of proper length. 2- Field Type was not set correctly for table types.WhiteSpace was padded in the type returned by adapter 3- Support was added for field types like: NUMC,DEC, TIMS, INT4 etc.
. |
| Resolution: This is fixed now. |
|
| 17 | CR103070 | JR38445 | User trace of the adapter does not state that the file SapBusinessObjectMetadata.xsd is missing in the deployed BAR file.
|
| Symptom:User trace of the adapter does not state that the file SapBusinessObjectMetadata.xsd is missing in the deployed BAR file.
. |
| Resolution: This is fixed now. |
|
| 18 | CR103040 | | QISS iterative development failure.
|
| Symptom:QISS iterative development failure.
. |
| Resolution: This is fixed now. |
|
| 19 | CR103067 | JR38117 | JCA SAP adapter v7 fails to load logon group members because sap 4.6 is missing a required structure in a lookup bapi.
|
| Symptom:JCA SAP adapter v7 fails to load logon group members because sap 4.6 is missing a required structure in a lookup bapi.
. |
| Resolution: This is fixed now. |
|
| 20 | CR103060 | JR33249 | The adapter does not perform the its best when there are one or more DATE fields in the return when BAPI interface is used.
|
| Symptom:The adapter does not perform the its best when there are one or more DATE fields in the return when BAPI interface is used.
. |
| Resolution: This is fixed now. |
|
| 21 | CR103053 | | When event is resubmitted from sap, its moved to the mqout,but not cleared from mq system queue.
|
| Symptom:When event is resubmitted from sap, its moved to the mqout,but not cleared from mq system queue.
. |
| Resolution: This is fixed now. |
|
| 22 | CR103059 | | BaseException: A resource exists with a different case: when discovering BAPIs |
| Symptom:BaseException: A resource exists with a different case: when discovering BAPIs |
| Resolution: The problem is now fixed. |
|
| 23 | CR 103529 | | SAPBusinessobjectMetadata.xsd for SAP Adapter to be changed to have CHANGING parameters. |
| Symptom:ASI business object definition for SAP Adapter to be changed to have CHANGING PARAM enumeration. |
| Resolution: The problem is now fixed |
|
| 24 | CR103304 | | Submitted sapparse record fails at runtime- EXPRESS field accessor not found.
|
| Symptom: Submitted sapparse record fails at runtime- EXPRESS field accessor not found. |
| Resolution: The problem is now fixed |
|
| 25 | CR103235 | | Inbound retry connection only used JCo retry mechanism |
| Symptom:Inbound retry connection only used JCo retry mechanism |
| Resolution: This is fixed now. |
|
| 26 | CR103044
| | Fetching metadataobject based on location ID for BOR does not work |
| Symptom: Fetching metadataobject based on location ID for BOR does not work |
| Resolution: This is fixed now. |
|
| 27 | CR103054 | | Sap adapter throws npe with ale inbound when exception occurs |
| Symptom: Sap adapter throws npe with ale inbound when exception occurs |
| Resolution: This is fixed now. |
|
| 28 | CR103056 | | JCA SAP Sync inbound bapi returns the union of input and output table rows if the output table rows were modified |
| Symptom:JCA SAP Sync inbound bapi returns the union of input and output table rows if the output table rows were modified |
| Resolution: This is fixed now. |
|
| 29 | CR103069 | JR38060 | Easy way to retrieve the client value e.g. through connection
factory without having to hardcode it. |
| Symptom: Easy way to retrieve the client value e.g. through connection
factory without having to hardcode it. |
| Resolution: This is fixed now. |
|
| 30 | CR103062 | | IDoc field Value are getting trimmed. |
| Symptom:IDoc field Value are getting trimmed. |
| Resolution: This is fixed now. |
|
| 31 | CR103041 | | BAPI: Integer field inside Structure is not created in SAP |
| Symptom:BAPI: Integer field inside Structure is not created in SAP |
| Resolution: This is fixed now. |
|
| 32 | CR103057 | | Deploy fails after using mqsicreateconfig/ adding setter/getter for rfctracePath |
| Symptom:Deploy fails after using mqsicreateconfig/ adding setter/getter for rfctracePath. |
| Resolution: This is fixed now. |
|
| 33 | CR103051 | | QISS editBO error : editBO is erroneous when we select 2 or more BOs in QISS |
| Symptom:QISS editBO error : editBO is erroneous when we select 2 or more BOs in QISS |
| Resolution: This problem is now fixed. |
|
| 34 | CR103436 | | Changing exception.printstacktrace to throw exception to stop adapter processing further. |
| Symptom:Changing exception.printstacktrace to throw exception to stop adapter processing further. |
| Resolution: This is fixed now. |
|
| 35 | CR 103162 | JR39129 | Duplicate messages are created in the event table by the Adapter due to unexpected database outage. |
| Symptom:During AEP Inbound operation, after several unplanned SAP outages during event processing duplicate messages can be observed. This is due to the fact that the event is delivered but the overall transaction is marked failure and no rollback is called by the transaction manager. |
| Resolution: If the event is already delivered to the downstream components but the overall transaction is marked failure due to issues in downstream component, the event is deleted if no rollback is issued. |
|
| 36 | | JR39474 | SAP ADAPTER V7 SELECTIVELY SEND FEW SEGMENTS IN THE IDOC TO SAP. |
| Symptom:The JCA SAP Adapter on V7 was failing if the segmenents that are not mandatory, having maxoccurs =1 , are not sent in the input xml during outbound. |
| Resolution: This is fixed now. |
|
| 37 | CR 103304 | JR38885 | Adapter throws exception while getAccessor("EXPRESS") is called |
| Symptom: - Adapter thows exception while fetching value for accessor EXPRESS.
|
| Resolution:Adapter was incorrectly trying to fetch the value for EXPRESS, correct field is EXPRSS , This is now fixed. |
|
| 38 | | JR37643 | ALE INBOUND WITH NAMESPACE SYNTAX IS THROWING EXCEPTIONS. |
| Symptom: - ALE inbound with namespace syntax "//"is throwing exception using extension IDOCs, where the extended IDOC is having a linked IDOC who's name includes namespace in it..
|
| Resolution: This is fixed now. |
|
| 39 | | JR38640 | ADAPTER THROWS NULLPOINTER EXCEPTION IF NON-MANDATORY LEVEL 1 IDOC SEGMENTS ARE OMITTED WHEN SENDING IDOC TO SAP. |
| Symptom: - ADAPTER THROWS NULLPOINTER EXCEPTION IF NON-MANDATORY LEVEL 1 IDOC SEGMENTS ARE OMITTED WHEN SENDING IDOC TO SAP.
|
| Resolution: This is fixed now. |
|
| 40 | | JR38223 | ADAPTER UNABLE TO PROCESS IDOCS VIA QRFC WHEN THE IDOC CONTAINS UNRELEASED SEGMENTS
|
| Symptom: - Adapter unable to process IDocs via qRFC when the IDoc contains unreleased segments.
|
| Resolution: This is fixed now. |
|
| 41 | | JR38356 | SAP INBOUND MISLEADING ERROR MESSAGE: E SAPTRFCSERVERDATABINDING GETDATAOBJECT CWYBS0499E:
|
| Symptom: - When using the SAP Adapter as inbound adapter, receiving following misleading error message:
SAPRA001 E SAPtRFCServerDataBinding getDataObject CWYBS0499E: An invalid key was encountered while the adapter was using Resource Bundle com.ibm.j2ca.sap.LogMessages with Locale en_US. The key is either null or an empty string.
Though it does not have any functional impact.
|
| Resolution: This is fixed now. |
|
| 42 | | JR38359 | SAP ADAPTER XSTRING HANDLING THROWS CLASSCASTEXCEPTION.
|
| Symptom: If XSTRING is defined field type of the business object SAP Adapter throws an exception at runtime. ABAP data type XSTRING cannot be parsed correctly from SAP adapter at runtime.
|
| Resolution: This is fixed now. |
|
| 43 | CR102456 | | Submitted 2nd EMD run with the same RAR in same workspace will fail if missing msvcr71.dll |
| Symptom:If msvcr71.dll is missing in the PATH then 2nd EMD run with the same RAR in the same workspace fails with the exception Array Out of Bounds |
| Resolution: This is fixed now. |
|
| 44 | | JR37644 | JCA SAP SYNC INBOUND BAPI RETURNS THE UNION OF INPUT AND OUTPUT
TABLE ROWS IF THE OUTPUT TABLE ROWS WERE MODIFIED.
|
| Symptom:JCA SAP SYNC INBOUND BAPI RETURNS THE UNION OF INPUT AND OUTPUT
TABLE ROWS IF THE OUTPUT TABLE ROWS WERE MODIFIED.
. |
| Resolution: This is fixed now. |
|
| 45 | CR101438 | JR36977 | Adapter throws SelectorException during migration from WBIA to JCA |
| Symptom:WBI adapter did not contain the prefix sap_ which is being set by default while creating business object definitions using SAPODA. JCA adapter expecting sap_ as prefix in BO definition throws error. |
| Resolution: New Parameter "Default BO Prefix" is introduced in Activation Spec at runtime. |
|
| 46 | CR101361 | JR36754 | DETAILED LOGGING BEING LOGGED IN SYSTEMOUT EVEN WHEN NO J2CA TRACE IS SET FOR B |
| Symptom: Even when the trace is not enabled i.e, with just *=info,detailed logging is logged into the systemout log |
| Resolution: The problem is now fixed |
|
| 47 | CR77600 | JR33249 | The adapter doesnÓ´ perform the best when there are one ore more DATE fields in the return when BAPI interface is used
|
| Symptom: When there are one or more DATE fields in the return BAPI, the adapter needs to be tuned for better performance |
| Resolution: The problem is now fixed |
|
| 48 | CR101858 | JR37537 | Connections to SAP are not closed when BAPI calls fail (only for concurrent requests) |
| Symptom:Connections to SAP are not closed when BAPI calls fail |
| Resolution: This is fixed now. |
|
| 49 | CR101872
| | Concurrent requests to SAP Adpater fail with JCO_ERROR_CONCURRENT_CALL |
| Symptom: Concurrent requests to SAP Adpater fail with JCO_ERROR_CONCURRENT_CALL |
| Resolution: This is fixed now. |
|
| 50 | CR101455 | JR37070 | Message flow does not stop on HP-UX |
| Symptom:Message flow does not stop on HP-UX |
| Resolution: This is fixed now. |
|
| 51 | CR101819 | JR37487 | WHEN EVENT IS RESUBMITTED FROM SAP, ITS MOVED TO THE MQOUT,BUT NOT CLEARED FROM MQ SYSTEM QUEUE |
| Symptom:WHEN A FAILED TO DELIVER EVENT IS RESUBMITTED FROM SAP, ITS MOVED TO THE MQOUT,BUT NOT CLEARED FROM MQ SYSTEM QUEUE |
| Resolution: This is fixed now. |
|
| 52 | CR101828 | JR37493 | ERRORS NOT WRITTEN TO SYSLOG |
| Symptom: DETAILED ERRORS NOT WRITTEN TO SYSLOG |
| Resolution: This is fixed now. |
|
| 53 | CR101825 | JR37494 | SAP ADAPTER THROWS NPE WITH ALEIN WHEN EXCEPTION OCCURS |
| Symptom:SAP ADAPTER THROWS NPE WITH ALEIN WHEN EXCEPTION OCCURS THUS MASKING THE ORIGINAL EXCEPTION |
| Resolution: This is fixed now. |
|
| 54 | | JR37349 | IDOC DATARECORD VALUES ARE GETTING TRUNCATED ON NON-UNICODE SYSTEMS. |
| Symptom:IDOC DATARECORD VALUES ARE GETTING TRUNCATED ON NON-UNICODE SYSTEMS. |
| Resolution: This is fixed now. |
|
| 55 | | JR37273 | SAP OUTBOUND ALE/BAPI CONNECTION LOST AND TRANSACTION GOES STATELESS MODE. |
| Symptom:SAP OUTBOUND ALE/BAPI CONNECTION LOST AND TRANSACTION GOES STATELESS MODE. |
| Resolution: This is fixed now. |
|
| 56 | | JR36874 | Adapter throws IllegalStateException if server doesnt support transaction delivery. |
| Symptom:IllegalStateException is thrown as AFTER_DELIVERY was called but message delivery didnt started with BEGAN_DELIVERY |
| Resolution: This problem is now fixed, BEFORE_DELIVERY and AFTER_DELIVERY is paired. |
|
| 57 | CR101913 | | The JCo Reset doesnt work when the request fail with an exception |
| Symptom:Connections to SAP are not reset if JCoReset Connection is checked and rollback happens. |
| Resolution: This is fixed now. |
|
| 58 | CR101178 | | No address data returned with an application containing 3 BAPIs or more |
| Symptom:No address data returned with an application containing 3 BAPIs or more |
| Resolution: This is fixed now. |
|
| 59 | CR 101456 | | Detecting illegal XML characters in SDO DESPI of Adapters. |
| Symptom: We are facing an issue in which a runtime exception is being thrown when the BO generated by the Adapter is being serialized down the line to be transferred over the wire during the BOXML serialization because of invalid xml characters in the BO. |
| Resolution: Provide options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently we have 4 choices: (a) Do not validate BO content for illegal XML characters (default); (b) Throw exceptions if BO content contains illegal XML charaters;(c) Discard illegal XML characters in BO content and log; (d) Escape sequence illegal XML characters and log. |
|
| 60 | CR 102613 | JR38019 | Enable JCA timer capability for inbound polling. |
| Symptom: Adapter uses a polling thread in the runtime, which will poll as per the pollperiod. The polling thread will be only submitted once and always being in the runtime environment. When there are no events for a longer duration, the polling thread will be hung and throws a warning message from the JCA container. |
| Resolution: Use JCA timer to schedule the polling thread, so the polling thread would be submitted according to the JCA scheduler, which will solve the thread hang issue. |
|
| 61 | CR 103432 | | SAP Adapter throws ClassCastException when reading annotation in Synchronous BAPI Inbound with Lazy BO parsing mode. |
| Symptom: SAP Adapter throws ClassCastException when reading annotation in Synchronous BAPI Inbound with Lazy BO parsing mode, when the Adapter RAR is deployed at Node level. |
| Resolution: During Node level deployment, the default BO parsing for runtime is Eager parsing. Hence, properties generated in Lazy parsing mode will encounter issue while reading annotations. The issue is resolved by reading the annotations accordingly. |
|
| 62 | | JR39773 | Inbound polling fails on WebSphere Message Broker (WMB) throwing java.lang.UnsupportedOperationException. |
| Symptom: Adapter fails during startup of the Inbound polling on WebSphere Message Broker. Adapter throws java.lang.UnsupportedOperationException will be thrown during the call to BootStrapContext.createTimer(). |
| Resolution: WMB currently does not return a timer in createTimer() call. The issue has been resolved by handling the exception at the adapter end and creating a java.util.Timer instance to handle the inbound polling. |
|
| This table lists the enhancements and fixes in interim fix version 7.0.0.3. |
| Enhancements |
| There are no enhancements in this interim fix. |
| Fixes |
| 1 | CR 100455 | JR35275 | JCA SAP ADAPTER GENERATED BO / MESSAGE SET SCHEMA FAILS VALIDATION |
| Symptom: The xsd schema generated by the JCA SAP ESD marks some control fields as required. However, the adapter treats these fields as optional |
| Resolution: This problem is now fixed. |
|
| 2 | CR 101273 | JR36038 | JCONNECTIONS STILL REMAIN ACTIVE EVEN AFTER THE ADAPTER IS STOPPED |
| Symptom: Even when the message flow is stopped i.e, adapter is stopped , connections are still active . when tested using SM59. |
| Resolution: This problem is now fixed. |
|
| 3 | CR 101226 | JR36606 | BASEEXCEPTION WHEN TRYING TO CREATE SAP OUTBOUND: ELEMENT DO NOT MATCH QNAME |
| Symptom: When client tries to create a SAP-Outbound-Adapter via WMB Toolkit Adapter v7 Wizard they get error message: com.ibm.adapter.framework.BaseException |
| Resolution: This problem is now fixed. |
|
| 4 | CR 101205 | | SAP ADAPTER V7 PROBLEMS CONNECTING TO NON-UNICODE SYSTEMS WITH LOWER CASE PASSWD |
| Symptom: SAP Adapter v7 fails connecting to non-unicode SAP Systems when the password is entered in lower case. |
| Resolution: This problem is now fixed. |
|
| 5 | CR 101271 | JR34424 | BAPI INBOUND WITH NAMESPACE SYNTAX "/<ABC>/<XYZ>" IS THROWING EXCEPTION |
| Symptom: When using a registered namespace on the SAP system for BAPI artifacts, the SAP adapter is throwing exceptions such as : "Business Object definition for 'SapStfcWriteToTopicWrapper' in namespace ...not found" |
| Resolution: This problem is now fixed. |
|
| 6 | CR 101049 | JR36123 | SAP JCA ADAPTER 7.0.0, QISS MODULE: ONLY FIRST CHILD TABLE GETS RETRIEVED |
| Symptom: TSAP Adapter Outbound QISS interface: only the first of several child tables is retrieved. The other child table remain null. |
| Resolution: This problem is now fixed. |
|
| 7 | CR 100905 | JR36095 | USING ALE PASSTHROUGH FOR OUTBOUND MESSAGES GOING TO SAP, SAP THROWS AN ERROR. |
| Symptom: Using ALE Passthrough for outbound messages going to SAP, not all the fields are set SAP throws an error and the SAP request node gets the error about those missing values |
| Resolution: This problem is now fixed. |
|
| 8 | CR 101046 | JR36223 | JCA SAP UNABLE TO COMPLETE ITERATIVE EMD WHEN RFC TRACE PATH IS SET |
| Symptom: The client is using the JCA SAP Adapter v7 and is not able to extend or add to their existing EIS artifacts using the WebSphere Adapter's 'Iterative Development' feature. |
| Resolution: This problem is now fixed. |
|
| 9 | CR 101272 | JR35371 | CXIGNORE SET FOR ALL FIELDS COMING IN FROM AEP INBOUND. |
| Symptom: IDocs sent from SAP EIS via AEP custom handler contain only contain CxIgnore values. |
| Resolution: This problem is now fixed. |
|
| 10 | CR 101270 | | BOR DISCOVERY FOR ALL FILTER PATTERNS NOT CONTAINING ASTERIK DOES NOT WORK |
| Symptom: BOR discovery for all filter patterns not containing asterik does not work |
| Resolution: This problem is now fixed. |
|
| 11 | CR 101398 | | BAPI ZPM_TEST_RFC OUTBOUND WILL GENERAL FFDC |
| Symptom: In SAP Adapter, BAPI ZPM_TEST_RFC outbound is generating FFDC: Field NUMBER not a member of BAPIRETURN |
| Resolution: This problem is now fixed. |
|
| 12 | CR 101394 | | ARRAYINDEXOUTOFBOUND ISSUE ON ITERATIVE DISCOVERY FOR BOR |
| Symptom: Iterative discovery does not work for BOR. ARRAYINDEXOUTOFBOUND exception. |
| Resolution: This problem is now fixed. |
|
| 13 | CR 101269 | | ITERATIVE DISCOVERY DOES NOT WORK FOR BOR |
| Symptom: Iterative discovery does not work for BOR |
| Resolution: This problem is now fixed. |
|
| 14 | CR 101395 | | SET "*CROSS" AS BOR FILTER BAPI WHICH BEGIN WITH CROSS SHOULD BE LISTED. |
| Symptom: Set "*Cross" as BOR filter, BAPI which begin with Cross, such as "Cross-System command", will be listed. |
| Resolution: This problem is now fixed. |
|
| 15 | CR 101397 | | THE DESCRIPTION IN "FIND OBJECTS IN ENTERPRISE SYSTEM" SHOULD BE DIVIDED |
| Symptom: The description of BAPI in "Find Objects in Enterprise System" should be divided by "/" or something else |
| Resolution: This problem is now fixed. |
|
| 16 | CR 101386 | | SAP ADAPTER TO PROVIDE AN OPTIONAL FEATURE FOR PRESERVING LEADING SPACES IN THE IDOC FIELDS. |
| Symptom: SAP Adapter to provide an optional feature for preserving leading spaces in the IDoc fields. |
| Resolution: This problem is now fixed. |
|
| 17 | CR 101037 | | INFORMATION DISPLAYED IN PROGRESS BAR SHOULD BE TRANSLATED INTO OS LOCAL USED |
| Symptom: In EMD, Panel's progressing bar information is not translated accordingly |
| Resolution: This problem is now fixed. |
|
| 18 | CR 101445 | | NO CBE 'DELIVERY.ENTRY' EVENT FOR SAP INBOUND EVENT DELIVERY |
| Symptom: No CBE 'delivery.entry' event for SAP Inbound event delivery |
| Resolution: This problem is now fixed. |
|
| 19 | CR 101387 | | SAP ADAPTER CBES MUST HAVE CORRELATION IN ORDER TO TRACK THE EVENTS IN A FLOW |
| Symptom: SAP Adapter CBEs must have correlation in order to track the events in a flow. |
| Resolution: This problem is now fixed. |
|
| 20 | CR 101013 | | DUMMYKEY BEHAVIOR IS DIFFERENT FROM BASIC IDOC TO EXTENSION IDOC |
| Symptom: Dummykey behavior is different from basic IDoc to extension IDoc |
| Resolution: This problem is now fixed. |
|
| 21 | CR 101018 | | EMD FOR MORE THAN ONE IDOCS FOR AEP INTERFACE, GENERATED METHODBINDING IS INCORRECT |
| Symptom: Selecting one basic IDoc and one extension IDoc or two basic IDocs to generate artifacts, the generated methodbindings are not the expected ones. |
| Resolution: This problem is now fixed. |
|
| 22 | CR 101020 | | METHOD NAME ATTRIBUTE OF GENERATED BO FOR AEP INTERFACE IS WRONG |
| Symptom: For multi-IDocs, in top level BO the generated methodname attribute belonged to operation element does not reflect the value, which fills during EMD process in Specify Composite Property panel |
| Resolution: This problem is now fixed. |
|
| 23 | CR 101274 | | CANT DEPLOY THE SAPINPUT NOTE IF NUMBER OF LISTENERS IS SET TO 1 |
| Symptom: When load balancing is enabled - cant deploy the sapinput note if number of listeners is set to 1 |
| Resolution: This problem is now fixed. |
|
| 24 | CR 101421 | JR36754 | DETAILED LOGGING BEING LOGGED IN SYSTEMOUT EVEN WHEN NO J2CA TRACE IS SET TO INFO |
| Symptom: Even when the trace is not enabled i.e, with just *=info ,detailed logging is logged into the systemout log |
| Resolution: This problem is now fixed. |
|
| 25 | CR 101058 | | JCO_ERROR_SESSION_REF_NOT_VALID ERROR HAPPENS WHEN TESTING ALE INBOUND |
| Symptom: JCO_ERROR_SESSION_REF_NOT_VALID error happens when testing ALE inbound |
| Resolution: This problem is now fixed. |
|
| 26 | CR 101423 | | EVENT NOT FOUND ERROR LOGGED IN THE WEBSPHERE BI CONNECTOR LOGS -AEP MODULE |
| Symptom: Event not found error logged in the websphere bi connector logs -aep module |
| Resolution: This problem is now fixed. |
|
| 27 | CR 101422 | JR33249 | PERFORMANCE FIXES ALONG WITH THE STRINGOUTOFBOUNDS EXCEPTION FIX. |
| Symptom: Performance fixes along with the stringoutofbounds exception fix. |
| Resolution: This problem is now fixed. |
|
| 28 | CR 101275 | JR35842 | EMD WIZARD IN WMB: "SENT IDOC AS ONE BO: TRUE" CANNOT BE CHANGED |
| Symptom: With WMB Toolkit 6.1 and SAP Adapter 6.1, the ESD Wizard shows the option to receive an individual message per IDoc sent but it cannot be changed. |
| Resolution: This problem is now fixed. |
|
| 29 | CR 101014 | | AEP INBOUND FAILS WITH "UNABLE TO CREATE DEFINITIONS NULL" SOMETIMES |
| Symptom: With some certain steps, AEP inbound EMD fails with a "java.lang.RuntimeException: Unable to create definitions null" error. |
| Resolution: This problem is now fixed. |
|
| 30 | CR 101427 | | THE FINISH BUTTON IN THE LAST PANEL OF ALEPT ITERATIVE DOES NOT WORK |
| Symptom: The finish button in the last panel of ALEPT iterative does not work correctly |
| Resolution: This problem is now fixed. |
|
| 31 | CR 101263 | | SetValueofString() METHOD IS NOT SUPPORTED FOR FOLDER AND FILE PROPERTIES DURING ITERATIVE DISCOVERY |
| Symptom: If the first run of the discovery wizard contains a File, Folder or Schema type property, subsequent iterative discovery wizard runs fail to launch and an error message is displayed to the user. |
| Resolution: This problem is now fixed. |
|
| 32 | | JR39166 | SAP ADAPTER PROPERTY "RESET THE JCO CLIENT AFTER CLOSING THE CONNECTION HANDLE" DO NOT PROPERLY REFRESHING JCO REPOSITORY.
|
| Symptom: SAP Adapter property "RESET THE JCO CLIENT AFTER CLOSING THE CONNECTION HANDLE" do not refresh the JCO REPOSITORY on connection reset if parameters are changed on the SAP side. .
|
| Resolution: This is fixed now. |
|
| 33 | CR102692 | | EMD error while selecting Generic IDOC feature using ALE PassThrough Inbound module. |
| Symptom: EMD error while selecting Generic IDOC feature using ALE PassThrough Inbound module.
|
| Resolution: This is fixed now. |
|
| 34 | | JR38223 | ADAPTER UNABLE TO PROCESS IDOCS VIA QRFC WHEN THE IDOC CONTAINS UNRELEASED SEGMENTS |
| Symptom: Adapter unable to process IDocs via qRFC when the IDoc contains unreleased segments
|
| Resolution: This is fixed now. |
|
| 35 | | JR38117 | JCA SAP V7 FAILS TO LOAD LOGON GROUP MEMBERS BECAUSE SAP 4.6 IS MISSING A REQUIRED STRUCTURE IN A LOOKUP BAPI
|
| Symptom: The JCA SAP Adapter on V7 is unable to make use of inbound
loadbalancing via the Logon group. The adapter fails as it
performs a lookup to query all active SAP Application Servers
that are members of the target Logon Group. The failure is
caused by SAP 4.7 and its BAPI, 'TH_SERVER_LIST' missing a
structure for 'LIST_IPV6'.
|
| Resolution: The JCA SAP Adapter code is now fixed so that even on SAP 4.6 it can perform the inbound load balancing. |
|
| 36 | CR76307 | | Flat file IDoc support for ALE passthrough inbound.
|
| Symptom: SAP adapter can send IDoc to endpoint in inline format(ie each Control record 524 bytes and Data record 1063 bytes) only.
|
| Resolution: Support for flat file IDoc is provided as an enhancemnent in EMD.Option provided in EMD to select flat file IDoc.If a user select flat file IDoc in EMD , field appears to select IDoc version and enter the delimiter value.IDoc Version can be left blank if unreleased segment also needs to be discoverd. If IDoc version selected in EMD is less than the version of IDoc sent from SAP,extraneous data if present in segments would be truncated automatically. |
|
| 37 | CR102204 | | SAP Adapter throws ClassCastException with ALEPassthrough Inbound when exception occurs.
|
| Symptom: SAP Adapter throws ClassCastException with ALEPassthrough Inbound when exception occurs.
|
| Resolution: This is fixed now. |
|
| 38 | | JR37644 | JCA SAP SYNC INBOUND BAPI RETURNS THE UNION OF INPUT AND OUTPUT
TABLE ROWS IF THE OUTPUT TABLE ROWS WERE MODIFIED.
|
| Symptom:JCA SAP SYNC INBOUND BAPI RETURNS THE UNION OF INPUT AND OUTPUT
TABLE ROWS IF THE OUTPUT TABLE ROWS WERE MODIFIED.
. |
| Resolution: This is fixed now. |
|
| 39 | CR101913 | | The JCo Reset doesnt work when the request fail with an exception |
| Symptom:Connections to SAP are not reset if JCoReset Connection is checked and rollback happens. |
| Resolution: This is fixed now. |
|
| 40 | CR101438 | JR36977 | Adapter throws SelectorException during migration from WBIA to JCA |
| Symptom:WBI adapter did not contain the prefix sap_ which is being set by default while creating business object definitions using SAPODA. JCA adapter expecting sap_ as prefix in BO definition throws error. |
| Resolution: New Parameter "Default BO Prefix" is introduced in Activation Spec at runtime. |
|
| 41 | CR101361 | JR36754 | DETAILED LOGGING BEING LOGGED IN SYSTEMOUT EVEN WHEN NO J2CA TRACE IS SET FOR B |
| Symptom: Even when the trace is not enabled i.e, with just *=info,detailed logging is logged into the systemout log |
| Resolution: The problem is now fixed |
|
| 42 | CR77600 | JR33249 | The adapter doesnÓ´ perform the best when there are one ore more DATE fields in the return when BAPI interface is used
|
| Symptom: When there are one or more DATE fields in the return BAPI, the adapter needs to be tuned for better performance |
| Resolution: The problem is now fixed |
|
| 43 | CR101858 | JR37537 | Connections to SAP are not closed when BAPI calls fail (only for concurrent requests) |
| Symptom:Connections to SAP are not closed when BAPI calls fail |
| Resolution: This is fixed now. |
|
| 44 | CR101872
| | Concurrent requests to SAP Adpater fail with JCO_ERROR_CONCURRENT_CALL |
| Symptom: Concurrent requests to SAP Adpater fail with JCO_ERROR_CONCURRENT_CALL |
| Resolution: This is fixed now. |
|
| 45 | CR101455 | JR37070 | Message flow does not stop on HP-UX |
| Symptom:Message flow does not stop on HP-UX |
| Resolution: This is fixed now. |
|
| 46 | CR101819 | JR37487 | WHEN EVENT IS RESUBMITTED FROM SAP, ITS MOVED TO THE MQOUT,BUT NOT CLEARED FROM MQ SYSTEM QUEUE |
| Symptom:WHEN A FAILED TO DELIVER EVENT IS RESUBMITTED FROM SAP, ITS MOVED TO THE MQOUT,BUT NOT CLEARED FROM MQ SYSTEM QUEUE |
| Resolution: This is fixed now. |
|
| 47 | CR101828 | JR37493 | ERRORS NOT WRITTEN TO SYSLOG |
| Symptom: DETAILED ERRORS NOT WRITTEN TO SYSLOG |
| Resolution: This is fixed now. |
|
| 48 | CR101825 | JR37494 | SAP ADAPTER THROWS NPE WITH ALEIN WHEN EXCEPTION OCCURS |
| Symptom:SAP ADAPTER THROWS NPE WITH ALEIN WHEN EXCEPTION OCCURS THUS MASKING THE ORIGINAL EXCEPTION |
| Resolution: This is fixed now. |
|
| 49 | | JR37349 | IDOC DATARECORD VALUES ARE GETTING TRUNCATED ON NON-UNICODE SYSTEMS. |
| Symptom:IDOC DATARECORD VALUES ARE GETTING TRUNCATED ON NON-UNICODE SYSTEMS. |
| Resolution: This is fixed now. |
|
| 50 | | JR37273 | SAP OUTBOUND ALE/BAPI CONNECTION LOST AND TRANSACTION GOES STATELESS MODE. |
| Symptom:SAP OUTBOUND ALE/BAPI CONNECTION LOST AND TRANSACTION GOES STATELESS MODE. |
| Resolution: This is fixed now. |
|
| 51 | | JR36874 | Adapter throws IllegalStateException if server doesnt support transaction delivery. |
| Symptom:IllegalStateException is thrown as AFTER_DELIVERY was called but message delivery didnt started with BEGAN_DELIVERY |
| Resolution: This problem is now fixed, BEFORE_DELIVERY and AFTER_DELIVERY is paired. |
|
| 52 | CR101394 | | Iterative discovery for BOR fails with Array index out of range |
| Symptom:Iterative discovery for BOR fails with Array index out of range error |
| Resolution: This problem is now fixed. |
|
| 53 | CR101269 | | Iterative discovery does not work for BOR |
| Symptom: Iterative discovery does not work for BOR |
| Resolution: This problem is now fixed. |
|
| 54 | CR101270 | | BOR discovery for all filter patterns not containing asterik does not work |
| Symptom:BOR discovery for all filter patterns not containing asterik does not work |
| Resolution: This problem is now fixed. |
|
| 55 | | JR36606 | SAP Adapter v7 fails for BAPI Inbound/Outbound in EMD flow |
| Symptom: SAP Adapter v7 fails for BAPI Inbound/Outbound in EMD flow. Element or Attribute do not match QNAme production QNAme::=(NCName':')?NCNAme. |
| Resolution: This problem is now fixed. |
|
| 56 | CR101205 | | SAP Adapter v7 problems connecting to non-unicode systems with lower case passwd |
| Symptom: SAP Adapter v7 problems connecting to non-unicode systems with lower case passwd |
| Resolution: This problem is now fixed. |
|
| 57 | | JR36095 | USING ALE PASSTHROUGH FOR OUTBOUND MESSAGES GOING TO SAP,SAP THROWS AN ERROR. |
| Symptom: Using ALE Passthrough for outbound messages going to SAP, not all the fields are set SAP throws an error and the SAP request node gets the error about those missing values. 'com.ibm.j2ca.sap.exception.SapAleOutboundException: Value ' ' cannot be converted to NUM type at field PSGNUM' (CHARACTER)" |
| Resolution: This problem is now fixed. |
|
| 58 | | JR36223 | Iterative Discovery Wizard throws errors when properties of type File, Folder or Schema type are used. |
| Symptom: If the first run of the discovery wizard contained a File, Folder or Schema type property, subsequent iterative discovery wizard runs fail to lauch and an error message is displayed to the user. |
| Resolution: Fixed by overriding the method setValueAsString for those complex type properties in the Adapter Foundation classes. This is a tooling only fix and does not apply to the runtime. A fresh run of the discovery wizard is required to get the Iterative discovery working. |
|
| 59 | | JR34424 | BAPI INBOUND WITH NAMESPACE SYNTAX "/ABC/XYZ" IS THROWING EXCEPTIONS |
| Symptom: BAPI INBOUND WITH NAMESPACE SYNTAX "/ABC/XYZ" IS THROWING EXCEPTIONS. com.ibm.websphere.sca.ServiceRuntimeException: commonj.connector.runtime.SelectorException: commonj.connector.runtime.SelectorException: For the RFC TypeSapCwldOutboundRequestMqWrapperOperation is not found using the application-specific information: commonj.connector.runtime.SelectorException: Business object definition for 'SapAAinUiBpGetWrapper' in namespace 'http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/AIN/UI_BP_GET/sapaainuibpgetwrapper' not found.. The adapter has not been configured for the BAPI /AIN/UI_BP_GET |
| Resolution: This problem is now fixed. |
|
| 60 | | JR36123 | SAP JCA ADAPTER 7.0.0, QISS MODULE: ONLY FIRST CHILD TABLE GETS RETRIEVED |
| Symptom: SAP JCA ADAPTER 7.0.0, QISS MODULE: ONLY FIRST CHILD TABLE GETS RETRIEVED |
| Resolution: This problem is now fixed. |
|
| This table lists the enhancements and fixes in interim fix version 7.0.0.1 |
| Enhancements |
| There are no enhancements in this interim fix. |
| Fixes |
| 1 | CR100495 | | Adapter does not poll events from Non Unicode SAP systems during AEP processing |
| Symptom: A java.lang.NullPointerException is thrown when an application is configured for AEP Inbound processing with Non Unicode SAP Systems |
| Resolution: This problem is now fixed. |
|
| 2 | CR100471 | | AEP Interface: Event data being returned as blank, though the data is present |
| Symptom: With the AEP interface: Event data being retuned as blank eventhough there is data available for the fields. |
| Resolution: This problem is now fixed. |
|
| 3 | CR100528 | | BAPI Work Unit doesnt update data successfully when JCO Reset is enabled |
| Symptom: BAPI Work Unit doesnt update data successfully when JCO Reset is enabled |
| Resolution: This problem is now fixed. |
|
| 4 | CR100470 | | No value fields are being set to "CxIgnore" during AEP Inbound |
| Symptom: No value fields are being set to "CxIgnore" during AEP Inbound |
| Resolution: This problem is now fixed. |
|
| 5 | CR100472 | | AEP: Delete archived events not working |
| Symptom: AEP - Delete archived events not working |
| Resolution: This problem is now fixed. |
|
| 6 | CR100473 | | AEP: Delete queue events not working |
| Symptom: AEP - Delete queue events not working |
| Resolution: This problem is now fixed. |
|
| 7 | CR100474 | | AEP: Log updates not working |
| Symptom: AEP - Log updates not working |
| Resolution: This problem is now fixed. |
|
| 8 | CR100552 | | Error appear when invoke BAPI 2 times when JCO Reset is enabled |
| Symptom: Error appear when invoke BAPI update 2 times when JCO Reset is enabled on WMB7 |
| Resolution: This problem is now fixed. |
|
| 9 | CR100456 | | Inbound Processing with extended IDocs doesn't work |
| Symptom: Inbound Processing with extended IDocs doesn't work |
| Resolution: This problem is now fixed. |
|
| 10 | CR100575 | | ERROR MESSAGE WHEN BUILDING A NEW SAP REQUEST ADAPTER CONNECTION |
| Symptom: ERROR MESSAGE WHEN BUILDING A NEW SAP REQUEST ADAPTER CONNECTION. (Changing Parameters) |
| Resolution: This problem is now fixed. |
|
| 11 | CR100576 | | INCORRECT XML CREATED FOR THE UNPOPULATED FIELDS. |
| Symptom: Empty tags are included in the message if the fields are followed by other populated fields, but all unpopulated fields at the end of a segment do not have empty tags outputted xml. |
| Resolution: This problem is now fixed. |
|
| 12 | CR100578 | | BCD Value corrupt during a BAPI call when the underlying locale uses COMMA (,) for a decimal DOT (.) |
| Symptom: BCD Value corrupt during a BAPI call when the underlying locale uses COMMA (,) for a decimal DOT (.) |
| Resolution: This problem is now fixed. |
|
| 13 | CR100579 | | SAP Input node doesnt work correctly under SAP Load Balancing setup |
| Symptom: SAP Input node doesnt work correctly under SAP Load Balancing setup |
| Resolution: This problem is now fixed. |
|
| 14 | CR100110 | | when RuntimeException thrown in Session Bean, two ALEAUD generated |
| Symptom: when RuntimeException thrown in Session Bean, two ALEAUD generated |
| Resolution: This problem is now fixed. |
|
| 15 | CR100547 | | IDoc Data from the second/child segments is not processed - AEP Oubound |
| Symptom: IDoc Data from the second/child segments is not processed - AEP Oubound |
| Resolution: This problem is now fixed. |
|
| 16 | CR100634 | | Error handling for malformed IDocs |
| Symptom: When you send an IDoc that is not properly constructed from WMB to SAP using SAP Adapter, the SAP Adapter does NOT pass it over to SAP at all (which is correct behaviour) - but does NOT throw any error
message about the fact that the IDoc is not correct. This has to be fixed, so that the adapter will report an error when it receives an invalid IDoc. |
| Resolution: This problem is now fixed. |
|
| 17 | CR100627 | | Retries not stopping though the adapter is stopped |
| Symptom: Retries not stopping though the adapter is stopped |
| Resolution: This problem is now fixed. |
|
| 18 | CR100613 | | Gateway service is not turned to sapgwXX by default |
| Symptom: The system number changes on the first screen of EMD doesnt reflect in the connection properties screen of EMD. User has to manually modify the system number in the connection properties |
| Resolution: This problem is now fixed. |
|
| 19 | CR100595 | | Consecutive requests followed by a failed AEP outbound request FAIL |
| Symptom: Consecutive requests followed by a failed AEP outbound request FAIL |
| Resolution: This problem is now fixed. |
|
| 20 | CR100708 | | Load balancing-Not required connect properties should be disabled |
| Symptom: Load balancing-Not required connect properties should be disabled |
| Resolution: This problem is now fixed. |
|
| 21 | CR100661 | | Problems with BAPI result set call with a queryBO that has multiple entries |
| Symptom: Problems with BAPI result set call with a queryBO that has multiple entries |
| Resolution: This problem is now fixed. |
|
| 22 | CR100702 | | The SAP BAPI fault to show the right error code returned from SAP |
| Symptom: The SAP BAPI fault to show the right error code returned from SAP |
| Resolution: This problem is now fixed. |
|
| 23 | CR100747 | | Number Property is missing in the BAPI Fault BO |
| Symptom: The SAP BAPI fault shows only the ID and doesnt include the Number |
| Resolution: This problem is now fixed. |
|
| 24 | CR100604 | | 2 properties can be configured when try to Edit "MARA" during EMD |
| Symptom: 2 properties can be configured when try to Edit "MARA" during EMD |
| Resolution: This problem is now fixed. |
|
| 25 | CR100356 | | When BO name is same and BO namespace is different, inbound work may be failed |
| Symptom: When BO name is same and BO namespace is different, inbound work may be failed |
| Resolution: This problem is now fixed. |
|
| 26 | CR100532 | | Adapter will encoutner NPE after restart the app on server! |
| Symptom: Adapter will encoutner NPE after restart the app on server! |
| Resolution: This problem is now fixed. |
|
| 27 | CR100430 | | Memory leak in WAS Inbound with BeanType |
| Symptom: Memory leak in WAS Inbound with BeanType |
| Resolution: This problem is now fixed. |
|
| 28 | CR77930 | | Printing out the AdapterFoundationClasses version in the Logs/traces |
| Symptom: Printing out the AdapterFoundationClasses version in the Logs/traces |
| Resolution: This problem is now fixed. |
|
| 29 | CR100089 | JR35267 | BAPI Updates Not Seen |
| Symptom: CALLING 2 DIFFERENT BAPI'S (BAPI1 AND BAPI2) - ONE AFTER THE OTHER - TWO TIMES IN A ROW, BAPI1 IS NOT GETTING COMMITTED. |
| Resolution: This problem is now fixed. |
|
| Upgrade notes |
| To upgrade to this Interim fix version on WebSphere Process Server, do the following : |
| 1. Ensure that you have followed the "Installation Instructions" section in the download link before proceeding. |
| 2. If you need to use the test fix for EMD, delete the connector project in WebSphere Integration Developer, import the new RAR file, and apply the enterprise information system (EIS) specific dependency files. |
| a. Open the Java build path for the SCA module and remove the Connector project that is selected on Projects tab. |
| b. Open the dependency editor and remove the connector project. |
| c. Delete the connector project from the workspace |
| d. Import the new RAR file. Add any dependency files from EIS specific application-specific information as needed. |
| e. Open the Java build path for the SCA module and select the Connector project that is selected on the Projects tab. |
| f. Open the dependency editor and add the connector project if it is not already present and select Deploy with Module. |
| 3. If you need to update deployed applications on WebSphere Process Server, do the following : |
| a. Select Update for the corresponding application on the WebSphere Process Server administrative console. |
| b. Select Single Module with a relative path as name of the RAR file - CWYAP_SAPAdapter.rar, CWYAP_SAPAdapter_Tx.rar. |
| c. Click Browse on the local file system to select the updated RAR file that has the changes. |
| d. Select the default values in the remaining steps and click Finish. This will ensure that existing configurations, for example, are not changed and that only JAR files will be updated. |
| e. If there is a change in CWYAP_SAPAdapterExt.jar, the jar should placed in the 'lib' directory of WebSphere Process Server and the server has to restarted. |
| To upgrade to this Interim fix version on Websphere Message Broker (WMB) runtime, do the following : |
| 1. Unzip the Package_WMB.zip to your temp local directory , it would create following directory "AdapterPackage". |
| 2. Stop all your Brokers that are using this install. |
| 3. Go to "AdapterPackage" directory it should contain the files CWYAP_SAPAdapter.jar, CWYBS_AdapterFoundation.jar and CWYAP_SAPAdapterExt.jar |
| a. Backup the existing file CWYAP_SAPAdapter.jar, CWYBS_AdapterFoundation.jar and CWYAP_SAPAdapterExt.jar files. |
| b. Copy the above files to MQSI_INSTALL_PATH\adapters\prereqs\jar directory , where MQSI_INSTALL_PATH is WMB runtime install path. (eg. C:\Program Files\IBM\MQSI\7.0\adapters\prereqs\jars). |
| 4. Restart your Brokers. |
| To upgrade to this Interim fix version on Websphere Message Broker Toolkit (WMBT), do the following : |
| 1. Unzip the Package_WMBT.zip to your temp local directory , it will create the directory "AdapterPackage". |
| 2. Stop your WMB Toolkit. |
| a. Backup the existing CWYAP_SAPAdapter_Tx.rar file. |
| b. Copy the above CWYAP_SAPAdapter_Tx.rar files to WMBT_INSTALL_PATH\ResourceAdapters\SAP_(version_number) , where WMBT_INSTALL_PATH is WMBT runtime install path. (eg. C:\Program Files\IBM\WMBT70\ResourceAdapters\SAP_7.0.0.0). |
| 3. Restart WMBT. |