Skip to main content

WebSphere MQ and WebSphere DataPower SOA Appliances problem determination - Middleware News

Section 1. Checking for resolutions to known problems:

    Visit the WebSphere DataPower SOA Appliances Product support portal for additional support content.
Section 2. Collecting information on this problem
    The following information describes the basic documentation needed by IBM support to investigate questions or problems when using IBM WebSphere DataPower SOA Appliances with WebSphere MQ

    Step 1. Describe the problem and environment
      1. Develop a clear description of the question or problem.
      2. Create a simple use case which shows the question or problem.
      3. List all the software, software version/release, with operating systems in the use case.

    Step 2: Turn on tracing to recreate and capture documentation for IBM Support to review
      1. Set the following trace and logging settings:
      2. Access the DataPower SOA Appliance by using the WebGUI interface through your browser.
      3. From the Control Panel in the WebGUI, select the Troubleshooting icon.
      4. On the Troubleshooting Panel, under Logging, set the Log Level to "debug" by using the selection box. Click Set Log Level.
      5. Select Debug Probe tab.
      6. Look for the service you are using.
      7. From the pull down select the service you configured for the simple use case.
      8. Click on the "Add Probe" button.

    Step 3: Recreate the problem.
      1. Using the simple use case, with sample data, recreate the problem using 2 or 3 transactions.
      2. Document the recreate steps.
      3. Capture screen images.
      4. Turn of traces.

    Step 4: Collect these files:
      • Error Report:
        1. From the Control Panel in the WebGUI, select the Troubleshooting icon.
        2. On the Troubleshooting Panel, under Reporting, click the Generate Error Report button.
        3. Once the Error Report is generated, right click on the View Error Report and select Save Target As ... to save the Error Report to a local file.
      • Export of appliance configuration:
        1. Export your configuration to a file by opening the ADMINISTRATION menu from the left hand navigation list.
        2. Click Export Config to display the initial Export Configuration screen.
        3. Click the Create a backup of the entire system radio button and click Next.
        4. Enter a comment noting the problem and click Build Export button.
        5. The configuration of the entire system is backed up to a file named export.zip. An opportunity to download the zip is automatically presented on the next page.
        6. Click the Download button to down load the file to your workstation.
      • Probe file -
        1. From the Control Panel in the WebGUI, select the Troubleshooting icon.
        2. Select Debug Probe tab.
        3. Look for the service you are using.
        4. From the pull down select the service you configured for the simple use case.
        5. Under Probe column, Click on the "Magnifying glass icon".
        6. Press the "Export Capture" button.
        7. The appliance will prompt you to download the file
      • MQ server error logs and FDC file(s) if any
Section 3. Preparing to contact IBM Support
      1. Obtain the version and release of WebSphere MQ and the operating system where WebSphere MQ is running
      2. Obtain the serial number of the appliance which experienced the problem. This is need for IBM entitlement processing, before a PMR can be created. Use the WebGUI, select Status > System > Version Information, locate tag on the case of the appliance, or from the CLI use Show System
      3. Locate the firmware version of the appliance. Using the WebGUI, select Status > System > Version Information or from the CLI use Show Version
      4. Locate your IBM customer number from your records.
      5. Determine the describe the business impact and severity of the problem based on the Severity Levels table found in the following technote: "WebSphere DataPower Extended Maintenance and Support Services".
      6. Determine which telephone number IBM should use to contact you concerning this problem report.
Section 4. Contacting IBM Support and sending your MustGather information to IBM support
      1. Refer to specifics in Contacting IBM WebSphere DataPower SOA Appliance Support.
      2. After you have contacted IBM Support, a PMR number will be assigned. Create a zip file of the MustGather information:
        • A text file which contains: the questions and answers to any of the MustGather steps, elaboration on the problem, list of steps to recreate, notation on specific errors, and description external events noted at the time of the error.
        • WebSphere DataPower WebGui and WebSphere MQScreen Captures
        • An error report at the time of the error, from either the WebGui or CLI.
        • WebSphere DataPower export zip
        • WebSphere DataPower probe export
        • Sample message from simple use case
      3. Rename the zip file and send to IBM as noted in Exchanging information with IBM WebSphere DataPower Technical Support for problem determination.
      4. Do not send any proprietary or confidential information from your company.

Comments

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201...

Adding SSL certificates to a mixed z/OS and Unix queue manager environment - Middleware News

Adding SSL certificates to a mixed z/OS and Unix queue manager environment - Middleware News 1. Security Considerations IBM advises customers who are using SSL, that the most secure way to do this is to use recognized Certification Authorities to sign their certificates. Ensuring secure transfer of information is the main purpose of SSL. This integrity must be properly observed when setting up SSL. You should always be certain who has signed each of your SSL certificates, who has had and who continues to have access to them. The first secure way to generate certificates is to generate a certificate request, on each system or machine that uses SSL. This request has to be signed by an external Certification Authority before it can be used. Getting certificate requests signed by a CA is secure, because during the signing process at no point do any files contain the certificate's Private Keys. This principle is vital to SSL security. Signing certificates in this way is covered...