PD² Adapter Q&A Webinar SPS Spotlight Series May 2015

This information was originally created for The SPS Spotlight Series project, which ran from November 2013 through November 2015. Updates to the original content may be incorporated to ensure accuracy. If you have any questions about this information, please contact the SPS Help Desk at sps.helpdesk@caci.com.

Overview Difference between the ASF and the Adapter Difference between types of EDA files Locations of log files for the Adapter PDS Review of the PD² Buffer table Review of the multiPoll scheduler MWS errors Java memory

Differences between ASF and Adapter Q: What is the difference between the ASF and the Adapter? A: Even though most sites install the Application Server on the PD² Adapter machine, the two do not interact in any way. Application Server (ASF) Adapter Creates ps and idx files Creates XML files Sent to DLA via a 3rd party utility Can be configured to send XML files to EDA via DLA Transaction Svcs Creation of files is based on a configurable schedule Creation of files is based on the multiPoll scheduler time interval Task configured in the PD² client or on the ASF itself. Task configured on the Integration Server and MWS pages. Can generate a document Automated Attachment capability

Difference between ASF and Adapter The ASF provides this assistance in two main areas: Document Generation and Electronic Document Access (EDA). Generation of Documents. Instead of generation on a client machine, the ASF can generate the documents. Creation of EDA files. Creates the PostScript (ps) and Index (idx) files for released documents. These files get placed in a specific directory on the server where ASF is installed.

Difference between ASF and Adapter - ASF Clicking the Jobs button, opens the Jobs page listing the services provided by the ASF. Highlighting the Electronic Document Access (EDA) service, and clicking scheduler, should bring up the scheduler for EDA. Creation of EDA files is based on a configurable schedule. Generation of files is based on a configurable schedule.

Difference between ASF and Adapter - ASF The ASF EDA tasks can also be configured within the PD² client. From the menu option Select Utilities  System Administration. Click the ASF task to configure Electronic Document Access (EDA).

Difference between ASF and Adapter - Adapter The purpose of the PD² Adapter is to provide an interface that supports the integration between the PD² and external systems. The PD² Adapter is an application that offers the capability to extract and insert documents, and retrieve data based on certain events. The documents inserted and extracted by the PD² Adapter are formatted in a standard XML file format. Configurations for the Adapter are handled on the Integration Server page. http://localhost:5555/ The IP address and port are configurable at the site level.

Difference between ASF and Adapter - Adapter Creation of XML files is based on the multiPoll scheduler time interval. The multiPoll scheduler exist on the Integration Server > scheduler page, where the interval time can be configured.

Difference between ASF EDA files and Adapter EDA files Q: What is the difference between EDA files generated by the ASF and the EDA files generated by the Adapter? A: The ASF supports EDA by monitoring the PD² database for released awards and at a scheduled time, generating a PostScript (ps) and index file (idx) for each newly released or modified award and placing the files in a specified directory. Once created the PostScript and index file can be sent to the appropriate location at DLA Transaction Services. The process is typically done by an FTP push or pull based on the site’s preference.

Difference between ASF EDA files and Adapter EDA files The PD² Adapter supports EDA by monitoring the PD² database for released awards and, for each newly released or modified award, the Adapter will create an XML file. The delivery option of this XML file to DLA is configurable in the Trading Partner section in the My webMethods (MWS) website: https://localhost:8585 The IP address and port are configurable at the site level. KB articles: 15501 – Information on POCs to help obtain TN Partner Info. 15570 – Information on adding the new BPA doc types (55C, 9CM, 49C, 5CM).

Adapter EDA TN Partner Partner Profiles link list all of the TN Partner Profiles. This is where the EDA Partner is configured.

Adapter EDA TN Partner Once in the edit mode for the EDA Partner, click the Delivery Settings tab to configure how the EDA XML will be transmitted. In the Delivery Method tab, sites will need to configure how EDA XML files are created. There are 2 options: HTTPS: The EDA XML files will be sent directly to DLA TS. Sites will need to contact their GEX or DLA POC for connection information. FTP: This option will FTP the XML files to a specific location. This option is site specific and will require sites to either push the XML to DLA TS or have DLA TS pull these files (via SFTP).

The Integration Server and MWS log files Q: Where can I find the log files for the Integration Server and MWS? A: The Integration Server logs can be found: \SoftwareAG\IntegrationServer\logs The important ones are: server.log (or server.log.20150407) WMERROR_20150407_000056.log The MWS log files can be found: \SoftwareAG\MWS\server\default\logs _full_.log _problems_.log errors.log

The Integration Server and MWS log files The webMethods server log and error log can also be found on the Integration Server page, under the Logs section.

Order of Processing of Documents Q: How does the Adapter determine the order of processing for documents in the PD² Buffer table? A: The Adapter determines order by first in, first out. It looks at the insertion timestamp and determines the order using that value. Looking at the buffer table results, the ins_tmsp column shows when the documents were inserted into the buffer table.

PDS Questions Q: PDS XML files are no longer being created on my PD² Adapter Server. How can I troubleshoot this problem? A: There are several issues that could cause PDS XML files to stop creating. Are both the Integration Server and MWS services up and running? Try to log into the Integration Server page (localhost:5555) or the MWS page (localhost:8585). If unable to connect, further investigation will be needed. Are documents being polled and extracted from the buffer table? Use the Buffer Diagnostic script in Script-Aid to assist. In the \SoftwareAG\IntegrationServer\config directory, there is a file called PDSDocStore.dat. This file logs all documents processed by the PDS Extract Utility. If this file becomes corrupt, it can be deleted and then PDS XML files will be produced again. The PDSDocStore.dat file will get created again once documents begin processing.

PDS Questions Q: What could cause PDS XML files to stop getting created after I upgraded to SR15? A: There could be several factors. First, check to see if released documents are being inserted into the buffer table. You can run the Adapter Buffer Diagnostic script in Script-Aid (using the Date Range option) to determine this. If no released documents are being inserted, then there was a failure to run the PMOSqlScript2.sql script. This file can be found in the \SoftwareAG\install\sps folder. Running this script is part of the upgrade/install instructions. If documents are inserting into the buffer table, are they being polled and extracted? If not, check to see if the multiPoll scheduler is active or suspended.

PDS Data Schema Q: What data schema should PDS be using, v2.3 or v2.4? A: It is the site’s choice; however, sites should evaluate the use of U.S. Dollars and Lump Sum Units of Measure from the PDS Weekly Reports to decide if the site is ready for PDS data schema v2.4. EDA can handle PDS data schema v2.4, but it is preferred sites stay on PDS data schema v2.3 unless they have overcome U.S. Dollars and Lump Sum Unit of Measure usage problem.  In PDS data schema v2.3, awards and mods with these units of measure get a warning.  In PDS data schema v2.4, they will fail. 

Reviewing the multiPoll scheduler The state of the multiPoll scheduler is Suspended. This means that no documents are being polled or extracted from the PD² Database. Clicking on the Suspended link, the system will prompt you to verify if you want to activate the scheduler. The scheduler is now active and counting down.

Reviewing the PD² Buffer Table Q: When reviewing the Buffer results, how do I determine if/when a document was or wasn’t processed? A: From the results set above, the red shaded rows show documents that were inserted on 1/02/2015 and polled & extracted once, successfully. pol_flg = 1 ext_flg = P The blue shaded rows show documents that were inserted on 1/29/2015 but never extracted. pol_flg = 1 ext_flg = 0 The green shaded rows show documents that were inserted on 1/13/2015 and 2/8/2015 and were reflagged on 3/16/2015 to be reprocessed. They were polled & extracted successfully. pol_flg = 1 ext_flg = P

Reviewing the PD² Buffer Table Q:When reviewing the Buffer results, how do I determine if/when a document was or wasn’t processed? A: From the results set above, the red shaded rows show documents that were inserted on and after 4/08/2015. The results show that the document was polled successfully pol_flg = 1. However the ext_flg = E, which means the document experienced and error during extraction. The cause of this error should be shown in the Integration Server logs (server & error). If the ext_flg = E, the documents will not show up in the Transactions page in MWS.

Reviewing the PD² Buffer Table A pol_tmsp showing (NULL) and a pol_flg showing 0 means that the document was not polled An ext_flg showing 0 means that the document was not extracted.

Reflagging of a Document for PDS or EDA Show them script-aid scripts. In Script-Aid there are three (3) Scripts that can reflag documents to be processed by the PD² Adapter. These script will help recreate the following files (if applicable): PDS XML EDA XML Integration flat files The Reprocess Document for EDA script is used to flag a document so that it can be reprocessed by the ASF. This script will help recreate the Postscript (ps) and Index (idx) files.

Adapter/MWS Issue – Access Denied An error is being produced when trying to run the search function on the Transcations page in My webMethods: java.rmi.RemoteException: HTTP error response: [ISS.0084.9001] Invalid credentials <h4>Access Denied</h4>: This error can be caused by large amounts of data in the MWS database.

Adapter/MWS Issue – Access Denied Take the following steps to resolve this issue and prevent it from recurring: Reboot the entire Adapter server and at the same time stop/restart the MWS Sybase Server instance.  Query the ActivityLog table - select count(*) from ActivityLog -  in the MWS database to see how many rows exist.  If a large number of rows is returned (ex: 5000), sites should contact the SPS Help Desk for a script to truncate the data.  To prevent recurrence of the problem, change the MWS Database Archive and Delete Periods.  Instructions can be found in the PD² Adapter Functional Users Guide, Section 7.2.5 – ‘Changing Database Archive and Delete Periods’. More information can be found on this on the SPS Knowledge Base in KB id 14894.

Increasing Java Memory in SR15 Q: How do we increase Java memory on the Adapter server when we upgrade to SR15/Adapter v3.2? A: For Adapter v3.2 (SR15), the Java memory can be changed in the setenv.bat file. This file is located in the \SoftwareAG\IntegrationServer\bin directory. In SR15, the Adapter v3.2 can be installed on Windows 64bit. This allows the Java Memory values to be increased from the old value of 1024M to a much larger value. Doubling the value to 2048M would be a good starting point.