|
This table lists the enhancements and fixes in fix pack version 7.0.0.4.
|
|
Enhancements
|
|
There are no enhancements in this fix pack.
|
|
Fixes
|
|
1
|
103428
|
JR38869
|
Peoplesoft adapter fail to copy EIS value
|
|
Symptom: The signed Number field in EMD finally turns out to be integer attribute in generated BO definition file, this is by current design. In adapter user guideline page 6, it mentions BO attribute type for SIGNED NUMBER maps to attribute type Integer.
The problem is when EMD part can not generate decimal attribute for this kind of NUMBER/SIGNED NUMBER with decimal positions.
|
|
Resolution: Provide the capablity to EMD part to generate decimal attribute for NUMBER/SIGNED NUMBER.
|
|
|
2
|
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.
|
|
|
2
|
101456
|
|
Detecting illegal XML characters in SDO DESPI of Adapters
|
|
Symptom: A runtime exception is thrown during the BOXML serialization if the business object generated by the Adapter contains invalid xml characters.
|
|
Resolution: Adapter provides options to let the user to make choices and add validation in SDO DESPI of Adapters. Currently user can choose any of the 3 options: (a) Do not validate business object content for illegal XML characters (default); (b) Throw exceptions if business object content contains illegal XML charaters;(c) Discard illegal XML characters in business object content and log.
|
|
|
2
|
|
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 fix pack version 7.0.0.3.
|
|
Enhancements
|
|
There are no enhancements in this fix pack.
|
|
Fixes
|
|
1
|
100875
|
JR35982
|
JCA PeopleSoft Adapter fails with JOAException to set get keys in the second time when doing Update operation
|
|
Symptom: When adapter does Update operation, it fails with JOAException in the second time setting get keys for some CIs.
|
|
Resolution: Remove the second time setting get keys when doing Update and Update operation can succeed.
|
|
|
2
|
100760
|
JR35830
|
VALIDATION FOR PRIMARY KEY ASI SETTING IN CHILD BO
|
|
Symptom: When Child BO has no primary key ASI, Update operation can not succeed in some cases.
|
|
Resolution: Adapter code has been changed to support that Child BO could have no primary key ASI.
|
|
|
3
|
100841
|
JR35978
|
When Customer has no get keys set get() method is not available in EIS side. The response of a create operation fails with JOAException
|
|
Symptom: When CI has no get keys or get() method is not available in EIS side, the response of a create operation fails with JOAException.
|
|
Resolution: Adapter does not call get() method to generate response for Create operation when CI has no get keys or get() method is not available in EIS side.
|
|
|
4
|
101261
|
|
When doing child create, it fails due to insert at invalid position.
|
|
Symptom: When IgnoreEffectiveSequence and InsAtOldestEffDtPos are set to true and EIS has no child, if input data contains child, it will do child create and it fails due to insert at invalid position (-1).
|
|
Resolution: Adapter will insert at position 0 in this case to avoid error.
|
|
|
5
|
101262
|
|
When KeepRelations is false, Update operation returns incorrect response.
|
|
Symptom: When KeepRelations is false, EIS has some child and input data has no child, Update operation returns incorrect response that has a dummy child, sometimes even returns a dummy child with a non dummy grand child.
|
|
Resolution: Adapter will call get() to get the EIS data to generate correct response for Update operation if get() method is available in EIS side.
|
|
|
6
|
101324
|
JR36715
|
Peoplesoft Adapter fails for update operation when set setid as primary key.
|
|
Symptom: If a propety is not getkey, but is key, after running ESD, PrimaryKey ASI will be set to true for this property. This leads to runtime error when calling set method for this property.
|
|
Resolution: Adapter will not set PrimaryKey ASI to true for the property that is not getkey.
|
|
|
6
|
93590
|
|
When doing update for some specific CI, update will take no effect.
|
|
Symptom: Peoplesoft will perform an extra get operation when producing command for Update for solving the issue of CR 101262, but for some specific CI, this extra get will cause update fail.
|
|
Resolution: Add a flag to differentiate whether Peoplesoft record is used in producing command or generating response. The extra get operation is supposed to be performed when generating response.
|
|
|
|
This table lists the enhancements and fixes in fix pack version 7.0.0.1.
|
|
Enhancements
|
|
There are no enhancements in this fix pack.
|
|
Fixes
|
|
1
|
100262
|
|
Ambiguous semantics of the max connection number in the event delivery config
|
|
Symptom: Adapter will not use connection pool for event delivery if max connection number is 1 and delivery mode is "UNORDERED". In this situation, multiple thread will share one connection without thread safe mechanism, which will cause exception.
|
|
Resolution: The fix makes connection pool be used when max connection number is 1, connection pool keep thread safe and thus is recommended to use under "UNORDERED" and "ORDERED BY KEY" delivery mode; If user preferred not to use connection pool, he/she could set max connection number to 0, while thread safe will not be guaranteed.
|
|
|
2
|
77930
|
|
Printing out the AdapterFoundationClasses version in the Logs/traces.
|
|
Symptom: Currently with all the adapters , The AFC version is not printed out in the logs/traces. It would be really helpful to have this information printed out to the logs/traces especially in debugging issues due to conflicting AFC being loaded at runtime.
|
|
Resolution: print AFC version in the trace
|
|
|
3
|
99888
|
|
Change to use PmiRmJmxService MBean to get arm transaction factory name.
|
|
Symptom: When adapter gets ARM transaction factory name to process ARM transaction, a WAS internal private API is used for it, which need to be replaced with public interfaces.
|
|
Resolution: Switched to Invoke PmiRmJmxService MBean, a set of public interfaces exposed by WAS to get ARM transaction fatory name.
|
|
|
4
|
100356
|
|
When BO name is same and BO namespace is different, inbound work may be failed.
|
|
Symptom: When adapter creates 2 or more different modules with BO having same name but different namespace and structure, inbound and outbound operations of those modules will throw NullPointerException.
|
|
Resolution: Redefined the methods of "hashCode()" and "equals()" in the SDOV1Type class. Then individual adapter can distinguish those BO correctly by "namespace + name" if those BOs name are equal.
|
|
|
5
|
100406
|
|
Adapter will encoutner NPE after restart the app on server!
|
|
Symptom: For Adapter inbound and outbound operation(standalone deployment), after the application is restarted, the NullPointerException will appear when the adapter tries to query the ASI Infor from cache.
|
|
Resolution: The BO's namespace and name has been preserved as BO instance's fields. After the application is restarted, adapter can still get them from those instance's field rather than the stale data cache.
|
|
|
6
|
100430
|
|
Memory leak in WAS Inbound with BeanType.
|
|
Symptom: When adapter caches some BeanTypes that have a great deal of properties, java OutOfMemmory Exception be thrown during performing inbound and outbound operation with some events (persisting 20-50 times in WAS broker).
|
|
Resolution: The adapter now preserves those BeanType's class names as key of cache, rather than BeanType's instance. When broker is WAS, adapter can get BeanType structure by referring to its class name.
|
|
|
|
To upgrade to the fix pack version 7.0.0.3, do the following:
|
|
1. Ensure you have followed the 'Installation Instructions' section in the download link before proceeding further.
|
|
2. If you need to use the Fix Pack for EMD, delete the connector project in the WID, import the new rar and apply the EIS specific dependency files. The following steps describe how to do the same.
|
|
a. Open the Java Build Path for the SCA module and remove the Connector project selected on projects tab.
|
|
b. Open the dependency editor and remove the connector project.
|
|
c. Delete the connector project from workspace.
|
|
d. Import the new rar file. Add any dependency files from EIS specific APIs as needed.
|
|
e. Open Java build path for the SCA module and select the Connector project selected on projects tab.
|
|
f. Open the dependency editor and add the connector project if it is not already present and check "Deploy with Module".
|
|
3. To update deployed applications(that have an embedded adapter RAR file) on the WebSphere Process Server,use the following procedure
|
|
a. Stop the application that needs to be updated,using the WebSphere Process Server admin console
|
|
b. Select Update for the corresponding application in the WebSphere Process Server admin Console.
|
|
c. Select Replace or add a single file option with relative path as name of the rar file - CWYES_PeopleSoft.rar.
|
|
d. Click the Browse button to select the updated RAR file on your local file system.
|
|
e. Select the default values for the consecutive steps and select Finish.This will ensure that existing configurations e.g. MCF,are not changed and the JAR files are only updated.
|
|
|
July 08, 2011 6:00 PM
|
|
(C) 2011 IBM Corporation. Proprietary and Confidential. All Rights Reserved.
|
|