1 / 34

PD² Adapter Overview

PD² Adapter Overview. SPS Spotlight Series November 2013. Overview. What is the Adapter v3.1 Adapter v3.1 Architecture Adapter v3.1 with MWS Architecture Integration Server pages My webMethods Server pages. What is the PD² Adapter?.

charlies
Download Presentation

PD² Adapter Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. PD² Adapter Overview SPS Spotlight Series November 2013

  2. Overview • What is the Adapter v3.1 • Adapter v3.1 Architecture • Adapter v3.1 with MWS Architecture • Integration Server pages • My webMethods Server pages

  3. What is the PD² Adapter? • The PD2 Adapter is a mechanism to insert and extract PD2 data in standard eXtensible Markup Language (XML) format • Standard XML format is defined by Document Type Definitions (DTDs) • DTDs are defined for Awards, PRs, Quotes, etc. • The PD2 Adapter is built using the webMethods Product Suite

  4. Components of the PD² Adapter • webMethods Integration Server • webMethods Broker • Event Subscription and PD2 buffer tables • Diagnostic scripts can be found in Script-Aid • My webMethods Server • My webMethods Database • PD² Adapter Packages and Services • webMethods • CACI • SPS Legacy Integration • PDS • Archiving

  5. Adapter v3.1 Architecture with MWS 2K Instance webMethods Physical Machine webMethods Integration Server SPS WmRoot WmTn Sybase Physical Machine 16K Instance webMethods Broker Server MWS Monitoring Administration Browser

  6. Integration Architecture

  7. Outgoing Transaction Flow

  8. Outgoing Transaction Flow (cont.) • A document is released in PD² • The document gets inserted into the PD2 Buffer table • The MultiPoll scheduler polls the buffer table for data to be extracted • Documents are only extracted if the corresponding event is configured and enabled in the event subscription table • If extracted successfully, will show up in MWS

  9. Information Exchange • Integrations enable information exchange between PD² and External Systems

  10. Incoming Transaction Flow

  11. webMethods Integration Server - localhost:5555 • Navigation on the Integration Server webpage

  12. Integration Server Scheduler Page Multipoll scheduler active and counting down.

  13. Integration Server Packages Legacy Integration packages

  14. Package Version Verification

  15. Integration Server – JDBC Pools Page Testing connection to MWS DB

  16. Integration Server – JDBC Adapters Page (Archiving, DocTransfer Connections)

  17. MWS for Adapter v3.1 • My webMethods Server (MWS) – What is it? • Portal platform for webMethods Product Suite • Provides browser-based User Interface (UI) for administration and transaction monitoring • MWS Features • TN/Broker Administration and Transaction Monitoring has been enhanced and moved to MWS • Administration functions: • Profile Management • Edit Document Types/Processing Rules • Monitoring functions: • Create/Save Queries • View Transaction Attributes, Content, Activity Log

  18. My webMethods Login Screen - localhost:8585

  19. My webMethods Server (MWS) • New look and feel and a new navigation framework • Forced to choose Monitoring or Administration and to wait for page to render to reach sub-menus in SR13 (left) • Sub-menus directly accessible in SR14

  20. TN Partner Profiles • Corporation (ex: SPS Help Desk) - standard • Broker -standard • GFEBS • GEX/EDA • NECO • PDS Duns value. Links back to the tn_receiver value in the Event Subscription table

  21. TN Partner Profiles Delivery Settings

  22. MWS Transactions page

  23. MWS Transactions page: Activity Log

  24. MWS Transactions page: Contents & XML

  25. Reviewing XML

  26. Helpful SPS Knowledge Base Articles • Locations of webMethods Server, Error, and Session logs • KB article 7028 • \webMethods71\Integration Server\logs • \webMethods71\MWS\server\default\logs • Locations of Translator (ETI) logs • KB article 7107 • Where do I need to update passwords • KB article 11728 • What information to provide to SPS Help Desk. • KB article 7115 • How do I search for incoming and outgoing documents processed by the PD² Adapter? • KB article 12005

  27. Questions & Answers:

  28. Q&A • Please explain what a package is. • A: An Adapter package is a set of compiled code or instructions that is executed by My webMethods to perform an intended function. Some examples include the checking for the existence of Standard Data, document numbers, and clauses. • Is there a difference between GEX and EDA? • A: There is no difference between the two. They are one in the same. • Can I remotely log into the MWS? If so, how? • A: Since the MWS is a rendered web page it is possible to view/access the MWS remotely however this is dependent on a site's respective firewall and internet restrictions.  Assuming there are no restrictions in place that would prevent the ability to remotely access the MWS over the site's network, the MWS should be able to be accessed by utilizing the Adapter server's IP Address combined with the Port number.  An example would appear as follows:  http://123.123.123.123:8585 • Do I need to have all of the Adapter Packages installed? • A: The standard packages for the Adapter must be installed. However the SPS Legacy Integrations, Archiving, Doc Transfer, and PDS are packages that can be optionally installed.

  29. Q&A continued • Is there a document that lists all places that requires a password update? • A: Yes, that Knowledge base article is 11728. • What happens when the MWS database fills up with transactions? • A: Typically the symptom that happens when the MWS database fills up is that access to the MWS page fails. You can resolve this 1 of 2 ways. The first is to stop/start the My webMethods Server Sybase service instance. The second one is to contact the SPS Level 2/3 Help Desk where we can issue you a script to truncate the XML stored in this database. • What happens to the transactions? Can we save those transactions? • A: Truncating the MWS removes all of the transactions from the database. However, since the MWS database is just a storage database for XML files, truncating those files does not affect the system. Typically those transactions are not saved as there is a configurable setting that actually archives and deletes those files after a set number of days. • How do I determine how my PD2 Event Subscription table is configured? • A: In Script-Aid, you can run the Event Subscription Diagnostic script to return the Event Subscription results. For assistance with configuration, please contact the SPS Level 2/3 Help Desk.

  30. Q&A continued • Is there a way to reflag a document so it will only produce EDA or PDS XML? • A: Currently when reflagging a document using the Adapter Reflag scripts in Script-Aid, there is not a way to distinguish between creating different types of XML. If the next release of Script-Aid (version 6.7) there will be a way to reflag for a specific file. • How do I know which version of the PD² Adapter I have installed? • A: On the Integration Server page, click on the Management link and navigate to the Fdi package and click on the name. If the version shown is 3.0, it is Adapter v3.0. If the version shown is 3.1, it is Adapter v3.1. We also have KB article 7457 with step by step instructions. • What's the proper way to shutdown and restart My webMethods 7 Integration Server? • A: Please review KB 7128 for instructions. Proper shutdown of the Integration Server is important and will prevent issues when starting back up. • Every time I start the Integration Server I see a message saying “No JMS Connection Alias,” should I be concerned with this error? • A: This error can be returned because the required Process Engine JMS Connection Alias has not been configured. This message can be ignored since the Adapter does not use the JMS Connection.

  31. Q&A continued • I tried to reprocess a document through the Adapter using the Adapter reflag scripts, but received an error stating the document was never flagged for processing through the Adapter. How can this be and how do I resolve this? • A: The error occurs because the document does not exist in the PD2 Buffer Table. Please contact the SPS Help Desk to have this issue reviewed. Also, the SPS Help Desk can issue you a script to insert the document into the buffer table so that it can get processed by the Adapter. • How do I confirm, or where can I check, whether or not the Adapter is sending out the SPS XML files to EDA? • A: Review the Transaction Page on MWS and see if the EDA rows are showing successful transmissions or if there are any errors. You should also contact EDA directly to see if they are receiving files from your site. • I was told that many of the error messages on the Integration Server 5555 can be ignored. How can I tell which messages are important? • A: Many of the errors that show up are informational in nature. Please contact the SPS Help Desk for further investigation into which errors can be ignored and which ones will require further attention. • Is there a way to check incoming/outgoing if we're currently on CITRIX? • A: Unfortunately this is a site specific question that will depend on the configuration of your Citrix Environment. If you have the ability to access a web browser within your Citrix environment and have the appropriate network connectivity to the Adapter/MWS instances, then you should have the ability to view Incoming and Outgoing Transactions.

  32. Q&A continued • Have you been able to resolve the issue of transactions looping in My WebMethods? • A: There are several workarounds for this issue.  The first being to increase the multiPoll scheduler from running every 60 seconds to running every 600 seconds.  If this does not resolve the issue, please contact the SPS Help Desk so that we can investigate the issue more closely and provide the other workarounds if needed. • How does the adapter determine order of processing for objects on the buffer_pmo? Does inbound data take precedence over outbound extractions? • A: The Adapter determines order by first in first out. It looks at the insertion timestamp and determines the order using that value. Outbound extractions take precedence over inbound data. • Can we see what is in the Broker table? • A: No. It is not possible to see what is inside the Broker. You can only see the number of documents within each Broker queue. • What if the client queues on the broker grow too large to clean out? Is there another method aside from dropping/recreating the broker? • A: Unfortunately, the easiest solution is to drop and recreate the entire Broker. We have a Knowledge Base article 5903 with instructions on how to perform these steps. If you experience this issue quite often, please contact the SPS Help Desk for further assistance.

  33. Q&A continued • My server has MWS services, but no webmethods directory. How can I tell if I have it installed or not? • A: Fresh installs of Adapter 3.1 (My webMethods 8.2) may get installed into the SoftwareAG folder. This is a My webMethods/SoftwareAG feature. • If we see the multiPoll scheduled task stuck in a 'running' status for a period of several hours (without documents sent to the MWS), what are the recommended steps toward resolution? • A: There are several steps you can take. The first one would be to delete and recreate the MultiPoll scheduler to see if that resolve the issue. The next step would be to check the Broker queues to see if documents are backing up in any of the queues. Also, try to restart the entire Adapter machine. If none of these resolve the issue, please contact the SPS Help Desk for further assistance. • Our JDBC Connection area only includes PD2JDBC Connection..., and it is not enabled. Is that a concern? • A: The PD2JDBCConnection should be enabled in order to ensure documents are processed to and from the PD² production database successfully.  If this connection is disabled, you can attempt to enable it through the JDBC Adapter connections page or open a Service Request with the SPS Help Desk so that this issue can be investigated as necessary.

  34. Q&A continued • Is EDA's IP address required to transmit files? • A: In order to successfully interface with the Global Exchange (GEX), you will need both the destination IP Address and Port number as well as an active EDAXML account to transmit the EDAXML data successfully to GEX. • We have to manually enable and disable multiPoll multiple times a day or the actions constantly repeat themselves and cause multiple errors and fill up MWS. Has this been looked into anymore? Is there a solution? We are using SR13. • A: While there is no permanent fix to address this issue, there are a few work-arounds that can be implemented.  Please reach out to the SPS Help Desk to ensure you are currently using all available work-arounds for this issue. • Does the password have to be set every 90 days? • A: That is a configurable option in Sybase Central and is dependent on each site’s security policy and the JPMO/DoD policy. • If a document processes for some interfaces but not others, and reflagging does not help, can a script fix that too? • A: This all depends on why the document failed to extract. If the document is not eligible for processing due to a difference in processing rules, then no script could be provided to "FORCE" the document to be extracted however you should contact the SPS Help Desk to investigate this issue further and accurately identify why this may not be extracting as you had hoped.

More Related