IBM E02HRLL-G Administration Guide - Page 171
Documents routed twice when network is lost or document manager server shutdown abruptly
View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 171 highlights
Documents routed twice when network is lost or document manager server shutdown abruptly If the system running your Document Manager abruptly loses its network connection or shuts down while processing a document that has not yet had its status updated, the document may be sent twice. The system administrator should take steps to avoid unexpected shutdowns or abnormal outages of the document manager workstation. 0A1 generated with data validation errors About this task The 0A1 specification mandates that GlobalSupplyChainCode be present in the XML. If the incoming 3A7 does not contain this value, it must be added as an attribute to the 0A1. GlobalSupplyChainCode must be either in the 3A7 document or added as attribute to 0A1 in Document Definition. To add the attribute: 1. Click Hub Admin > Hub Configuration > Document Definition. The Console displays the Manage Document Definitions window. 2. Click Package: RNIF > Protocol: Rosettanet > DocumentType: 0A1, and click the Edit attribute values icon. 3. If the Global Supply Chain Code attribute is not there, click Add Attributes to add it. 4. Select a value from the list. 5. Click Save. EDI reports export the first 1000 records only The export function of the 2 EDI Reports FA Overdue and Rejected Transactions exports the first 1000 records only in order to minimize unexpected system shutdowns because of memory overflow issues. If the number of records to export from the reports is over 1000, export the records directly from the related database view: LG_EDI_Overdue_FA_VW or LG_EDI_Rejected_Tx_VW. Console does not start after a server restart If you have installed WebSphere Partner Gateway, started the console server and logged into the console successfully, but find that once you have restarted the server your console does not display and runs in a loop, ensure that your tracing level is not set to ″WAS.*=finest″. This setting is used to perform the finest logging of all WebSphere Application Server related classes. The default connection time out for the WebSphere Partner Gateway console to start is set at 180 seconds and if the WebSphere Application Server tracing level is set to ″finest″ the processing time it takes to log all of that information along with making the requisite database connections causes the system to time out. Alter the setting and restart the console server. Note: Setting the tracing level to ″finest″ can affect system performance. Chapter 17. Troubleshooting 165