| This table lists the enhancements and
fixes in fix pack version 6.1.0.4. |
| Enhancements |
| There are no enhancements in this fix pack. |
| Fixes |
| 1 |
75473 |
|
The adapter returns old information/data from the SAP
EIS. |
| Symptom: When the adapter
retrieves data that was recently modified, the values that
were returned were not the latest values. |
| Resolution: The adapter resets
all connection resources before retrieving data, thereby,
retrieving the latest data. | |
| 2 |
75474 |
|
JCO Connection pool error during server restart |
| Symptom: After restarting the
server, some of the deployed modules threw an exception which
looks like: MessageEndpoint activation failed for
ActivationSpec com.ibm.j2ca.sap.SAPActivationSpecWithXid and
MDB Application
SAPInboundInvoiceServiceApp#SAPInboundInvoiceServiceEJB.jar#export.interfaces.SAPInvoiceInboundInterfaceEIS,
due to the following exception: com.sap.mw.jco.JCO$Exception:
(106) JCO_ERROR_RESOURCE: Connection pool boy.novo.dk is
removed. at
com.sap.mw.jco.JCO$Pool.getClient(JCO.java:5006) |
| Resolution: The adapter now
uses a unique pool name for all applications and the symptom
is no longer reproducible. | |
| 3 |
75643 |
|
While running an outbound using the BAPI WorkUnit
interface, the adapter resets the connection resource after
executing each BAPI thereby resetting the global state. BAPI's
executed later did not get the latest values. |
| Symptom: When running an
outbound using the BAPI WorkUnit interface, the adapter was
resetting connection resource after each BAPI execution, thus
resetting global state. This was causing BAPI called later not
to get the latest values. |
| Resolution: The adapter now
resets the connection resource only after executing all
BAPIs. | |
| 4 |
96037 |
|
When a simple BAPI call fails, the adapter does not
rollback to remove table locks. |
| Symptom: While using the
BAPI_GOODSMVT_CREATE BAPI, the adapter does not rollback
correctly in cases of failure. |
| Resolution: This has been
corrected. The adapter now rolls back correctly after any
failure. | |
| 5 |
96094 |
|
ALE inbound fails with a null pointer exception after
applying JR26701 on WPS. |
| Symptom: The adapter was still
excepting the WebSphere Process Server runtime to return an
exception when the attribute being queries does not exist. The
WebSphere Process Server runtime now returns a NULL instead
this leading to an NullPointerException. |
| Resolution: The adapter can now
handle a NULL if the BO.getProperty() call fails, in line with
the API specification change. | |
| 6 |
75522 |
|
The adapter does not support more than four BAPIs in
the EMD Object selection screen. |
| Symptom: When more than four
BAPIs are selected for processing during an inbound EMD, the
adapter does not correctly generate the artifacts and the
event processing fails. |
| Resolution: The adapter can now
handle more than four BAPIs and it generates the artifacts
correctly. | |
| 7 |
92875 |
|
During inbound processing, if you select three BAPIs,
an index out of range error is thrown during EMD. |
| Symptom: In the Configure
Composite Properties panel, if you select three BAPI's and
click on Next, the following error message is displayed: Error
in creating schema files. Array index out of range: 3 |
| Resolution: The EMD now
completes properly for any number of
BAPIs. | |
| 8 |
92924 |
|
An error message is always displayed at runtime,
without any effect on the behavior. |
| Symptom: While running any
inbound or outbound scenario, the following error message is
always dispayed, without any impact on runtime: [10/14/08
16:55:44:890 CST] 00000093 LogUtils E SAPRFCDataBinding
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. |
| Resolution: This issue has been
fixed. | |
| 9 |
75748 |
|
Commit or Rollback on BAPI should be done by the
container. |
| Symptom: The adapter was calling
the Commit or Rollback functionality on its own and not based
on the request by the container. |
| Resolution: This has been
fixed. Adapter will now call Commit or Rollback as per
container request if it is Local Transaction. When
NoTransaction is used, the adapter does an automatic
auto-Commit/Rollback | |
| 10 |
75654 |
|
When the Import or Export section of a BAPI (instead
the Tables section) contains tables, then a BAPI fails. |
| Symptom: During runtime, a BAPI
call with Table parameters in the Import or Export section
fails with the exception: CWYAP2044:The Z_READ_PRICING_DATA
BAPI (without transaction) failed. Error: Cannot convert field
CONFIG of type TABLE to JCO.Structure Explanation=In the input
BAPI business object, the data, metadata or both are
incorrect. |
| Resolution: The adapter now
supports Table parameters in the Import/Export
section. | |
| 11 |
75545 |
|
The adapter EMD throws "Error: nothing found" while
discovering certain BAPIs. |
| Symptom: When we attempt to
discover a nested BAPI(more than 2 levels deep) using the EMD
Discovery screen, ESD wizard connects to SAP with the Filter,
if specified. While retrieving the metadata from SAP, the
wizard terminates with the error ("Nothing found"). |
| Resolution: The adapter can now
handle nested BAPIs in the discovery
screen. | |
| 12 |
75649 |
|
Decimal fields are not saved in BAPIs. |
| Symptom: When decimal fields are
present in a BAPI, there are errors in the return type. |
| Resolution: The adapter can now
correctly handle decimal fields in BAPI
parameters. | |
| 13 |
75878 |
|
When more than one inbound application is running,
during startup an error message is displayed stating that the JCO
pool name already exists. |
| Symptom: When the first inbound
application is started, the hostname of the SAP system is used
as the pool name. When more than one application is started
simultaneously, an error message is displayed stating that the
JCO pool name already exists. |
| Resolution: The adapter now
creates unique pool names for each inbound
module. | |
| 14 |
75880 |
|
1475880ALE inbound listener threads still remain and
are not killed after the application is stopped |
| Symptom: When running an inbound
ALE module, some listener threads still remain and try to
process idocs even after the application is stopped. |
| Resolution: This has been
fixed. Listener threads are killed after the application
stops. | |
| 15 |
76039 |
|
ESD fails if two BAPIs have the same field names,
separted by a '_'. |
| Symptom: When you select two
BAPIs in the SCI interface ESD with field names that differ by
a _ alone(though the structures are the same), the ESD fails
to generate the artifacts. |
| Resolution: This has been
fixed. The adapter now ignores case while trying to generate
the second XSD. | |
| 16 |
92923 |
|
An error message displayed in the log when running
ALE outbound without a Business Graph. |
| Symptom: If you deploy an ALE
outbound module, uncheck "Generate business graph" in EMD, and
deploy it in WebSphere Process Server there is an exception
logged at runtime eventhough the functionality works fine -
[10/14/08 15:27:03:406 CST] 0000006d LogUtils E
com.ibm.j2ca.sap.ale.outbound.AleInvoker postIDoc
CWYAP3068:Cursor.getNext() method call failed, verify that the
input business object Cursor
com.ibm.j2ca.extension.dataexchange.sdo.InputCursorSDO@61b261b2
data is initialized. Error Message: Exception while getting
accessor. Please make sure property exists with accessor name
verb Explanation=The input data has not been populated in the
input business object Cursor. UserAction=Input business object
data may not have been initialized in the business object
specified in the error message, make sure data in initialized
before calling getNext(). |
| Resolution: This has been
fixed. The adapter now displays an Information message in the
log file. | |
| 17 |
92929 |
|
Log file has no information about the partner
character set information. |
| Symptom: If an incorrect value
is given to the partner character set, like abc123, the
adapter does not log an error indicating that the value set is
not valid. |
| Resolution: This has been
fixed. The adapter now displays an appropriate log
message. | |
| 18 |
93147 |
|
When you deploy SAP adapter module on WebSphere
Process Server, IllegalCharsetNameException is thrown. |
| Symptom: If no value is
specified for the Partner character set, the adapter throws an
IllegalCharsetNameException at runtime. |
| Resolution: This has been
fixed. The adapter does not throw the exception if no value is
set. The default value is used
instead. | |
| 19 |
76089 |
|
SQI without Business Graph throws an exception |
| Symptom: Executing SQI without
BG throws the following exception:
com.ibm.websphere.sca.ServiceRuntimeException: DataBinding
Exception thrown in J2CMethodBindingImpl.invoke()
commonj.connector.runtime.DataBindingException: Failed to
initialize cursor at
com.ibm.ws.sca.internal.j2c.J2CMethodBindingImpl.invoke(J2CMethodBindingImpl.java:360)
at
com.ibm.ws.sca.internal.j2c.J2CInterfaceBindingImpl.invoke(J2CInterfaceBindingImpl.java:118)
at
com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler.invokeDynamicImport(J2CImportHandler.java:1044)
at
com.ibm.ws.sca.internal.j2c.handler.J2CImportHandler.processMessage(J2CImportHandler.java:338)
at .................. |
| Resolution: This has been
fixed. | |
| 20 |
76042 |
|
Adapter throws an error if the data record is not
populated. |
| Symptom: When using one or more
SAPRequestNodes, the adapter fails to complete subsequent
request after a failure. |
| Resolution: This has been
fixed. | |
| 21 |
75794 |
|
Poor service diagnostics for wrongly configured SAP
Gateway host setting. |
| Symptom: The Adapter does not
throw an exception if the gateway host setting is wrongly
configured. It only logs a trace of the issue - thus the
Message Broker cannot catch an exception to be able to report
the issue to the user. |
| Resolution: This has been
fixed. | |
| 22 |
75795 |
|
Building Connection with Async q/tRFC BAPI with Out
Params gives bad error. |
| Symptom: The adapter continues
to execute a q/tRFC BAPI request which has a required Output
paramater. Since the q/tRFC call is async, required Output
parameters cannot be supported. |
| Resolution: This has been
fixed. The adapter does not allow completion of the EMD wizard
when selected BAPIs have required Output parameters for
executing a q/tRFC BAPI call. | |
| 23 |
75814 |
|
While using the adapter connection wizard to build an
Inbound to SAP adapter, if you set only "Gateway Service" and omit
"Gateway Host" the following error message is thrown: throw
NullPointerException
SAPManagedConnectionFactory.isGatewayConfigured |
| Symptom: The Adapter Connection
Wizard can allow a user to build an Inbound to SAP Adapter
that will throw NullPointerException
SAPManagedConnectionFactory.isGatewayConfigured if they only
set "Gateway Service" and omit "Gateway Host". |
| Resolution: This has been
fixed. | |
| 24 |
76058 |
46390,082,000 |
The JCA SAP adapter does not correctly generate the
operation name for inbound using extension IDocs. |
| Symptom: The adapter was
generating a different operation name during the EMD run and
another at runtime. This mismatch caused a
FunctionSelectorException at runtime. |
| Resolution: This has been
fixed. | |
| 25 |
90460,217,631 |
|
The time fields are being translated to hhmmss
format(0-12hr format) with missing AM/PM information. |
| Symptom: Adapter returns the
time value in 12 hour format without the AM/PM information
which is not complete. |
| Resolution: The adapter now
sends the time in 24 hour format
correctly. | |
| 26 |
52930,SGC,724 |
|
Adapter messages incorrectly uses the event type
"E" |
| Symptom: BAPI trace messages
that are actually non-error messages incorrectly uses the
event type "E". |
| Resolution: This has been
fixed. | |
| 27 |
76149 |
40278,999,858 |
The JCA SAP Adapter does not handle multibyte
characters from non-Unicode systems correctly. |
| Symptom: When using the QISS
module to retrieve data from a non-Unicode system, the BO gets
filled incorrectly as soon as table contains multibyte
characters. |
| Resolution: The adapter now
correctly handles multibyte characters from non-Unicode
systems. | |
| 28 |
76163 |
52369,SGC,724 |
The adapter does not serialize a complex IDoc
structure correctly in the endpoint. |
| Symptom: A BO dump of a complex,
multi-segment IDoc is not serialized correctly. |
| Resolution: This has been
fixed. | |
| 29 |
75915 |
|
Nullname space support in base class. |
| Symptom: Base class doesn't
support null namespace using 6.1 adapter. |
| Resolution: This has been
fixed. | |
| 30 |
93155 |
|
TypeFactory is using ext classloader instead of
application classloader in WAS. |
| Symptom: Class.forName method
could not find the record and throws Business Object not found
exception and Inbound on ALE fails. |
| Resolution: This has been
fixed. | |
| 31 |
76299 |
|
Adapter on WebSphere Transformation Extender throws a
NullPointerException. |
| Symptom: NullPointerException
thrown while performing outbound or inbound communication with
Websphere Adapter on WebSphere Transformation Extender. |
| Resolution: No more
NullPointerExceptions are thrown by the Adapter on WebSphere
Transformation Extender while performing outbound and inbound
operation. | |