IBM Support

MustGather - Read first for WebSphere Partner Gateway Enterprise and Advanced Editions, version 6.1, 6.1.1 and 6.2

Troubleshooting


Problem

Information required by the IBM® WebSphere® Partner Gateway (WPG) Support team to diagnose problems on WPG system of version 6.1, 6.1.1 or 6.2.x. It is recommended to gather this information before calling IBM support, so as to help in early diagnosis, expedite the troubleshooting process and resolution of the Problem Management Records (PMRs) when: 1. Symptoms match known problems (rediscovery). 2. There is a non-defect problem that can be identified and resolved. 3. There is a defect that identifies a workaround to reduce severity. 4. Locating root cause can speed development of a code fix.

Resolving The Problem

This section instructs the various items of documentation that is required by the IBM Support team to diagnose the problem encountered with WebSphere Partner Gateway.


This WebSphere Partner Gateway Read first tech-note provides with different types of scenarios to collect perspective data depending on specific component or problem scenarios.

Please take a look at the following table, and select the type of the component or scenario that best describes the problem you experience. Then follow the detailed instructions provided in the associated MustGather tech-note:

Alert notification
Archival
AS2 / MDN
BCGMAS / BCGBUS / Service Integration technologies
DB2 SQL error
Document stuck / looping
ebMS / ebXML
EDI / FA; Mapping / Transformation
FTP / FTP Scripting type of Receiver or Destination
Installation / Uninstallation - Product; Fix Pack, iFix (UPDI)
Integrated FTP Server *
JMS (Java Messaging Service)
Migration
Other; Console accessibility; Unknown problem
Partner Migration
Performance
RosettaNet / Ack
Security
SFTP **
Start / Stop
Web Services

Note:
* WPG supports Integrated FTP Server feature on version v6.1.1, v6.2 and above.
** SFTP feature is supported on WPG v6.2 and above.

Back to top



► Instruction of how to check WPG system information (please expand)

  • For Operating System:
    • AIX®
    		oslevel -r
    Windows®
    		Go to Start>Control Planel>System. Find the "System" information in the 'General' tab.
    Linux®
    		uname -arv
    Solaris
    		uname -a
    HP-UX
    		uname -r
  • For WPG:
    • WPG
    		Determine topology mode of installed WPG:
    Simple mode - All hub components are installed in single WebSphere Application Server server (e.g. server1). This mode does not exploit clustering capabilities of the Network Deployment.
    Simple Distributed - consists of one application server (e.g. bcgserver) containing all hub components. A Network Deployment environment (e.g. bcgdmgr) is used. A separate messaging cluster (bcgmas) is used to allow internal communication between the components.
    Full Distributed - similar to the simple distributed topology, except each component (Receiver, Community Console, and the Document Manager ) resides on a different application server (e.g. bcgreceiver, bcgconsole, bcgdocmr).
    WPG version and fix pack level:
    Please check on the WPG Console log-on page.
    Determine what iFix have been applied:
    (For WPG version 6.2) Run bcgHistory.sh or bcgHistory.bat file located under <bcghub-dmgr>/bin location, and provide with the fix history output file. ("Complete" option will create a file named FixHistory.txt under the same directory.)
    WebSphere Application Server
    		Provide the versionInfo.txt by issuing the following command under <WAS_HOME>/bin:
    versionInfo -maintenancePackages -file versionInfo.txt
    JDK
    		Provide the output by issueing the below command under <WAS_HOME>/java/bin:
    java -version
  • For back-end system:
    • Software
    		Instruction for gathering information
    DB2®
    		1. command 'db2level'
    - or -
    2. Generate db2support data:
    In DB2 Command Line Processor, run the db2support command (by a user with SYSADM authority, such as an instance owner) to collect DB2 and system diagnostic information required to debug a problem. (Note that the -c option is used the db2support utility will establish a connection to the database):
    db2support <output_path> -d <database_name> -c

    The output is generated and stored in a compressed ZIP archive, db2support.zip.
    See this link for more information on the db2support command.
    Oracle®
    		sqlplus -version
    WebSphere MQ
    		dspmqver

    (Reporting MQ version information is required only if you are using MQ as external JMS provider.)

Back to top


► General hints and tips

► Related information

[{"Product":{"code":"SSDKJ8","label":"WebSphere Partner Gateway Enterprise Edition"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.2.1;6.2;6.1.1;6.1","Edition":"Advanced;Enterprise","Line of Business":{"code":"LOB59","label":"Sustainability Software"}},{"Product":{"code":"SSDKKW","label":"WebSphere Partner Gateway Advanced Edition"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":null,"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.2.1;6.2;6.1.1;6.1","Edition":"Advanced","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Product Synonym

WPG

Document Information

Modified date:
16 June 2018

UID

swg21281975

Page Feedback