Page 1 WebSphere IBM WebSphere Partner Gateway Enterprise and Advanced Editions ® Version 6.2 Administration Guide...
Page 2 5724-L68) and to all subsequent releases and modifications until otherwise indicated in new editions. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
Page 3: Table Of Contents
Localizing HTTP synchronous target time out . . 23 Transport and destination retries . . 46 Managing interactions and document definitions . . 23 Forward proxy support . . 49 Managing XML formats . . 24 © Copyright IBM Corp. 2007, 2008...
Page 4 . 125 Viewing destination details . . 88 Initiating and viewing document type . . 125 Changing destination status . . 88 Searching for an open document . . 126 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 5 SQL 0964C Transaction log full error on the Export and Import of archiver configuration . . 132 BCGMAS database . 162 Archiver runtime tasks . . 132 IBM service log unreadable. . 163 Archiver reports . . 133 WebSphere Application Server informational Archiver Restore . . 135 messages .
Page 6 Recovery process when queue and disk is full or unavailable . . 184 Index ....257 Workflow Handler Runtime Error . 184 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 7: Chapter 1. About This Book
This partner is created by the hubadmin user. This user is the company that bought the WebSphere Partner Gateway and is running the system. There can be many internal partners, but only one default internal partner. Businesses act as © Copyright IBM Corp. 2007, 2008...
Page 8: Typographic Conventions
ProductDir ProductDir represents the directory where the product is installed. All IBM WebSphere Partner Gateway product path names are relative to the directory where the IBM WebSphere Partner Gateway product is installed on your system. %text% and $text...
Page 9: Related Documents
Note: Refer to Technical Support Technotes and Flashes in WebSphere Partner Gateway Support Web site for the latest information about this product. Access http://www.ibm.com/software/integration/wspartnergateway/support/ and select the component area of interest. New in release 6.2 WebSphere Partner Gateway V6.2 supports the following new features: v Integration with WebSphere Transformation Extender using WebSphere Partner Gateway’s extensibility framework...
Page 10 CPP/CPA Editor for ebXML Message Service (ebMS) v Enhancements – Improved archiver performance – Improved document throughput performance for AS2 and large files For more details about the new 6.2 features, see http://www-01.ibm.com/ software/integration/wspartnergateway/about/ IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 11: Chapter 2. Managing The Websphere Partner Gateway Component Applications
For a simple mode system, it is necessary to know how to start and stop the application server that hosts all of the WebSphere Partner Gateway components. To start the WebSphere Partner Gateway components, run one of the following scripts: v UNIX <install dir>/bin/bcgStartServer.sh v Windows <install dir>\bin\bcgStartServer.bat © Copyright IBM Corp. 2007, 2008...
Page 12: Managing Websphere Partner Gateway Components In A Distributed Mode System
The cell is administered by the central WebSphere Deployment Manager. This means that: – All the servers within the cell can be started, stopped, and modified from the Deployment Manager. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 13: The Deployment Manager
3. Open an appropriate Internet browser. 4. Navigate to http://<computer name or IP address of the Deployment Manager>:55090/ibm/console to open the WebSphere Integrated Solutions Console Welcome login screen, and log in. Note: A user id is not required for logging in. On the left side of the Welcome screen you will see a list of tasks that can be done from this console.
Page 14: Starting And Stopping Servers From The Command Line
The Integrated FTP Server is started implicitly when the FTP Management server starts. To Stop the FTP Management server on a computer, use stopftpmgmtserver script. This script is located in the WPG Install Dir/ftpserver/bin. This script does not IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 15: Starting And Stopping The Components In A Simple Distributed Mode System
require any command line arguments. The Integrated FTP Server is stopped implicitly when the FTP Management server stops. Note: This is applicable for all deployment modes. Starting and stopping the components in a simple distributed mode system There are two clusters in a simple distributed mode system: bcgmasCluster The messaging cluster that has messaging servers.
Page 16: Stopping Servers In A Simple Distributed Mode System
2. Stop each WebSphere Partner Gateway server by running the stopServer script located in the <WebSphere Parnter Gateway Install Dir>/wasND/Profiles/ bcgprofile/bin directory on the computer where the server is installed. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 17: Starting And Stopping The Components In A Full Distributed Mode System
The syntax is for stopping the messaging server or bcgserver for the component servers is: stopServer <server_name> Where server_name is bcgmas for stopping the messaging server, and bcgserver for the component servers. Starting and stopping the components in a full distributed mode system Before you begin, you must know that there are four clusters in full distributed mode system.
Page 18: Stopping Servers In A Full Distributed Mode System
2. WebSphere Partner Gateway receiver (or console) servers. Note: The receiver and console servers can be stopped in either order. 3. WebSphere Partner Gateway document manager servers. 4. Messaging servers. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 19 Stopping all the servers using the Deployment Manager About this task 1. Select the bcgconsoleCluster (or bcgreceiverCluster) and click Stop. 2. Select the bcgreceiverCluster (or bcgconsoleCluster) and click Stop. 3. Select the bcgdocmgrCluster and click Stop. Note: Wait until the cluster has stopped before stopping the messaging cluster. 4.
Page 20 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 21: Chapter 3. Basic Community Console Tasks
Lightweight Directory Access Protocol (LDAP) then a Company Login Name field will not display. For further information about LDAP see the section, Chapter 7, “LDAP support for logon authentication,” on page 75. 5. Click Login. © Copyright IBM Corp. 2007, 2008...
Page 22: Navigating Through The Community Console
Icon name Collapse Copy Data contained Activate Delete Destination disabled Display raw document Document in progress Document processing failed Document processing successful Download map Edit Edit attribute values Edit off IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 23 View details View group memberships View Help system Note: The Help icon is translated when using the console with one of the IBM supported language locales. View permissions View the Document Definition attribute setup View users View validation errors Chapter 3.
Page 24: Logging Off From The Community Console
When you finish using the Community Console, click Logout at the top-right side of any Console window. The system logs you out and returns you to the Console Login window. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 25: Chapter 4. Hub Administration Tasks
– Uppercase characters – Lowercase characters – Numeric characters – Special characters This setting enables stricter security requirements when passwords are composed of English characters (ASCII). The default setting is off. It is © Copyright IBM Corp. 2007, 2008...
Page 26: Changing Database Connectivity, Database User And Password
Hub Admin > Hub Configuration > Event Codes. You can export them to other applications and can set the alert status of the event code as well. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 27: Viewing And Editing Event Codes
Viewing and editing event codes About this task The following procedure describes how to view the details of an event code. You can edit the visibility and alert status of the event code and view its severity. 1. Click Hub Admin > Hub Configuration > Event Codes. 2.
Page 28: Specifying Events That Can Be Notified
1. Click Hub Admin > Hub Configuration > Receivers. 2. On the Receiver List window, click the View Details icon to view the receiver details. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 29: Deleting Receivers
3. Click Edit icon to edit the receiver parameters. 4. In the Status field, select either Enabled or Disabled option to change the receiver status. Deleting receivers About this task You can delete receivers that you are not going to use. Note that the deletion occurs immediately.
Page 30: Managing Xml Formats
XML document families. For each family you can add, delete, and modify the XML formats in the family. You can also copy formats in a family, and move formats from one family to another. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 31: Large File Support
For complete information about creating XML document families and formats, see the WebSphere Partner Gateway Hub Configuration Guide. Large file support WebSphere Partner Gateway can use XPath version 1.0 expressions in formats. The processing power of XPath support limits the size of files that can be used with full XPath XML formats.
Page 32: Importing A Handler
EDIRouterBizProcessHandler support comma-separated content-type values. For these handlers, the text/plain content-type has to be added manually. Note: Do not change the handler values unless advised to do so by an IBM representative. Perform the following steps to add the text/plain attribute to these handlers.
Page 33: Managing Maps
Managing maps This section describes how to manage the different types of maps available for use with WebSphere Partner Gateway. Updating validation maps About this task Use this procedure to update a validation map currently in the system: 1. Click Hub Admin > Hub Configuration > Maps > Validation Maps. The validation maps currently in the system are displayed.
Page 34: Managing Edi Fa Maps
See the WebSphere Partner Gateway Hub Configuration Guide for attribute descriptions. 4. Update the envelope profile attribute values, and click Save. See the WebSphere Partner Gateway Hub Configuration Guide for attribute descriptions. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 35: Enveloper
Creating envelope profile records About this task 1. Click Hub Admin > Hub Configuration > EDI > Envelope Profile. 2. Click Create in the Envelope profiles window. 3. Type a value for the following fields: v Envelope profile name: Type a unique name for the new envelope profile. This is a required field.
Page 36: Connection Profiles
Use the Control Number Configuration page to configure control numbers that the Enveloper will use. You can also search for one or more control-number partners by name or by using wildcard search criteria, and optionally, EDI capability. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 37: Current Control Numbers
Wildcard searches can contain any combination of letters and asterisks (*) in place of other letters. A search using only an asterisk (*) as the search string returns a list of all EDI-capable partners. See the WebSphere Partner Gateway Hub Configuration Guide for more information about control numbers and control number masks.
Page 38: Managing System Configuration Data
3. Navigate to the configuration page you want to edit. 4. Click Edit on that page and change the data. 5. Click Save to save the changes to the database or Cancel to discard them. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 39: Configuring The Alert Mail Server
After changing data, most changes are made immediately without restarting the system. Changes that require one or more components to be restarted are noted in Appendix C“Appendix C - component-specific system attributes” on page 223. Note: You should not change any of these values unless you are very familiar with the way the WebSphere Partner Gateway product operates.
Page 40: Managing Event Delivery
IDs for the partners. You can also update existing partner definitions by importing them with the migration utility. With the IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 41: Managing Document Manager Information
administrative API, you can list some of the configuration artifacts in a system. A full export of the system using the migration utility provides listings of partner capabilities, partner connections, and receivers (targets) in the exported XML file. Managing Document Manager information You can use the admin console to view and modify the Document Manager administration properties.
Page 42: Supporting Ebms
CPA that are stored in the file system. While creating the interaction the default action is set to Pass Through. The following are the additional flows made for supporting ebMS: v Ping v Status Request IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 43: Non-Prepopulated Attributes
v Error During runtime when processing an ebMS document from a Partner, WebSphere Partner Gateway validates that the ebMS interaction conforms to the ebMS configuration (for example if encryption is required) and if there is a non - conformance the document is failed. The specific failure events can be viewed in the Document or ebMS viewers.
Page 44: Algorithms Supported By The Ebms
WebSphere Partner Gateway Hub Configuration Guide for more information on Validating WebServices. To validate Payload under SOAP Envelope, you need to perform the following additional configurations on the top of Webservice channel configuration: IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 45: Using Non-Repudiation Logging
v Upload the necessary validation map to WebSphere Partner Gateway. See Configuring document types chapter of WebSphere Partner Gateway Hub Configuration Guide for uploading validation maps onto WebSphere Partner gateway. v For DTD based validation, associate DTD against validation map under its respective WebService channel.
Page 46: Prerequisite To Setup Websphere Partner Gateway - Websphere Transformation Extender Integration Environment
RMI Server that it is listening. 9. In WebSphere Partner Gateway console, provide values for the attributes: v wtx.rmihostname v wtx.rmiport v rmiuseserver v bcg.wtx.mapLocation, which is under system administration tab IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 47: Chapter 5. Account Administration Tasks
3. Click Search. The system finds the partners that match your criteria. 4. To change the partner status, click Enabled or Disabled in the Status column. 5. To view the details for a partner, click the View details icon next to the partner. © Copyright IBM Corp. 2007, 2008...
Page 48: Deleting Partners
JMS Message Class JMS Message Type JMS Queue Name Lock User Number of Threads Password Provider URL Package Retry Count Retry Interval Server IP Receiver URI User Id User Name IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 49: Viewing And Editing Destinations
Table 4. Required transport information (continued) File Required transport HTTP HTTPS FTPS Scripting Directory SMTP information transport transport transport transport transport transport transport transport Validate Client IP Validate Client SSL Cert Note: 1. When the Authentication Required option of a destination is on, and the user name and password provided, the destination passes the user name and password to the external system that it connects to for document delivery.
Page 50 These attributes are read at the destination and replaced in the script file. User Id Required to access the FTP server. User Name User name for secure access through the partner firewall. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 51: Viewing And Editing Default Destination
Table 5. Destination parameter descriptions (continued) Parameter Description Validate Client IP Validates the IP address of the sending partner before processing the document. Used with the destination that is selected as a source destination for a connection. Validate Client SSL Cert Validates the sending partner’s digital certificate against the business id associated with the document before processing the document.
Page 52: Uploading Transports
For each destination retry (user defined), WebSphere Partner Gateway will automatically perform the transport retries. For example, if three destination retries are specified, the system retry pattern is: IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 53 v First attempt fails v Destination retry 1 fails Transport retry 1 fails Transport retry 2 fails Transport retry 3 fails v Destination retry 2 fails Transport retry 1 fails Transport retry 2 fails Transport retry 3 fails v Destination retry 3 fails Transport retry 1 fails Transport retry 2 fails Transport retry 3 fails...
Page 54 This is Transport retry 2 of 2. At this point, if the document has not been sent, the document is moved to the Gateway failed directory. For the previous scenario, the following overall time intervals occur: IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 55: Forward Proxy Support
120 seconds (Item 1 on page 47) – Console Gateway Connection timeout. Item 1 subtotal = 120 seconds 20 seconds (Item 2 on page 47) – Console Gateway Interval (Console retry 1 of 3) 120 seconds (Item 2a on page 47) – Console Gateway Connection timeout. 3 seconds (Item 2b on page 47) –...
Page 56 An option to filter is provided. Modify the certificate sets that are used in the connection. Alternatively, this can be done from the participant connection itself. Steps to manage Certificates sets: IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 57: Configuring The Certpath Related Properties
1. In the Console, navigate to Profile > {Partner} > Certificate > Certificate Management 2. If you have logged in as a Hub Operator, then choose an internal partner and external partner. Make sure that both the values are not ″ALL″. 3.
Page 58: Viewing And Editing Digital Certificates
To enable the use of CRLDP, set the com.ibm.security.enableCRLDP Java Virtual Machine property in the Generic JVM Properties field to true as follows: -D-com.ibm.security.enableCRLDP=true To disable the use of CRL DP, set the com.ibm.security.enableCRLDP Java Virtual Machine property in the Generic JVM Properties field to false as follows: -D-com.ibm.security.enableCRLDP=false...
Page 59: Disabling A Digital Certificate
2. Click the View details icon next to a certificate. The Console displays the Viewing Certificate Details window. 3. Click the Edit icon to edit the digital certificate. 4. Update the following parameters in the window, then click Save. Table 6. Digital Certificate Parameters Parameter Description Certificate name...
Page 60: Managing Partner Connections
This improves connection efficiency by multiplying the use of a single connection for production, test, or routing to multiple systems within one organization. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 61: Connection Duplication
Connection duplication The system avoids inadvertent duplication of connections by uniquely identifying each connection based on the following parameters: v Source Partner v Source package and version v Source protocol and version v Source document type and version v Source Activity (if defined) v Source Action (if defined) v Target Partner For example if there are two connections with the same source partner, source...
Page 62 Use the following procedure to conduct an advanced search for connections. When selecting a Source and a Target, observe the following guidelines: v The Source and Target must be unique. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 63: Changing Connection Configurations
v Do not mix a production destination with a test destination when selecting Source and Target; otherwise, an error occurs. Both the Source and the Target must be production or test destinations. 1. Click Account Admin > Connections > Partner Connections. The Console displays the Manage Connections window.
Page 64: Managing Exclusion Lists
RosettaNet notifications sent to the internal partner from its trading partners. Trading partners are identified by name and business ID. The following notifications can be selected for routing restriction: v 0A1 - Notification of Failure IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 65: Adding Partners To The Exclusion List
Sent to the internal partner by a partner that cannot complete a particular document type. v Backend Event A system-generated XML file sent to notify the internal partner that the partner has received a business document successfully. Adding partners to the exclusion list About this task Use the following procedure to add a partner to the Exclusion List.
Page 66 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 67: Chapter 6. Administering Partner Migration
IIOP port (typically 58809) of the console has to be available from the workstation where the utility runs. 2. You must have Java 5 available on the workstation where the utility will run. In your machine install JDK1.5. © Copyright IBM Corp. 2007, 2008...
Page 68 The directory that MIGRATION_PATH points to is the directory called bcgmigrate under the directory where the .zip file is extracted. For example, if you want to extract the files to the directory c:\IBM\migration, then you should set MIGRATION_PATH to c:\IBM\migration\bcgmigrate.
Page 69: Invoking From The Command Line
a .zip file holding an XML file. The XML must conform to the XML schema bcgMigrationExport.xsd located in migration utility root/schemas directory. Note: Ensure that the dependency requirements between export types are met. These dependencies are outlined further in the topic Migrating configuration type dependencies.
Page 70 Example command for import The following is an example command for import on a Windows system: bcgmigrate.bat -h localhost:58809 -a import -f D:\partnerMigration\BCGMigration_localhost.zip -u hubadmin -p admin123 -r d:\partnermigration\output -d 5 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 71: Mapping Of Xml Element With Console
For a UNIX system, the invocation is similar, except you use bcgmigrate.sh instead of bcgmigrate.bat. Once the import is completed, the logs are written to the file BCGMigration.log. If the -r option is not specified for an import, then the output will be placed in the directory configured in -f option.
Page 72 CapabilityInfo. There is an edit attribute icon that takes the attributes. These attributes are also part of CapabilityInfo in the form of ROAttrValueInfo. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 73: Exporting Partner Migration
Table 9. Map of XML element with Console (continued) Element name in XML Console view ChannelInfo Account Admin > Participant Connections > Search. Each row that is activated and deactivated. Initially all the connections are in deactivated state. They are available for connection creations. Once it is activated, the actual connections are created.
Page 74 Proxy configuration – All or None s. Event Codes – All or None t. Alert Notifications – All alert notifications or selected alert notifications or None. u. System admin properties – All or None IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 75: Considerations When Creating Your Own Import Data
Considerations when creating your own import data If you decide to create your own import file or to edit an import file that was created by the export utility, there are several things that you must consider. Not only does your XML file need to conform to the XML schema for an import file, but there are rules about the content of the file that are not controlled by the schema.
Page 76 Variable workflow (actions) Handlers v Contacts Partners v Addresses Partners v Control number initialization Partners v XML families and format Routing objects v Destinations Transport types, destination types, and handlers IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 77 v Transformation maps Routing objects v User configuration Partners and Group configuration v FTP User Configuration User configuration, Group configuration, and Partners v Group configuration Partners v Certificates Partners, Certificate sets, Destination types, and Routing objects Complex dependent items are the configurable items that are dependent on independent items and are more complex than first level dependent items.
Page 78: Export/Import Order
26. Control Number Initialization 27. Alert Notifications 28. B2B Capabilities 29. Connections 30. Gateways 31. Certificates 32. User configuration 33. FTP users 34. Error flow configuration 35. Archiver configuration 36. System Admin properties IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 79: Bcg And Dis Import
BCG and DIS Import BCG migration utility also imports maps and routing objects. When the production system has maps and routing objects imported through DIS tool, the BCG migration utility will overwrite, if overwrite option is enabled. If you import the run time environment (maps and routing objects) through DIS client, DIS import must be performed after BCG Import, so that the target production system will have the configuration required at run time.
Page 80 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 81: Chapter 7. Ldap Support For Logon Authentication
1. Make an entry in the java.security file residing in the WASND_ROOT/java/jre/ lib/security folder. The syntax for the new entry in the java.security file is: policy.url.3=file:///fully qualified path/wpg.policy 2. Restart all of the Java processes. © Copyright IBM Corp. 2007, 2008...
Page 82: User Names And Groups
This script is located in the {dbloader install location}/scripts/{database type} directory. This script: v Sets the attribute bcg.ldap.containerauth located in the Console System Administration > Console Properties > Common Attributes to False. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 83: Sample Ldap Configuration
IBM Tivoli Directory server and configure the WebSphere Application Server to authenticate users in the LDAP server. 1. Install the IBM Tivoli Directory server. Follow the instructions in the installation guide that comes with IBM Tivoli Directory server.
Page 84 Note: The values provided for the settings are shown as an example. 15. Click Finish. 16. Create a user and add a directory entry under 'o=ibm,c=us'. For example, to add user 'cn=user1,o=ibm,c=us': a. Select the 'Person' structural object class so that you get 'password' as an optional attribute.
Page 85: Specifying Ldap Users To Use The Websphere Partner Gateway Console
Restart the server using the following command: startserver <servername> -username <ldap_username> -password <ldap_password> Now the user can login using any username created in the IBM Tivoli Directory server. Specifying LDAP users to use the WebSphere Partner Gateway Console About this task After authentication in LDAP server, you must associate the LDAP user with the Hubuser role.
Page 86 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 87: Chapter 8. Support For Ipv6
To configure IPv6 on a Windows 2003/XP system, follow the Microsoft guidelines at http://www.microsoft.com/windowsserver2003/techinfo/overview/ ipv6faq.mspx. If you are operating on a IPv6 supported Windows platform consult your system administrator to enable the tunneling feature. © Copyright IBM Corp. 2007, 2008...
Page 88: Hp-Ux 11I
System Administration> nodes and select bcgnode. Click Full Resynchronize. Note: The synchronization can take approximately 5 to 10 minutes. 5. Restart all of the servers. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 89: Configuring Attributes
Configuring attributes About this task If the workstation where the Document Manager is installed is configured with IPv6 and documents are sent using a destination based on IPv6 protocol, then the IPv6 address of the workstation must be configured. To configure the workstation address: 1.
Page 90 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 91: Chapter 9. Managing The Destination Queue
Viewing the Destination Queue About this task To view a list of documents residing in the destination queue, use the following procedure: 1. Select Viewers > Destination Queue. The Console displays the Destination Queue window. © Copyright IBM Corp. 2007, 2008...
Page 92: Viewing Queued Documents
Viewing queued documents About this task To view documents queued for a specific Partner: 1. Click Viewers > Destination Queue. 2. From the Destination Queue Search window, click Documents Search. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 93: Stopping The Processing Of Documents From The Destination Queue
3. From the Queue Documents Search window, specify the search criteria (see Table 12). Table 12. Queue Documents Search window Criteria Description Partner Name To complete this field you can: 1. Specify the Partner name in the field. 2. Specify part of the partner name in this field and click Show Partners.
Page 94: Viewing Destination Details
Destination details and a list of queued documents appear. 5. Click Online in Destination Info to place a destination offline, or click Offline to place destination online. (You must be logged in as hubadmin to change destination status.) IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 95: Chapter 10. Analyzing Document Flows
Use the Document Analysis tool to get a detailed overview of the number of documents in the system, organized by state, within a specific time period. Use the search criteria to locate failed documents and investigate the reason for the failures. © Copyright IBM Corp. 2007, 2008...
Page 96: Viewing The State Of Documents In The System
Sort results by From Partner Name or To Partner Name. Refresh Controls if the search results are refreshed periodically (internal partner only). Refresh Rate Controls how often search results are refreshed (used by internal partner only). IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 97: Viewing Process And Event Details
3. Click Search. The system displays the Document Analysis Summary. Viewing process and event details About this task The following procedure describes how to view process and event details: 1. Click Tools > Document Analysis. The system displays the Document Analysis Search window.
Page 98: Exporting The Document Volume Report
Yahoo Web address (www.yahoo.com) into your browser address field. Nothing is sent; it is an empty request. The response received from the destination or Web server will indicate its status: IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 99: Pinging Ebms Partners
v If a response is returned, the server is up. v If nothing is returned, the server is down. Important: The Test Partner Connection feature works with HTTP that does not require any connection parameters. To test a partner connection: 1.
Page 100 The server refuses to send you this file. Maybe permission has been explicitly turned off. v 404 - Not Found IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 101 The server has not found anything matching the requested URL. This file doesn’t exist. This is the message you get if you type bad URL into your browser. This can also be sent if the server has been told to protect the document by telling unauthorized people that it does not exist.
Page 102: Edi Reports
Package field. Document type Specific document type. The types displayed vary depending on the value you select in the Protocol field. Reference ID Specifies a transaction ID. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 103: Edi Rejected Transaction Search
Table 18. EDI FA Overdue Search Criteria (continued) Value Description Sort By Specifies the criteria for sorting the search results. The defaults are Overtime Due and Descend. Use Descend to display the most overdue FAs first. Select Ascend to display the least overdue FAs first.
Page 104 Group Number The group number of the transaction. Transaction Number The identifying number of the transaction. Status Code The status code of FA. Status Text The status text of FA. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 105: Ftp Reports
FTP Reports FTP Reports provides details on FTP Statistics and FTP Connections. FTP Statistics About this task The FTP Statistics page will display the FTP Server Status in Read Only Mode. Note: The statistics will not be displayed if the FTP Server or the FTP Management Server is not available.
Page 106 The time when the user last accessed this connection. If this is blank, it means that the user has only logged in and not issued any command yet. Client Address The client IP from which the user has logged in. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 107: Chapter 11. Viewing Events And Documents
Data available through the Event Viewer includes event name, time stamp, user, and partner information. This data helps you identify the document or process that © Copyright IBM Corp. 2007, 2008...
Page 108: Event Types
Type of event: Debug, Info, Warning, Error, or Critical. Event code Search on available event codes based on selected event type. Event location Location where event was generated: all, unknown, source (from), target (to). IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 109: Viewing Event Details
Table 25. Event search criteria (continued) Value Description Sort by Sort results by: v Event Name v Time Stamp v Type v Source Partner v Source IP The default is Time Stamp. Descend or Ascend Descend displays the most recent time stamp or the beginning of the alphabet first.
Page 110: As Viewer
Ensure that the source gateway on the AS side is a SMTP gateway (in case of AS1) or HTTP destination (in case of IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 111: Searching For Messages
AS2) or FTP gateway (in case of AS3), which is configured to the MDN address. Thus the decryption failure MDN is sent back over this AS to none binary connection. Searching for messages About this task 1. Click Viewers > AS Viewer. The system displays the AS Viewer window. 2.
Page 112: Viewing Message Details
4. Click the View details icon next to the message that you want to view. The system displays the message and the associated document details, described in Table 27 on page 107. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 113: Rosettanet Viewer
Table 27. Message details Value Description Message ID ID number assigned to the AS packaged document. This number identifies the package only. The document itself has a separate Document ID number that is displayed with the document details. The maximum length is 255 characters. Source Partner Partner initiating a business process.
Page 114: Viewing Rosettanet Process Details
Document ID Proprietary document identifier assigned by the sending partner. The field is not in a fixed location and varies by document type. Source Partner Initiating partner. Target Partner Receiving partner. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 115: Viewing Raw Documents
4. Click the View details icon next to the RosettaNet process you want to view. The system displays details and associated documents for the selected process. 5. Click the View details icon next to the document you want to view. The system displays the document and associated event details.
Page 116 User defined search fields can be defined for the document in your system when configuring XML Formats, EDI Transformation maps, or can be defined in custom user exits. For more information about configuring XML Formats, see IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 117: Viewing Document Details, Events, And Raw Documents
the WebSphere Partner Gateway Hub Configuration Guide. For help on creating user exits, see the WebSphere Partner Gateway Programmers Guide. If custom search fields have not been defined for the documents in the system, then leave the search fields blank. Note: User defined search data is only saved for documents exchanged after the configuration is complete.
Page 118: Mass Document Resend
2. In the resultant screen of document viewer, select either Inbound or Outbound check box to resend all the documents in that category. Alternatively, you can resend the documents individually by selecting the check box against it. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 119: Viewing Edi Documents
Note: At a time, you can send either Inbound or Outbound and not both. 3. Click Resend. Viewing EDI documents In addition to pass through support for EDI Interchanges, WebSphere Partner Gateway supports the de-enveloping and enveloping of EDI Interchanges. The EDI interchange documents are de-enveloped when received from either an external partner or an internal partner.
Page 120: Document Validation Errors
XML field: Displays the XPath expression of the XML element causing the error. v Value description: Displays the erroneous value that is not being accepted for the element shown. v Error description: Describes the error condition and the correct element value expected. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 121: Viewing Data Validation Errors
Viewing data validation errors You can quickly search for documents that have failed processing using the color-coded text in the XML fields that contain validation errors. Fields that contain validation errors are displayed in red. If up to three separate validation errors occur within nested XML fields, the colors are used to distinguish between the error fields, as outlined in Table 33.
Page 122: Stopping A Document That Is In Process
Acquisition Engine (DAE), or Business Process Engine (BPE). v Out documents are those that leave WebSphere Partner Gateway, either to the Backend or to the partner. These documents can fail either in the BPE or Delivery Manager. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 123 To re-send a failed In document, select In document and click Resend. The document is resubmitted either from DAE or BPE based on the failure location. For example, In document failures can occur in DAE in the following cases: v Received document size is more than the maximum size limit. v Non-repudiation of the received document failed.
Page 124: Ebms Viewer
Ascend displays either the oldest time stamp or the end of the alphabet first. The default is Descend. Results Per Page Display n number of results per page. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 125: Viewing Ebms Process Details
3. Click Search. The system displays ebMS processes that match your search criteria. Viewing ebMS process details About this task 1. Click Viewers > ebMS Viewer. The system displays the ebMS Viewer Search window. 2. Select the search criteria from the lists. 3.
Page 126: Requesting And Viewing The Status Of A Document
See Chapter 9, “Managing the Destination Queue,” on page 85 for more information. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 127: Chapter 12. Simulating Production Traffic
“Preparing to test” on page 122 v “Setting up test scenarios” on page 122 v “Uploading and viewing your requests and responses” on page 125 v “Initiating and viewing document type” on page 125 © Copyright IBM Corp. 2007, 2008...
Page 128: Preparing To Test
Two-way outbound from an internal partner to an VTP_Owner VTP_OWNER external partner (Upload Request). Simulating internal partner. Two-way inbound from an external partner to an VTP_TP VTP_TP internal partner (Upload Request). Simulating external partner. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 129: Sample Scenarios
Table 35. Test scenarios (continued) Destination for Scenario Connection Two-way outbound from an internal partner to an VTP_TP VTP_TP external partner (Upload Response). Simulating external partner. Two-way inbound from an external partner to an VTP_Owner VTP_Owner internal partner (Upload Response). Sample scenarios This section describes the steps involved in configuring the RN PS to simulate two one-way RosettaNet (RN) interactions.
Page 130 /B2Bintegrate/rosettanet directory of the installation CD: v Package_RNIF_V02.00.zip v BCG_Package_RNIFV02.00_3A4V02.02.zip v Package_RNSC_1.0_RNIF_V02.00.zip v BCG_Package_RNSC1.0_RNIFV02.00_3A4V02.02.zip 2. Define the interactions for 3A4 purchase order requests and confirmations to be routed through the hub. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 131: Uploading And Viewing Your Requests And Responses
3. Configure the internal partner and external partner B2B capabilities to be the Source and Receiver of partner 3A4 requests and confirmations that use RNSC content. 4. Establish the partner connections between the internal partner and the external partner to support the scenario you want to simulate. 5.
Page 132: Searching For An Open Document
5. Click Route. The document is routed through the system to the appropriate destination based on routing information contained in the document. 6. Click View Document Type to view the document. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 133: Removing An Open Document
Removing an open document About this task 1. Click RosettaNet Partner Simulator > View Document Type. 2. Click Remove next to the displayed document. The document is deleted from the system. Chapter 12. Simulating production traffic...
Page 134 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 135: Chapter 13. Archiving
Partner Gateway archiver configuration. View archiver task About this task To view the archiver task, login as administrator and follow these steps: 1. Click Hub Admin > Hub Configuration > Archiver > Archiver Configuration. © Copyright IBM Corp. 2007, 2008...
Page 136 Disabled_Failed: displayed if a task fails while running. Click ’Resume’ to schedule the task If the status is Disabled, Stopping, or Running, then the following parameters will be in non-editable mode. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 137: Archiver Task Modification
Table 37. Archiver Configuration (continued) Section Field Description Data Retention Period in The number of days of data (specified in days this field) will be retained in the system, and the rest will be archived or purged. Copy NonRep data By default, this value will be checked, which indicates that the non-repudiation data will be backed up to the archive...
Page 138: Export And Import Of Archiver Configuration
Note: The criteria to backup the data is based on the configuration of the archiver task. 5. The archiver cleans-up the files from the Common File System. All files older than the cutoff date specified are deleted. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 139: Archiver Reports
6. The archiver purges the data from the tables in the database. The data that is updated or created earlier than the cutoff date is deleted. 7. The archiver task is then marked as ’Successful’ and the timestamp is updated in the reporting database tables.
Page 140 LG_SYNCH_REQ_RESP LG_ACTIVITY_EVENT LG_ACTIVITY LG_STACKTRACE LG_EVENT LG_ACK LG_CHAIN LG_EDI_FA_RECONCILE LG_ENVELOPE_INCLUSION BP_RNSTATEHDRAUDITLOG BP_RNMSGDIGEST BP_SPONSOR_STATE BP_RNSTATEDTL BP_RNSTATEHDR BP_AS_STATE_DTL BP_AS_STATE_HDR BP_STATE_HDR BP_RM_STATE_DTL State Engine BP_RM_STATE_HDR BP_SPONSOR_STATE_EBMS BP_DUPCHECK LG_SUMMARY_MI LG_SUMMARY_RN LG_SUMMARY_RN_MI LG_EVENT_EVENTSUMMARY LG_EVENTSUMMARY LG_ACTIVITY_SUMMARY LG_SUMMARY IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 141: Archiver Restore
v Number of rows purged from LG_MSG_ARCHIVE v Configuration settings enabled for that particular task v Purging schedule that was configured v Archive criteria used, such as Sending partner, Package, Protocol, and Document type. This is displayed only if the CopyNonRep data is selected while running the archiver task.
Page 142: Restoring Archived Data Of Websphere Partner Gateway V6.1 And Earlier
3. Click Search. The list of archiver tasks, along with the corresponding details are retrieved from the LG_MSG_RESTORE table and presented in a tabular format. The following information is displayed: IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 143: User Intervention For Archiving
v View Raw Message, click to view the raw message details of a particular record v Sending Partner, click on the partner name to view the complete partner profile v Package v Protocol v Document Type v Subvolume v Certificate name, click on the certificate name to view the certificate details. 4.
Page 144: Archiver Restrictions
. v DB2 version 8 does not support import using database calls. Hence you need to perform the import of database tables using the script provided - bcgDBNonRepImport. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 146: Log File Management
Find this by browsing to http://<deployment-mgr-address>:55090/admin. Port 55090 is the default used by the installer, however this may be different if the default port was not used during installation. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 147: Trace File Management
For both modes, the steps to configure the circular log files used by a server are the same. 1. Locate the server in the console by clicking on Servers/Application servers in the left pane to list the server names in the right pane. 2.
Page 148: Configuring Tracing In A Simple Mode System
2. To view the details of the server you want to configure, select the server name in the list. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 149: Tracing Tasks Common To Both Types Of Systems
3. Scroll down until you see the Troubleshooting heading near the bottom of the page. Click Logging and Tracing under Troubleshooting. 4. Click Diagnostic trace to view the details of the tracing configuration. By default, trace files for the distributed mode of WebSphere Partner Gateway applications are configured as shown in Table 40.
Page 150: Setting Log Detail Levels
Log detail levels are accessed using a link that is provided on the Diagnostic tracing Configuration and Runtime pages for an application server. When you click this link, you are presented with a page that shows a tree-view of IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 151: Identifying Websphere Partner Gateway Trace Messages
Note: The Java package names for WebSphere Partner Gateway classes all begin with the prefix com.ibm.bcg so you can locate the individual components by looking for packages that use this prefix. There are three ways to set log detail levels: v To set log details at the component level using the component tree: 1.
Page 152: Interpreting Websphere Application Server Log And Trace Messages
530 Maximum number of server connections has been reached. After the connection is established, the user information is authenticated. After user authentication is performed, FTP Server produces a client login notification IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 153 event. The appropriate login event message is logged into WebSphere Partner Gateway database. The possible response codes for user authentication are: v 501 Syntax errors in parameters or arguments v 503 Login with USER first. v 202 Already logged-in v 21 Maximum number of anonymous login has been reached. v 421 Maximum number of login has been reached.
Page 154 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 155: Chapter 15. Ftp Server Configuration Management
The Database Properties page allows you to enter the database properties like Host name, User name, Password, and Port. These values will automatically be saved in FTP server. Other Properties: The Other Properties page list all the editable properties. © Copyright IBM Corp. 2007, 2008...
Page 156: Ftp User Management
Search for FTP users across partners based on the required search criteria. v Edit FTP user information. v Create a new FTP user, which creates FTP user in the hub operator. v View FTP configuration information. v Edit FTP configuration information. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 157: Chapter 16. Relocation And Redeployment Of Websphere Partner Gateway
1. Stop all application servers, nodes, and deployment manager 2. Run the following commands to backup the configuration files of deployment manager and the components installed on deployment manager: v <Deployment Maneger Installed Path>/WASND/Profiles/<ProfileName>/bin/ backupConfig.bat © Copyright IBM Corp. 2007, 2008...
Page 158: Restoring The Configuration Details
<New IP/Hostname>. This executable is available in the folder <Installation directory of Deployment Manager>/bin. This command changes the host name/IP address of DMGR profile and starts the deployment manager. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 159: Changing The Host Name And Port Number Of Database
3. Change node associations with new DMGR hostname; execute bcgChangeDmgrHostname.bat\sh with new Host name/IP address and SOAP port as input parameters, that is bcgChangeDmgrHostname.bat\sh <New IP/Hostname> <SOAP PORTNUMBER>. This executable is available in the folder <Installation directory of hub>/bin. 4. Change the host name of the WebSphere Partner Gateway components; execute the following: a.
Page 160: Relocation And Redeployment Examples
3. Change the host name/IP address of the node on which the WebSphere Partner Gateway components are installed. Follow these steps: a. In Machine B where deployment manager is installed, execute bcgChangeNodeHostname.bat\sh with new Host name/IP address and IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 161 Current node name as the input parameters, for example, bcgChangeNodeHostname.bat 9.1.1.2 bcgnode_B. The executable is available in the folder <Installation directory of Deployment Manager>/bin. b. In Machine B, access the Nodes where all WebSphere Partner Gateway components are installed. Execute bcgChangeNodeHostname.bat\sh with new Host name/IP address, DMGR host name, and DMGR SOAP port as the parameters, for example, bcgChangeNodeHostname.bat 9.1.1.2 9.1.1.1 55880.
Page 162 9.1.1.2 55880. Ensure that you provide new host name/IP address and new port number of the MAS database that is installed on Machine A. Note: Manually restart all the servers. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 163: Chapter 17. Troubleshooting
“Ensuring sufficient virtual memory for DB2 agents” on page 161 v “Fixing DB2 SQL errors” on page 161 v “IBM service log unreadable” on page 163 v “WebSphere Application Server informational messages” on page 163 v “Increasing the Receiver timeout setting” on page 163 v “Optimizing database query performance”...
Page 164: Avoiding Long Processing Time On Large Encrypted As Documents
Large encrypted AS documents can take a long time to process on some lower-end hardware configurations. To avoid delays, take the following actions: 1. Set the AS Compressed attribute to Yes to decrease the size of the document being sent. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 165: Avoiding Long Processing Time For Large Encrypted Documents
2. Follow the steps in the ″“Avoiding out-of-memory errors” to increase memory size and speed up processing of encrypted documents. Avoiding long processing time for large encrypted documents Large files can be compressed before sending. Large file support with an order of size in GBs has been extended for AS2 and AS3.
Page 166: Document Manager Workload
UCA400_NO collating setting. DB2 version 8.2 does not support all special cases (as described in Unicode Standard version 4.00 Technical Standard #10) for all languages. In these instances contact DB2 directly. Oracle IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 167: Ensuring Sufficient Virtual Memory For Db2 Agents
The following is an example of an insufficient virtual memory error: Error[DBChannelCheck] [main Thread 2] - Error in channel check for com.ibm.bcg.channel.CheckChannelParameters@ebda9664 com.ibm.ejs.cm.portability.ResourceAllocationException: DB2 SQL error: SQLCODE: -955, SQLSTATE:57011, SQLERRMC: null ERROR [BPEEngine] [main Thread 2] - BPE: ERROR [BPEEngine] [main Thread 2] - java.lang.ArrayIndexOutOfBoundsException: 0...
Page 168: Sqlcode -444 Error
DB2 parameters: v LOGPRIMARY v LOGSECOND v LOGFILESIZ SQL 0964C Transaction log full error on the BCGMAS database WebSphere Partner Gateway creates the BCGMAS database with the following default configuration values: IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 169: Ibm Service Log Unreadable
Where filename is the file name of the service log file. Note that if the service log is not in the default directory you must fully qualify the service log file name. This showlog command produces output in Common Base Event XML format. For more examples of Showlog scripts, go to http://publib.boulder.ibm.com/ infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/ aes/ae/ttrb_viewsvclog.html.
Page 170: Optimizing Database Query Performance
The RUNSTATS command updates the database query access plan for each table and index. To optimize database query performance, run RUNSTATS at least once a week when IBM WebSphere Partner Gateway application and database activity is at a minimum. As database traffic increases, run RUNSTATS more frequently, up to once a day.
Page 171: Documents Routed Twice When Network Is Lost Or Document Manager Server Shutdown Abruptly
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.
Page 172: Ftpscripting Receiver Receives Stringindexoutofboundsexception
On the System Administration > DocMgr Administration > Alert Engine page, update the bcg.alertNotifications.mailHost attribute v On the System Administration > DocMgr Administration > Delivery Manager page, update the bcg.delivery.smtpHost attribute IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 173: Resolving Classnotfoundexception For User Exit Classes
Optionally, you can change the value of the attributes bcg.alertNotifications.mailFrom and bcg.alertNotifications.mailReplyTo. Resolving ClassNotFoundException for User Exit classes The ClassNotFoundException error can occur when a required class is not found for the following user exits: v Receiver user exits v Custom Actions user exit v Sender user exits If the ClassNotFoundException error occurs, verify the following information: 1.
Page 174: Disabling Jit In A Websphere Application Server When Websphere Partner Gateway Produces A Javacore
(A file or directory in the path name does not exist.) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java(Inlined Compiled Code)) at java.io.FileInputStream.<init>(FileInputStream.java(Inlined Compiled Code)) at com.ibm.bcg.util.NonRepudiationDbImpl.copyFile(NonRepudiationDbImpl.java (Compiled Code)) at com.ibm.bcg.util.NonRepudiationDbImpl.store(NonRepudiationDbImpl.java(Compiled Code)) at com.ibm.bcg.server.BPEBean.doNonRepudiation(BPEBean.java(Compiled Code)) at com.ibm.bcg.server.BPEBean.processDocument(BPEBean.java(Compiled Code)) IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 175: Creating File Directory Destination On A Drive Other Than C
Exception in delivering the message in first attempt. Exception is: java.lang.Exception: Destination directory '/wsi_gateway/inbound/tradingpartner01'; does not exist at com.ibm.bcg.delivery.FileSender.getFileSystemProperties(FileSender.javA:244) 17 Oct 2005 19:00:12,844 ERROR [SenderFramework] [Gw_1_2] - First attempt failed: reason: java.lang. Exception : Destination directory '/wsi_gateway/inbound/tradingpartner01' does not exist To define a folder on a drive other than C:, use three forward slashes instead of two.
Page 176: Fixing The Browser Error: 500
CRL Distribution Point field on the Details tab or made available by a Certificate Authority download site. For example: http://SVRSecure-crl.verisign.com/SVRTrialRoot2005.crl 2. Copy the CRL into the WebSphere Partner Gateway common/security/crl folder. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 177: Databinding In Jms Exports/Imports Within Websphere Process Server
[11/1/05 14:14:07:426 PST] 00000080 SystemOut O <<com.ibm. bcg.dataBinding.Utility>> warning : Error in the element JMS-IBM-MsgTypeMsg : Class 'BCGPackagingHeaders' does not have a feature named 'JMS-IBM-MsgType' [11/1/05 14:14:07:426 PST] 00000080 SystemOut O <<com.ibm.bcg.dataBinding.Utility>> warning : Error in the element JMS-IBM-PutTimeMsg : Class 'BCGPackagingHeaders' does not have a feature named 'JMS-IBM-PutTime' [11/1/05 14:14:07:426 PST] 00000080 SystemOut O <<com.ibm.bcg.dataBinding.Utility>>...
Page 178: Fixing Test Partner Connection For Ssl Connections
WebSphere Partner Gateway might fail to route an EDI document received through HTTP. An EDI document is sent with the content-type as text/plain and you should ensure that the Fixed Workflow handlers are configured correctly. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 179: Fixing Bcg210013 Error
The Content-Types attribute can be set by the following steps: 1. Go to Hub Admin > Hub Configuration > Fixed Workflow > InBound. 2. Click com.ibm.bcg.server.ChannelParseFactory. 3. Click Edit. 4. In the configured list, select EDIRouterBizProcessHandler and click Configure. 5. Edit Content-Types attribute by adding text/plain content type.
Page 180: Increasing Buffer Size To Prevent Document Transmission Low Performance
To increase the buffer size: 1. Open the DB2 Command Line Processor: Start > Programs > IBM DB2 > Command Line Tools > Command Line Processor. 2. Connect to the database using the command: DB2 >...
Page 181: Db Password Required Error In Bcghubinstall.log
DB password required error in bcgHubInstall.log During the installation of WebSphere Partner Gateway hub, the installer logs the following error messages in bcgHubInstall.log: com.ibm.bcg.install.ismp.wizard.conditions.JdbcDatabaseConnectCondition, err, ERROR: dbPassword is required This error message does not cause any side effects. Servers can be started successfully and the documents can be routed successfully.
Page 182: Loading The Native Library
TCPC0003E and CHFW0029E errors in the SystemOut.log file. The errors can occur because of the following conditions: 1. The configured ports can be used by other applications, check for any port conflicts. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 183: Ca Certificate Expiration
2. Ports numbers lower than 1024 are privileged ports which are reserved for root. Unless your system has been configured to specially handle this restriction, non-root users will not be able to bind to those ports. WebSphere Partner Gateway uses the non-root user, WebSphere Partner Gateway user, to start components, but it cannot bind to privileged ports.
Page 184: Vcbaseexception In The Systemout.log
Note: If you implement a WebSphere Application Server fix pack after reordering the java.security file, your change is overwritten and the file must be reordered again. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 185: Fixing The Hanging Threads Warning
(server) when a document is processing. [2/1/07 14:04:40:546 EST] 00000088 ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared exception during invocation of method "onMessage" on bean "BeanId(BCGBPE#ejb/bcgBpeEJB.jar#BPEMainEngineMDB, null)". Exception data: javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.websphere.csi.CSITransactionRolledbackException: com.ibm.websphere.csi.CSITransactionRolledbackException: at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:742) at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:181) at com.ibm.ejs.csi.NotSupported.postInvoke(NotSupported.java:99) at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:581)
Page 186: Fixing Websphere Mq Messages
4. Click on the extended tab and set the maximum message length attribute to a value greater than the size of the message. 5. Go to the Queue properties for the queue that was specified while creating the gateway. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 187: Mqjms2013 Error
6. Click on the extended tab and set the maximum message length attribute to a value greater than the size of the message. MQJMS2013 error About this task During WebSphere Partner Gateway communication with WebSphere MQ, you can receive the following error: MQJMS2013 invalid security authentication To resolve the error, perform the following steps: 1.
Page 188: Correcting The Shortcut Ports For Websphere Application Server
Start Menu entries to launch the WebSphere Application Server ND admin console, you must change the ports. To change the ports: 1. Go to Start Menu > Programs > IBM WebSphere > Application Server Network Deployment V6.1 > Profiles > bcgprofile > Administrative console.
Page 189: Rendering Of Tab Headings On Displays With Resolution Greater Than 1024
Oracle 9i and the WebSphere Application Server Messaging Engine. For more details, see the IBM Technote for this issue. To find the IBM Technote: 1. Go to http://www.ibm.com/support/us/. 2. Type number 1239781 in the search box.
Page 190: Java.lang.noclassdeffounderror With Reprocessdbloggingerrors.bat
<WAS_HOME>\deploytool\itp\plugins\com.ibm.websphere.v61_6.1.0. But, after every fixpack release, the folder name com.ibm.websphere.v61_6.1.0 gets changed to the corresponding fixpack version. Hence, the batch file fails to find the ws_runtime.jar. To fix this issue, you have to set the ws_runtime.jar path, as described below: 1.
Page 191: Error While Invoking Websphere Transformation Extender Map
WebSphere Transformation Extender dtxpi.jar file is installed in the router/lib.userexits directory. IBM Support Assistant (ISA) Plugin WebSphere Partner Gateway is enabled for IBM Support Assistant (ISA). The ISA product plugin for WebSphere Partner Gateway provides features such as log collection for PMR (Problem Management Report), Searching product specific information, and so on.
Page 192: As Signature Failure For Interop Content Type
To resolve the issue, add application/pkcs7- mime content type to excludedContentTypesForCanonicalization property. This is applicable only for AS2 transactions as there is no canonicalization support provided for RNIF transactions. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 193: Appendix A - Performance Considerations
2. Click the Edit icon next to Processing Interval (in Minutes). 3. Type a value (from 1 through 60) indicating the number of minutes that should occur before data is summarized again. The default value is 15. 4. Click Save. © Copyright IBM Corp. 2007, 2008...
Page 194 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 195: Appendix B - Failed Events
A connection could not be Error created for the B2B capability because no actions are associated with the interaction. BCG106600 Document Definition Child level = {0} greater Error Create Error than or equal to parent level = {1} © Copyright IBM Corp. 2007, 2008...
Page 196 This event is generated when Provided RN an unusable Process Instance Process-Instance-ID ID is received and the Error configuration property indicates that the system will not generate a new Process Instance ID. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 197 Table 43. Failed events (continued) Event code Event name Internal description Severity Extended description BCG200015 Internal Partner Error This event is generated when Provided RosettaNet the x-aux-production header GlobalUsageCode value is unusable and the Error configuration property indicates that the system will not use the default value on error.
Page 198 System Error in the System error in the Critical This event is generated when Inbound Processor Inbound Processor for the system encounters an document: {0} error in the inbound processor. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 199 Table 43. Failed events (continued) Event code Event name Internal description Severity Extended description BCG210033 Message Store Failed Unable to store document Error This event is generated when plain text the system is unable to store the document in plain text. Ensure that the system has sufficient disk space, and that the following directories...
Page 200 EDIINT process validation. BCG240003 RosettaNet RosettaNet Unpackaging Error This event is generated when Unpackaging Error Error the system is unable to parse the RosettaNet preamble during unpackaging. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 201 Table 43. Failed events (continued) Event code Event name Internal description Severity Extended description BCG240005 RNPackager Delivery Delivery Header Parser Error This event is generated when Header Parser Failure Error: {0} the system is unable to parse the RosettaNet delivery header during unpackaging.
Page 202 XML message cannot be found. BCG240068 Connection Parser Connection Parse Error This event is generated when RosettaNet Failure RosettaNet Failure connection info might not be found in a RosettaNet document. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 203 Table 43. Failed events (continued) Event code Event name Internal description Severity Extended description BCG240070 XML Connection XML connection parse Error This event is generated when Parse Failure failed the system is unable to find connection information for an XML file. BCG240071 Flat File Connection Flat File connection parse...
Page 204 Document Delivery Document delivery to Error This event is generated when Failed partner destination failed: document delivery to a partner’s destination fails and the document is set to a failed state. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 205 Table 43. Failed events (continued) Event code Event name Internal description Severity Extended description BCG250002 Delivery Scheduler An internal error occurred Critical This event is generated when Failed in the Delivery Scheduler: an uncategorized internal error occurred within the Delivery Manager, because of a bad destination or document data, rather than failure to deliver.
Page 206 BCGEDICM0013 Missing Input Data No input data source was Error Source specified for component {0} BCGEDICM0014 Missing Output Data No output data source was Error Source specified for component {0} IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 207 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDICM0020 Parsing Error in Component {0} failed due Error Component to errors parsing the input data BCGEDICM0021 Database Error An error occurred while Error trying to access the database.
Page 208 BCGEDIEM0128 Network error Network error message Error message received received from IBM VAN. from IBM VAN. Details are Message Id = {0}, Message Description = {1}, Severity Code = {2} IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 209 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDIEM0150 The document passed The document passed does Error does not apply to not apply to EDIAckHandler EDIAckHandler BCGEDIEM0151 Error processing edi Error processing edi ack.
Page 210 {0} BCGEDIEV0058 Deenvelope Failed An attempt to deenvelope a Error message failed BCGEDIFT0100 Expected Argument Syntax error on command: Error Missing {0}. An expected argument was missing IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 211 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDIFT0110 FTP script Processing Error caused FTP script Error Stopped processing to stop BCGEDIFT0111 Missing File Base No base name provided for Error Name retrieved files...
Page 212 BCGEDIFT0224 GET Command Failed GET command failed. Error Reason: {0} BCGEDIFT0225 LIST Command LIST command failed. Error Failed Reason: {0} BCGEDIFT0226 QUIT Command QUIT command failed. Error Failed Reason: {0} IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 213 Syntax: {0}, Dictionary: {1}, Document: BCGEDINK0001 Invalid Network The document passed to Error Acknowledgement the IBM VAN network acknowledgement component is not a valid network acknowledgement BCGEDINK0002 Invalid Attribute The attribute {0} has an Error...
Page 214 Document values used for parsing were not specified or are blank BCGEDIUP0034 Invalid Structure Character separated data is Error Usage not a supported option for data formats that contain structures IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 215 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDIUP0038 Missing Record End of record reached Error Delimiter without record delimiter detected. Record delimiter expected was {0}. Record number was {1}. Record name was {2}.
Page 216 LOOP & RECORD BCGEDIUP0114 Unexpected Nodes Invalid ROD (flat file) Error Under Structure Node DataFormat. ROD (flat file) STRUCTURE node: {0} has child nodes other than STRUCTURE & FIELD IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 217 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDIUP0115 Empty Structure Child Elements not found Error Found in MetaDataElement: {0}, Element Type STRUCTURE BCGEDIUP0116 Invalid Character in Invalid Character found Error Data Format with {0} data format.
Page 218 {0}, Map name: {1}, Exception text: {2} BCGEDIUT0407 Database Error The control string for map Error Reading Map Control {0} could not be loaded String because of a database error IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 219 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDIUT0501 Input Document for The input document for the Error Transformation is transformation is empty Empty BCGEDIVA0001 Mandatory Data Mandatory data element is Error Element Missing missing, element name =...
Page 220 Segment name = {2}, segment position = {3}, sending trading partner id/qualifier = {4}/{5}, receiving trading partner id/qualifier = {6}/{7}, control numbers = {8} IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 221 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDIVA0014 Failed ’List Failed ’list conditional’ (L) Error Conditional’ (L) condition, the standard Condition defines items {0} as conditionally paired, but only {1} is present. If the first item is present, at least on of the others must be present.
Page 222 = {1}, segment position = {2}, sending trading partner id/qualifier = {3}/{4}, receiving trading partner id/qualifier = {5}/{6}, control numbers = {7}. Element type = {8}, value = IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 223 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDIVA0034 Invalid Time Element Invalid time element, Error element name = {0}, segment name = {1}, segment position = {2}, sending trading partner id/qualifier = {3}/{4}, receiving trading partner id/qualifier = {5}/{6},...
Page 224 Error Message Trailer trailer missing or invalid, Missing or Invalid control number = {0}, sending trading partner id/qualifier = {1}/{2}, receiving trading partner id/qualifier = {3}/{4}, control numbers = {5} IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 225 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDIVA0103 Transaction Set or Transaction set or message Error Message Trailer Count trailer contains an invalid Invalid segment count, transaction set or message control number = {0}, sending trading partner id/qualifier = {1}/{2}, receiving trading...
Page 226 Service segment validation Error validation not not supported for supported for document syntax document syntax. BCGEDIVA0991 Required Property or Required property or Error Content Element Not content element {0} not Found found IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 227 Table 44. EDI event codes and messages (continued) EDI Event code Event name Internal description Severity Extended description BCGEDIVA0992 No Message No message properties Error Properties Found found BCGEDIVA0993 Metadata Not Found Metadata not found, Error dictionary = {0}, document type = {1}, syntax = {2} BCGEDIVA0994 Empty Transaction Set...
Page 228 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 229: Appendix C - Component-Specific System Attributes
Table 45 are used to extract the corresponding values: Table 45. Default XPath Queries Default XPath queries Extracted value Document ID thisDocumentIdentifier[0]/ProprietaryDocumentIdentifier[0] thisMessageIdentifier[0]/ProprietaryMessageIdentifier[0] Document creation date and time stamp thisDocumentGenerationDateTime[0]/DateTimeStamp[0] theMessageDatetime[0]/DateTimeStamp[0] thisMessageDateTime[0]/DateTimeStamp[0] GlobalFunctionCode GlobalDocumentFunctionCode[0] © Copyright IBM Corp. 2007, 2008...
Page 230: Editing Ftp Administration
Attributes window where you can view, add and edit the XPath queries. Editing FTP Administration The FTP administration has the following properties: v Listener Properties v Connection Properties v IP Restrictor v Event properties v Database Properties v Other Properties IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 231 Listener properties: The component in the FTP server that listens to clients connection, command execution and so on. The properties of this listener are default listener properties and Client auth. Table 46. Default Listener Properties Property name Description bcg.ftp.config.listeners.default.class The concrete listener implementation. bcg.ftp.config.listeners.default.address The ip-address or hostname of the host that runs the ftp server.
Page 232 -connection.passive.ports bcg.ftp.config.listeners. clientauth.data- Class used for SSL connection.ssl.class Connection Properties: All connection properties are editable. Table 48. Connection Properties Property Name Description bcg.ftp.config.connection-manager.max-connection Maximum allowed connections bcg.ftp.config.connection-manager.max-login Maximum logins allowed IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 233 Table 48. Connection Properties (continued) Property Name Description bcg.ftp.config.connection-manager.default-idle-time Default idle time in seconds after a connection is established to disconnect bcg.ftp.config.connection-manager.timeout-poll-interval Time out interval to run the polling thread which collects idle connections IP Restrictor Properties: This has a list of IP Addresses having restricted access. Table 49.
Page 234: Attribute Tables
Attributes used to configure synchronous response handling by the receiver component—Table 69 on page 248 v Attributes used to configure the directory names used by the receiver component—Table 70 on page 248 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 235 v Attributes used to configure miscellaneous aspects of the receiver component—Table 71 on page 248 v Attributes used to configure the summary engine subcomponent of the Document Manager—Table 72 on page 249 v Attributes used to configure the sponsor engine subcomponent of the Document Manager—Table 73 on page 249 v Attributes used to configure the archiver subcomponent of the Document Manager—Table 74 on page 249...
Page 236 No default value String List the event codes, separated by bcg.event_log_exclude commas, that are not to be processed. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 237 Table 53. Attributes shared by one or more components (continued) Entry Default value Possible settings Description String with directory Path to directory where certificate bcg.CRLDir <Hub install path revocation list files are stored. root>/common/ security/crl/ TRUE String Boolean value A TRUE value causes the bcg.checkRevocationStatus TRUE or FALSE.
Page 238 See the description for traceLevel.XML-Parser and 2 traceLevel.All. Integer between 0 See the description for traceLevel.ROD-Parser and 2 traceLevel.All. Integer between 0 See the description for traceLevel.EDI-Serializer and 2 traceLevel.All. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 239 Table 54. Attributes used for processing EDI documents (continued) Entry Default value Possible settings Description Integer between 0 See the description for traceLevel.XML-Serializer and 2 traceLevel.All. Integer between 0 See the description for traceLevel.ROD-Serializer and 2 traceLevel.All. Integer between 0 See the description for traceLevel.EDI-Splitter and 2...
Page 240 Note: For Internationalization purposes you may want to change these values depending on the language of the OS and what is specified for directory names. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 241 Possible Entry Default value settings Description jms/bcg/cf/CONCF JNDI name Internal setting that affects bcg.jms.queue.factory inter-component communications. This is for IBM use only. jms/bcg/cf/CONCF JNDI name Internal setting that affects bcg.jms.topic.factory inter-component communications. This is for IBM use only. com.ibm. Class name Internal setting that affects bcg.jms.jndi_factory...
Page 242 The value of this attribute should match the setting of the attribute bcg.certs.vtp.CertificateDir, which is set in the Document Manager security settings. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 243 Table 57. Attributes used to configure the RosettaNet simulator (continued) Entry Default value Possible setting Description No default value File name The name of the certificate file bcg.console.certs.vtp.Certificate (DER, binary format) containing a public key that is used by the simulator.
Page 244 After every given number of bcg.BatchAlertScheduler.scheduleTime seconds, the batch alert generator will generate the batch alerts. Integer After every given number of bcg.NotificationAlertScheduler. seconds, the notification alert scheduleTime generator will generate the notification alerts. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 245 Table 59. Attributes used to configure the AS state engine Entry Default value Possible setting Description Integer Number of threads used by the bcg.asstate.thread_count AS state engine. Integer Batch size is always set to 1. bcg.asstate.batchSize Changing this attribute will not have any effect, and the attribute is reserved for future use.
Page 246 Time in milliseconds between directory bcg.inbound_poll_interval. scans. synchronous Integer Number of inbound threads for bcg.in_thread_count.synchronous synchronous router. Integer Maximum number of files to pick up in a bcg.inbound_files_per_pass. scan. synchronous IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 247 Table 63. Attributes used to configure the delivery manager Possible Entry Default value setting Description String Root directory under which bcg.delivery.gatewayDirectory <Hub install the files and subdirectories root>/common/gateways used to manage destinations (gateways) are located. $ROUTER.DM. SMTP_RELAY$ IP/Hostname Host that is used when bcg.delivery.smtpHost posting documents using SMTP.
Page 248 Internal setting that affects bcg.oaq_bpe_in.main main_InboundQ inter-component communications. This is for IBM use only. jms/bcg/queue/ JNDI name Internal setting that affects bcg.oaq_bpe_out.main deliveryManagerQ inter-component communications. This is for IBM use only. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 249 Entry Default value setting Description jms/bcg/queue/ JNDI name Internal setting that affects bcg.oaq_bpe_in.signal signal_InboundQ inter-component communications. This is for IBM use only. jms/bcg/queue/ JNDI name Internal setting that affects bcg.oaq_bpe_out.signal deliveryManagerQ inter-component communications. This is for IBM use only. jms/bcg/queue/...
Page 250 GlobalStateEngInstanceId and generates an MDN. This parameter is also used for retries. String Reporting UA is to indicate the bcg.ediint.reportingUA user agent reporting the MDN. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 251 Table 65. Attributes used to configure the Document Manager packaging process (continued) Entry Default value Possible setting Description 5000 Integer For AS outbound messages (with bcg.ediint.retryWaitTmMS asynchronous MDN), if the MDN is not received, the AS Engine retries after this number of milliseconds.
Page 252 Fax number of the 0A1 contact bcg.0A1.fromFaxNbr CONTACT.FAX_NO$ documentid String The value of this property acts as bcg.rnif.pip.twoaction.correlation correlation parameter between the 1-action and the 2-action of a two action PIP. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 253 This is for IBM use only. corbaloc:iiop: Internal setting that affects bcg.jms.context_url localhost:58809 inter-component communications. This is for IBM use only. Port 58809 is the default port for a simple mode installation. Your installation may differ. jms/bcg/queue/datalogQ JNDI name Internal setting that affects bcg.oaq_log_q...
Page 254 Default value Possible setting Description No default An IPv6 address The IPv6 address used by the bcg.receiver.ipv6 receivers. This is required if the computer that hosts the receiver component uses IPv6. IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 255 Table 72. Attributes used to configure the summary engine subcomponent of the Document Manager Entry Default value Possible setting Description Integer Time interval in minutes that bcg.summary.processingInterval determines how often event summary processing occurs. Integer The number of threads that bcg.summaryEng.thread_count prepare the event summary.
Page 256 Table 78. Other EDI properties Entry Default value Possible setting Description transcript.file.option If the option yes is selected, transcript files are generated in the current working directory specified under ″transcripts″ folder IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 257 Table 78. Other EDI properties (continued) Entry Default value Possible setting Description PageThreshold 1000 0–n This property controls paging of repeating message structures in the EDI components. Set it zero to disable paging. Nonzero values specify the maximum number of occurrences of a given item which can occur before paging occurs.
Page 258 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 259: Notices
Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
Page 260 The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Page 261: Programming Interface Information
These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work, must...
Page 262 WebSphere Partner Gateway Enterprise and Advanced Editions includes software developed by the Eclipse Project (www.eclipse.org) IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 263: Index
52 API calls Connections Disabling managing 34 changing configurations 57 a connection 58 archiving 129 components 54 a digital certificate 53 AS documents, encrypted 158 disabling or deactivating 58 actions 25 AS Viewer 109 © Copyright IBM Corp. 2007, 2008...
Page 264 54 IPV6 82 details 22 partner profiles 41 receivers 22 password policy 19 Encrypted AS documents 158 queue overflow 187 Error event type 102 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 265 Managing (continued) Proxy support, forward 49 Selecting (continued) system configuration data 32 transformation map 58 transformation maps 27 service log, IBM 163 XML formats 24 Source destination, changing 58 Maps SQLCODE Queue overflow 187 managing 27 -1225 162 Queue, stopping documents from 87...
Page 266 179 managing formats 24 VCBaseException 178 WebSphere Application Server shortcut 182 Typographic conventions 2 Updating maps 27 Uploading CPA 36 transports 46 URI, restriction 168 Using the Destination Queue 85 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide...
Page 268 Printed in USA...

This manual is also suitable for:

Websphere partner gateway

IBM E02HRLL-G - WebSphere Partner Gateway Express Administration Manual

Chapter 1. About this Book

Chapter 2. Managing the Websphere Partner Gateway Component Applications

Chapter 3. Basic Community Console Tasks

Chapter 4. Hub Administration Tasks

Chapter 5. Account Administration Tasks

Chapter 6. Administering Partner Migration

Chapter 7. LDAP Support for Logon Authentication

Chapter 8. Support for Ipv6

Chapter 9. Managing the Destination Queue

Chapter 10. Analyzing Document Flows

Chapter 11. Viewing Events and Documents

Chapter 12. Simulating Production Traffic

Chapter 13. Archiving

Chapter 14. Using Logging and Tracing Features

Chapter 15. FTP Server Configuration Management

Chapter 16. Relocation and Redeployment of Websphere Partner Gateway

Chapter 17. Troubleshooting

Quick Links

Related Manuals for IBM E02HRLL-G - WebSphere Partner Gateway Express

Summary of Contents for IBM E02HRLL-G - WebSphere Partner Gateway Express