- DL manuals
- IBM
- Software
- E02HRLL-G - WebSphere Partner Gateway Express
- Administration Manual
IBM E02HRLL-G - WebSphere Partner Gateway Express Administration Manual - Contents
Contents
Chapter 1. About this book
. . . . . . 1
Audience
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1
Roles, access levels, and responsibilities .
.
.
.
. 1
Typographic conventions .
.
.
.
.
.
.
.
.
. 2
Related documents .
.
.
.
.
.
.
.
.
.
.
. 3
New in release 6.2
.
.
.
.
.
.
.
.
.
.
.
. 3
Chapter 2. Managing the WebSphere
Partner Gateway component
applications . . . . . . . . . . . . . 5
Managing WebSphere Partner Gateway components
in a simple mode system .
.
.
.
.
.
.
.
.
. 5
Managing WebSphere Partner Gateway components
in a distributed mode system .
.
.
.
.
.
.
.
. 6
The Deployment Manager .
.
.
.
.
.
.
.
.
. 7
Starting and stopping servers from the command
line
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 8
Starting and stopping FTP Management Server
from command line .
.
.
.
.
.
.
.
.
.
. 8
Starting and stopping the components in a simple
distributed mode system .
.
.
.
.
.
.
.
. 9
Starting servers in a simple distributed mode
system .
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9
Stopping servers in a simple distributed mode
system .
.
.
.
.
.
.
.
.
.
.
.
.
.
. 10
Starting and stopping the components in a full
distributed mode system .
.
.
.
.
.
.
.
. 11
Starting servers in a full distributed mode system 11
Stopping servers in a full distributed mode
system .
.
.
.
.
.
.
.
.
.
.
.
.
.
. 12
Chapter 3. Basic Community Console
tasks
. . . . . . . . . . . . . . . 15
Logging in to the Community Console .
.
.
.
. 15
Navigating through the Community Console .
.
. 16
Community Console icons .
.
.
.
.
.
.
.
. 16
Logging off from the Community Console .
.
.
. 18
Chapter 4. Hub administration tasks . . 19
Managing password policy .
.
.
.
.
.
.
.
. 19
Changing database connectivity, database user and
password .
.
.
.
.
.
.
.
.
.
.
.
.
.
. 20
Managing event codes .
.
.
.
.
.
.
.
.
.
. 20
Viewing and editing event codes .
.
.
.
.
. 21
Exporting event code names .
.
.
.
.
.
.
. 21
Specifying events that can be notified
.
.
.
. 22
Document Validation Errors .
.
.
.
.
.
.
.
. 22
Managing receivers .
.
.
.
.
.
.
.
.
.
.
. 22
Viewing and editing receiver details .
.
.
.
. 22
Enabling or disabling receivers .
.
.
.
.
.
. 22
Deleting receivers .
.
.
.
.
.
.
.
.
.
. 23
Localizing HTTP synchronous target time out .
.
. 23
Managing interactions and document definitions .
. 23
Managing XML formats .
.
.
.
.
.
.
.
.
. 24
Large file support .
.
.
.
.
.
.
.
.
.
. 25
Enabling or disabling actions
.
.
.
.
.
.
.
. 25
Managing handlers .
.
.
.
.
.
.
.
.
.
.
. 25
Importing a handler
.
.
.
.
.
.
.
.
.
. 26
Deleting a handler .
.
.
.
.
.
.
.
.
.
. 26
Configuring the content-type attribute in
handlers
.
.
.
.
.
.
.
.
.
.
.
.
.
. 26
Managing maps .
.
.
.
.
.
.
.
.
.
.
.
. 27
Updating validation maps
.
.
.
.
.
.
.
. 27
Viewing validation maps Where used
.
.
.
. 27
Deleting validation maps .
.
.
.
.
.
.
.
. 27
Managing transformation maps.
.
.
.
.
.
. 27
Managing EDI FA maps .
.
.
.
.
.
.
.
. 28
Managing EDI
.
.
.
.
.
.
.
.
.
.
.
.
. 28
Envelope profile .
.
.
.
.
.
.
.
.
.
.
. 28
Enveloper .
.
.
.
.
.
.
.
.
.
.
.
.
. 29
Connection profiles .
.
.
.
.
.
.
.
.
.
. 30
Control number initialization
.
.
.
.
.
.
. 30
Current control numbers .
.
.
.
.
.
.
.
. 31
Managing system configuration data .
.
.
.
. 32
Configuring the alert mail server .
.
.
.
.
.
. 33
Viewing system activity .
.
.
.
.
.
.
.
.
. 33
Managing event delivery .
.
.
.
.
.
.
.
.
. 34
Managing API calls .
.
.
.
.
.
.
.
.
.
.
. 34
Managing Document Manager information .
.
.
. 35
Maximum hold time .
.
.
.
.
.
.
.
.
. 35
Maximum files-per-poll-interval
.
.
.
.
.
. 35
Supporting ebMS
.
.
.
.
.
.
.
.
.
.
.
. 36
Uploading a CPA to WebSphere Partner Gateway 36
Non-prepopulated attributes.
.
.
.
.
.
.
. 37
Algorithms supported by the ebMS .
.
.
.
. 38
Configuration details for validating Webservices .
. 38
Using non-repudiation logging .
.
.
.
.
.
.
. 39
Using message store
.
.
.
.
.
.
.
.
.
.
. 39
Prerequisite to setup WebSphere Partner Gateway -
WebSphere Transformation Extender Integration
Environment .
.
.
.
.
.
.
.
.
.
.
.
.
. 40
Chapter 5. Account administration
tasks
. . . . . . . . . . . . . . . 41
Managing partner profiles
.
.
.
.
.
.
.
.
. 41
Viewing and editing partner profiles .
.
.
.
. 41
Searching for partners .
.
.
.
.
.
.
.
.
. 41
Deleting partners
.
.
.
.
.
.
.
.
.
.
. 42
Managing destination configurations .
.
.
.
.
. 42
Required information for destination
configuration .
.
.
.
.
.
.
.
.
.
.
.
. 42
Viewing and editing destinations .
.
.
.
.
. 43
Viewing and editing default destination .
.
.
. 45
Viewing destination Where used .
.
.
.
.
. 45
Deleting destination
.
.
.
.
.
.
.
.
.
. 45
Uploading transports .
.
.
.
.
.
.
.
.
. 46
Deleting transports .
.
.
.
.
.
.
.
.
.
. 46
Transport and destination retries .
.
.
.
.
. 46
Forward proxy support .
.
.
.
.
.
.
.
. 49
© Copyright IBM Corp. 2007, 2008
iii
Summary of E02HRLL-G - WebSphere Partner Gateway Express
Page 1
Websphere ® ibm websphere partner gateway enterprise and advanced editions administration guide version 6.2.
Page 2
Note before using this information and the product it supports, read the information in “notices” on page 253. April 2010 this edition applies to version 6.2, release 0, modification 0 of ibm websphere partner gateway enterprise edition (product number 5724-l69) and version 6.2, release 0, modificat...
Page 3: Contents
Contents chapter 1. About this book . . . . . . 1 audience . . . . . . . . . . . . . . . 1 roles, access levels, and responsibilities . . . . . 1 typographic conventions . . . . . . . . . . 2 related documents . . . . . . . . . . . . 3 new in release 6.2 . . . . . . . . . . . . 3 chapter 2. Managing...
Page 4
Managing certificates . . . . . . . . . . . 49 configuring the certpath related properties . . . 51 viewing and editing digital certificates . . . . 52 disabling a digital certificate . . . . . . . 53 changing b2b attribute values . . . . . . . . 53 managing partner connections . . . . . . . . 54 co...
Page 5
Responding to an open document . . . . . 126 removing an open document . . . . . . . 127 chapter 13. Archiving . . . . . . . . 129 archiver configuration . . . . . . . . . . 129 view archiver task. . . . . . . . . . . 129 archiver task modification . . . . . . . . 131 export and import of archiver c...
Page 6
Vcbaseexception in the systemout.Log . . . . . 178 reporting file size for documents greater than 2 gb . . . . . . . . . . . . . . . . 178 ssl handshake fails because no certificate received 178 fixing the hanging threads warning . . . . . . 179 stopping the document manager exception . . . 179 fixi...
Page 7
Chapter 1. About this book this document describes how websphere partner gateway can be maintained to suit the requirements of the business-to-business (b2b) trading community. This guide assumes that you have already performed the necessary hub configuration tasks provided in the websphere partner ...
Page 8
Both hub operator and internal partner if they do not delegate the task of configuring and monitoring the websphere partner gateway system to some internal it group or a third-party company. External partner this is the partner with which the internal partner communicates. There can be multiple part...
Page 9
Table 1. Typographic conventions (continued) convention description text in a blue outline (in pdf files only) an outline around text indicates a cross-reference. Click the outlined text to go to the object of the reference. This convention is the equivalent for pdf files of the “underlined colored ...
Page 10
V ability to run installation verification test (ivt) at the end of websphere partner gateway component installation v ability to export and import complete websphere partner gateway configuration v support for auto-upgrade to minimize manual upgrade effort v console based archiver with scheduler v ...
Page 11: Component Applications
Chapter 2. Managing the websphere partner gateway component applications managing the websphere partner gateway component applications means starting, stopping, and configuring the application servers that host the websphere partner gateway components. These administrative tasks generally involve us...
Page 12
To stop the websphere partner gateway components, run one of the following scripts: note: you do not have to specify a server name. The server name is always server1 when simple mode is used. V unix (r) /bin/bcgstopserver.Sh v windows (r) \bin\bcgstopserver.Bat managing websphere partner gateway com...
Page 13
– the internal messaging can be managed from the deployment manager. V there are two variations on distributed mode called simple distributed mode and full distributed mode. – in simple distributed mode all three websphere partner gateway components are part of the same cluster. This also includes a...
Page 14
Note: this operation may take a few minutes. You can refresh the view periodically to see the status. 6. To start or to stop individual servers: a. In the left pane click application servers b. In the right pane, select the server for the node to start or stop. Note: remember that a node represents ...
Page 15
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 sy...
Page 16
Starting the servers when the deployment manager is unavailable about this task if the deployment manager is unavailable for use, you can start the messaging bcgmas and the bcgserver servers manually with the following steps: 1. Confirm that the node agents are running for each node with the bcgmas ...
Page 17
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 yo...
Page 18
Starting individual servers on each computer about this task 1. Select the messaging bcgmas server to start and click start . Note: wait until at least one of the servers has started before starting the websphere partner gateway component servers. 2. Repeat the previous step until you have started a...
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 s...
Page 20
14 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 21
Chapter 3. Basic community console tasks the tasks described in this guide are performed using the websphere partner gateway community console. The community console is a web application providing a secure access point accessible through a web browser. Topics covered in this chapter include: v “ log...
Page 22
6. The first time you log in, the system prompts you to create a new password. Type a new password, then type it again in the verify field. 7. Click save . Navigating through the community console the community console consists of various menus used to configure websphere partner gateway. The follow...
Page 23
Table 2. Community console icons (continued) icon icon name edit rosettanet attribute values expand export information export report hide search criteria modify no data contained open calendar out of sequence pause print required input role; click to create role start stop submitted synchronous data...
Page 24
Table 2. Community console icons (continued) icon icon name where used 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. 18 ibm websphere p...
Page 25
Chapter 4. Hub administration tasks this chapter describes the tasks that only a hub administrator can perform. These tasks are: v “managing password policy” v “changing database connectivity, database user and password” on page 20 v “managing event codes” on page 20 v “managing receivers” on page 2...
Page 26
Recommended that special characters remain off when passwords are composed of international characters. Non-english-language character sets might not contain the required three out of four character types. The special characters supported by the system are as follows: ’#’, ’@’, ’$’, ’&’, ’+’. V name...
Page 27
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. On the event codes window, click...
Page 28
Specifying events that can be notified about this task an event is logged for important activities or information within websphere partner gateway. There are some pre-defined events with specific event codes. To view the event codes, navigate to hub admin > hub configuration > event codes . When an ...
Page 29
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. There is no warnin...
Page 30
6. To disable an interaction, click the disabled default definition icon next to the interaction. Click ok to confirm. Websphere partner gateway replaces the delete icon with the enabled default definition icon. This indicates that the interaction is disabled. 7. To edit an interaction, click the ed...
Page 31
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 ca...
Page 32
Importing a handler about this task to import a new handler into your environment, follow these steps: 1. Click hub admin > hub configuration > handlers . 2. On the handlerslist window, click import . 3. For file , enter the name of an xml file that represents the handler you want to import, or use ...
Page 33
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 ...
Page 34
2. Click the download map icon to download a transformation map to your local computer. This is useful when you have to update a map. 3. Click the upload map icon to upload an updated map to the system. See the websphere partner gateway hub configuration guide for details on creating a new transform...
Page 35
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 ...
Page 36
Connection profiles you use connection profiles with de-enveloped transactions and with edi interchanges created by the enveloper. For transactions, the connection profile determines how the transaction is processed after it is de-enveloped. For interchanges, the connection profile determines how th...
Page 37
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 numb...
Page 38
All partners, leave the partner name field blank, and click search . To search for a specific partner, type the name in the partner name field, and then click search . V display current status : click to display the control-number status values for the selected partner-pair. 3. Click the edit icon t...
Page 39
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 ver...
Page 40
Managing event delivery about this task with websphere partner gateway, you can choose to publish system-generated events to an application (for example, a monitoring application). You publish these events to a jms queue. From the event publishing properties page, you can view the status of event pu...
Page 41
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 us...
Page 42
3. Click the edit icon to modify the properties. 4. Click save . Supporting ebms websphere partner gateway supports ebxml message service (ebms) mechanism. The ebms defines the message enveloping and header document schema used to transfer ebxml messages in a communications protocol. Ebms is defined...
Page 43
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...
Page 44
Algorithms supported by the ebms there are various algorithms supported by the ebms including: v “digest and signature algorithms” v “xml encryption and smime encryption algorithms” digest and signature algorithms the digest algorithms supported are as follows: v sha1 v sha256 v sha512 v ripemd160 t...
Page 45
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 res...
Page 46
The flexibility to decide which documents are to be persisted in the message store. You can choose not to store an inbound, outbound or both inbound and outbound websphere partner gateway documents in message store. For example, to configure the message store option for an as2 connection between a t...
Page 47
Chapter 5. Account administration tasks this chapter describes the tasks that can be performed by the account admin. These tasks are: v “managing partner profiles” v “managing destination configurations” on page 42 v “managing certificates” on page 49 v “changing b2b attribute values” on page 53 v “...
Page 48
6. Click the edit icon to edit the partner profile. 7. Click save . Deleting partners about this task to delete a partner, follow these steps: 1. Click account admin . 2. Type the partner name or business id in the appropriate field. 3. Click search . The system finds the partners that match your cr...
Page 49
Table 4. Required transport information (continued) required transport information http transport https transport ftp transport ftps transport ftp scripting transport file directory transport jms transport smtp transport validate client ip o o o o validate client ssl cert o note: 1. When the authent...
Page 50
Table 5. Destination parameter descriptions (continued) parameter description description optional description of the destination. Ftps mode select yes or no to control whether a secure connection is used. Destination name name used to identify the destination. Note: destination name is a user-defin...
Page 51
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...
Page 52
3. Click ok in the warning window to confirm deletion. Uploading transports about this task use the following procedure to upload a transport. 1. Click account admin > profiles > destinations . 2. Select manage transport type . 3. Click browse and select the transport. 4. Select whether to commit th...
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 tr...
Page 54
The delivery manager waits for the specified console interval of 20 seconds before starting console gateway retry 2 of 3. A. The http destination sender sends the request, but does not get the response within the connection timeout of 120 seconds (from the connection timeout). B. The delivery manage...
Page 55
In the instance where the connection does not time out but is refused, the preceding scenario is still started but the 120 second connection time out period does not occur since the connection was immediately refused. Forward proxy support for the http and https transports, you can set up forward pr...
Page 56
Digital signatures are calculations based on an electronic document using public-key cryptography. Through this process, the digital signature is tied to the document being signed and to the signer, and cannot be reproduced. With the passage of the federal digital signature bill, digitally signed el...
Page 57
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. Click search to filter partners or subset of partners. Note:...
Page 58
About this task to view and change the java virtual machine configuration for an application server process, use the java virtual machine page of the administrative console or use the websphere application server admin console to change the configuration through scripting. 1. In the administrative c...
Page 59
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...
Page 60
Managing partner connections partner connections are the mechanism that enables the system to process and route documents between the internal partner and its various partners. Connections contain the information necessary for the proper exchange of each document type including rosettanet trading pa...
Page 61
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 s...
Page 62
– click actions to display the connection details page, where you can view and change the action. For more information, see “selecting a new action” on page 58. – click destinations to display the connection management destinations window, where you can view and change the return destinations or des...
Page 63
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...
Page 64
2. In the scope list, select connection if the attribute changes will apply to all the operation modes associated with the connection, or select an operation mode to which the changes will apply. 3. Click the expand icon and expand the node to the document definition whose attribute values will be c...
Page 65
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 fol...
Page 66
60 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 67
Chapter 6. Administering partner migration the configuration migration utility enables you to selectively export and import websphere partner gateway configuration data. This differs from other data-moving options like database backup and restore because data is selectively extracted when it is expo...
Page 68
When you run the command line script to start the utility, it obtains the system environment variable java_home for this location. If java_home is undefined, then the script will prompt for you to enter the home location for java 5. For example, you can use the copy of java 5 that is installed for u...
Page 69
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 configuratio...
Page 70
Note: the user should either belong to hubadmin group or another group under operator that has the migration module permission enabled. If you issue the script with no arguments, a help prompt is displayed with the required arguments and syntax. The command line invocation syntax for windows is as f...
Page 71
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 o...
Page 72
Table 9. Map of xml element with console (continued) element name in xml console view receiverinfo hub admin > hub configuration > receivers. Each receiver in the list page is represented by receiverinfo. Protocolfamilyinfo hub admin > hub configuration > xml formats. Each document family is represe...
Page 73
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 i...
Page 74
Identifiers such as the id, rowts and time stamp is not exported during export. Only the logical identifiers such as name, description is exported. The configurations like handler types that does not have user defined configuration is not exported. Export option file contains the following options: ...
Page 75
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 ther...
Page 76
V proxy configurations v validation maps v fa maps v partners v system admin properties it is important to note that validation maps and fa maps are independent items when considered individually. But to be useful, they have to be linked to routing object definitions in the system. If the routing ob...
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 dependen...
Page 78
Transform map. Transform map is slightly different as it is used at interaction instead of routing object. But the concept of linking and association is same. Export/import order the generated xml file during export and the input xml file during import should follow the sequence. The order is arrang...
Page 79
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 object...
Page 80
74 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 81
Chapter 7. Ldap support for logon authentication in addition to using websphere partner gateway partner registry for console authentication, websphere partner gateway supports lightweight directory access protocol (ldap) container-based authentication that uses the websphere application server authe...
Page 82
User names and groups groups provide superuser permissions to all users who are members of the hubadmin group. By using groups, more than one user can have hub administrative responsibilities while maintaining password security. Because unique user names are required on an ldap server, user names mu...
Page 83
V resets the hubadmin user id password to the installation default and the database is now used to store passwords. Note: after these scripts are run, any passwords that were configured in ldap must be reentered for each defined user using the websphere partner gateway console. Sample ldap configura...
Page 84
8. Select your ldap server and login using the administrator username and password. 9. Go to server administration > manage server properties > suffices and add a suffix (for example, o=ibm, c=us). 10. Click apply . 11. Go to directory management-add an entry and select organization in structural ob...
Page 85
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 ...
Page 86
80 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 87
Chapter 8. Support for ipv6 internet protocol version 6 (ipv6) is an extension over the current ipv4 protocol. Ipv6 features support for 128 bit address as opposed to the 32 bit address supported by ipv4. Except the change in address format, no other configuration changes are required for ipv6 in th...
Page 88
Hp-ux 11i about this task to enable tunneling on an hp-ux 11i , follow the steps below: 1. Login as the root user. 2. To enable tunneling add the line ipv6_tunnel="1" to the file /etc/rc.Config.D/netconf-ipv6 . 3. Assign the following parameters in the file /etc/rc.Config.D/netconf-ipv6 : ipv6_desti...
Page 89
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. Log in to...
Page 90
84 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 91
Chapter 9. Managing the destination queue the destination queue lets you view documents queued for delivery from any destination in the system. You can also: v view all partner destinations that have documents queued for delivery. V display documents in a queue. V enable or disable destinations. The...
Page 92
2. Input the parameters shown in table 10. Table 10. Destination queue window criteria description partner name to complete this field you can: 1. Specify the partner name. 2. Specify part of the partner name in this field and click show partners . Select the partner from the partner list. 3. Specif...
Page 93
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 ...
Page 94
Note: if the document is already processed by document manager when you click stop process icon, the stop process action from console will not have any impact. Viewing destination details about this task to view information about a particular destination, including a list of documents in the queue, ...
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 sorted by state: v received v in progress v failed v successful you can focus your search using the following criteria: v date v time v type of process (to or from)...
Page 96
Viewing the state of documents in the system the following table describes the different document states. Table 13. Document states state description received the document has been received by the system and is waiting to be processed. In progress the document is currently in one of the following pr...
Page 97
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. 2. Select the ...
Page 98
1. Click tools > document volume report . The system displays the document volume report search window. 2. Select the search criteria from the lists. Table 16. Document volume report search criteria value description start date & time the date and time the process was initiated. End date & time the ...
Page 99
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. Click tools > test partner connection . 2. From the test partn...
Page 100
200 series v 200 - ok successful transmission. This is not an error. V 201 - created the request has been fulfilled and resulted in the creation of a new resource. The newly created resource can be referenced by the urls returned in the url-header field of the response, with the most specific url fo...
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. 404 errors are th...
Page 102
The server does not support the functionality required to fulfill the request. Application method (either get or post) is not implemented. V 502 - bad destination the server received an unusable response from the destination or upstream server it accessed in attempting to fulfill the request. V 503 ...
Page 103
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. Results per page s...
Page 104
2. Select one or more search criteria from the drop-down list: table 20. Edi rejected transaction search criteria value description start date & time the date and time the transaction was initiated. End date & time the date and time the transaction was completed. Source partner the partner that init...
Page 105
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. To ...
Page 106
Table 23. Ftp connections (continued) value description last access time 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. 100 ibm websphere...
Page 107
Chapter 11. Viewing events and documents the following features give you a view into overall system health. They are also troubleshooting tools for event resolution. V “event viewer” v “as viewer” on page 104 v “rosettanet viewer” on page 107 v “document viewer” on page 109 v “ebms viewer” on page 1...
Page 108
Created the event. If the event is related to a document, you can also view the raw document, which identifies the field, value, and reason for the error. Event types websphere partner gateway includes the event types listed in table 24. Table 24. Event types event type description debug debug event...
Page 109
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. Ascend displays either...
Page 110
Problem cause: the connection parse xml failure error is generated due to the following reason: the information from the incoming document is not sufficient for parsing the connection. Explanation: hub should parse the incoming document for getting the attributes required to find the connection for ...
Page 111
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. Select the search crit...
Page 112
Table 26. As viewer search criteria (continued) value description mdn status identify one or more mdn status from the mdn status multi-selection box. Possible options are: all display all results; do not filter on mdn status. Mdn not required display all as transactions where no mdn exists and no md...
Page 113
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 part...
Page 114
Table 28. Rosettanet search criteria (continued) value description end date and time the date and time that the process was completed. Source and target partner identifies the source (initiating) and the target (receiving) partners (internal partner only). Partner indicates whether the search applie...
Page 115
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. Viewing ...
Page 116
2. Select the search criteria from the lists, described in table 30. Table 30. Document viewer search criteria value description start date date the document type process was initiated. Start time time the document type process was initiated. End date date the document type process was completed. En...
Page 117
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 sav...
Page 118
The document processing information is displayed when you view document details, described in table 32. Table 32. Document processing values available through document viewer value description reference id unique identification number assigned to the document by the system. Document id unique identi...
Page 119
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-envel...
Page 120
2. Specify the search criteria to locate the edi interchanges received by websphere partner gateway. 3. Click search . The system displays a list of all the documents that meet your search criteria. 4. Click the view details icon next to the document id for the document that you want to view. 5. Cli...
Page 121
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 f...
Page 122
For details on viewing validation errors in a raw document, see “viewing raw documents” on page 109. Restrictions: the console only displays the first 100kb of a raw document. Validation errors beyond 100kb are not viewable. Stopping a document that is in process about this task click stop process t...
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-repu...
Page 124
To re-send a document: 1. Click viewers > document viewer . The system displays the document viewer search window. 2. Select the search criteria from the lists. 3. Click search . The system displays a list of documents. 4. Select the document or documents that you want to re-send. Note: if you are r...
Page 125
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. Click search . The system displays t...
Page 126
1. Raw documents greater than 100k are truncated. For example, when the signature is located at the bottom of the raw document ( .Rno file), and the size of the raw document exceeds 100k, or the signature is present after the first 100k of the .Rno file, the signature will not be shown in document v...
Page 127
Chapter 12. Simulating production traffic the rosettanet partner simulator (rn ps) can be used before and after the hub community goes live to simulate production traffic (requests, responses, and acknowledgments) between the internal partner and an external partner, which is referred to as the virt...
Page 128
Preparing to test about this task before you start the test, you must perform the following tasks, which may vary by the role that you are simulating, either a request or response from the internal partner, or a request or response from a partner: 1. Review the connections that you have configured t...
Page 129
Table 35. Test scenarios (continued) scenario destination for connection url two-way outbound from an internal partner to an external partner (upload response). Simulating external partner. Vtp_tp vtp_tp two-way inbound from an external partner to an internal partner (upload response). Vtp_owner vtp...
Page 130
3. If it is a self-signed certificate, with the console started, the ca certificate should be uploaded as root and intermediate certificate. If it is a ca signed certificate, the ca certificate should be uploaded as root and intermediate certificate. If the certificate path is to be built till root,...
Page 131
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 simula...
Page 132
3. Click route to start the test process. The document is routed through the system to the appropriate destination based on routing information in the document. V if the document is successfully routed, the system displays a message with links to the rosettanet and document viewers. Use these links ...
Page 133
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 127.
Page 134
128 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 135: Chapter 13. Archiving
Chapter 13. Archiving websphere partner gateway provides an archiver utility for archiving and purging data from the system. Using websphere partner gateway console, you can schedule the archiver task to run automatically without manual intervention. In case of failure, the report and the correspond...
Page 136
2. The following information is displayed: table 37. Archiver configuration section field description general task name name of the archiver task, which is constant and cannot be edited. Description brief description of the task, which is constant and cannot be edited. Last execution time date and t...
Page 137
Table 37. Archiver configuration (continued) section field description purging data retention period in days the number of days of data (specified in 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 in...
Page 138
1. Click hub admin > hub configuration > archiver > archiver configuration . The archiver task is displayed in the view mode. 2. Click edit icon to modify the required parameters. Refer to section table 37 on page 130 for details on the parameters. 3. Save the archiver configuration. The status will...
Page 139
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. Exception scenarios if any error occurs dur...
Page 140
Table 38. Data purging tables (continued) data table activity logging lg_activity_rndtl lg_activity_rnhdr lg_as_dtl lg_as_hdr lg_status_activity lg_b2bprocess_hdr lg_validation lg_activity_dtl lg_activity_endstate bp_process_log lg_delivery_log lg_synch_req_resp lg_activity_event lg_activity lg_stac...
Page 141
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...
Page 142
Restoring archived data of websphere partner gateway v6.1 and earlier about this task the console based restore (from archive) feature in websphere partner gateway v6.2 does not support the backup database archives taken on websphere partner gateway versions prior to v6.1. However, it supports the r...
Page 143
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. Cl...
Page 144
Will be corrected with the next successful purge operation, which needs to have a cutoff date greater than or equal to the one that was specified while stopping the archiver task. Archiver restrictions due to native database support for server side export and/or import, websphere partner gateway arc...
Page 145
Chapter 14. Using logging and tracing features one of the tasks of the websphere partner gateway administrator is to help diagnose problems that arise when documents are being processed. Logging and tracing are the tools that are used in the diagnosis of the problems. The administrator needs to know...
Page 146
The system is configured to write them. Websphere partner gateway applications provide numerous trace messages that can be used to get detailed information about the operation of the system. The trace messages are written to a trace file by themselves, without any of the log messages. The messages l...
Page 147
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. View the details of the server that you want to configure by sel...
Page 148
Configuring tracing in a simple mode system about this task setting up trace for a simple mode system is slightly different than for a distributed mode system. To configure tracing for a simple mode system, use the websphere application server admin console by browsing to http:// server- address >:5...
Page 149
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 applicatio...
Page 150
V trace messages can be written to a memory buffer or to a file. You specify this by choosing one of the trace output radio buttons. – if you select the memory buffer option, you must have a way to take what is in memory and put it into a file so you can see the messages. This is done from the runti...
Page 151
Components. Components are represented by the java package names for the classes that can provide trace information when they are issued by the application server. Note: the java package names for websphere partner gateway classes all begin with the prefix com.Ibm.Bcg so you can locate the individua...
Page 152
Interpreting websphere application server log and trace messages messages and errors from the websphere application server console processes display in the websphere partner gateway logs. Some of these messages might appear to be errors, but they are informational and do not pose a problem for the w...
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 r...
Page 154
148 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 155
Chapter 15. Ftp server configuration management the ftp server configuration properties are stored in websphere partner gateway database. In the console, navigate to system administration > ftp administration . The ftp server configuration is divided into six tabs: v event properties v listener prop...
Page 156
Ftp user management use ftp user management page to manage ftp users. In the console, navigate to account admin > ftp user management . You can perform the following tasks using ftp user management page: v search for ftp users across partners based on the required search criteria. V edit ftp user in...
Page 157: Partner Gateway
Chapter 16. Relocation and redeployment of websphere partner gateway typically, when the ip address or host name of the websphere partner gateway environment changes, the system configuration files needs to be updated in all machines where websphere partner gateway components are installed. Webspher...
Page 158
V /wasnd/profiles//bin/ backupconfig.Bat . Run this command on all machines where websphere partner gateway components are installed. Restoring the configuration details you will be able to restore the configuration details only if you backup the configuration using the steps mentioned in the above ...
Page 159
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 ip/hostname> . This executable is available in the folder /bin . 4. Change the host name of the websphere par...
Page 160
V bootstrap_address v sib_endpoint_address v wc_defaulthost the port number must be any value in the range 0 to 65535. Server type must be any of the following values: v simple v console v router v receiver v simpledistributed relocation and redeployment examples depending on the websphere partner g...
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 /bin . B. In machine b , access the nodes where all websphere partner gateway components are installed. Execute bcgchangenodehostname.Bat\sh with new host n...
Page 162
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 . 4. Change the hostname and port of the database. Ensure that dmgr is up and running before executing the following steps: a. In machine c where websphere par...
Page 163
Chapter 17. Troubleshooting this chapter provides troubleshooting information you can use to identify and resolve problems. See “appendix b - failed events” on page 189 for a list of failed events and their corresponding descriptions. Topics in this chapter include: v “avoiding long processing time ...
Page 164
V “configuring content-types attribute for the fixed workflow handlers” on page 172 v “fixing bcg210013 error” on page 173 v “increasing buffer size to prevent document transmission low performance” on page 174 v “websphere partner gateway hub installer logs error messages” on page 174 v “db passwor...
Page 165
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 exte...
Page 166
2. Select the websphere partner gateway component. 3. Select java and process mgmt > process definition > java virtual machine . 4. Update the values for initial heap size and maximum heap size 5. Restart websphere partner gateway. Document manager workload the number of processing threads used can ...
Page 167
Oracle databases use dynamic changing for collation sequences. In order to use this functionality, websphere partner gateway changes the value of the nls_sort session variable depending on the locale of the current user. Table 42 contains possible user locales, supported websphere partner gateway la...
Page 168
V “sql 0964c transaction log full error on the bcgmas database” sqlcode -444 error if you encounter sqlcode -444 error messages when starting any of the websphere partner gateway components (bcgconsole, bcgreceiver, bcgdocmgr), you should increase the value of the db2 database manager sheapthres par...
Page 169
Logfilsiz=1024 logprimary=13 logsecond=4 the amount of space required for the db2 transaction log is dependent on a number of factors, including the peak rate of documents being processed by websphere partner gateway during a given time period. If you observe that websphere partner gateway seems to ...
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 traf...
Page 171
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 adm...
Page 172
Ftpscripting receiver receives stringindexoutofboundsexception if you receive a stringindexoutofboundsexception while connecting to a pro ftp server, request the partner to remove all blank lines from the welcome message for the ftp server. This ftp server send this message whenever a client connect...
Page 173
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 receive...
Page 174
Reprocessor_home=document manager installation root java_home=$reprocessor_home/java log_reprocessor_classes=$reprocessor_home/classes 2. Run the utility from the command line: ./reprocessdbloggingerrors.Sh or reprocessdbloggingerrors.Bat disabling jit in a websphere application server when webspher...
Page 175
Aspackaging exception:java.Io.Filenotfoundexception: /opt/wbi/ca/common/data/inbound/process/917/fa/xxx (a file or directory in the path name does not exist.) at java.Io.Fileinputstream.Open(native method) at java.Io.Fileinputstream.(fileinputstream.Java(inlined compiled code)) at java.Io.Fileinputs...
Page 176
Fixing the browser error: 500 about this task the browser can show error: 500 and srve0026e: [servlet error]-[action]: java.Lang.Nullpointerexception error in the systemoutlog file. These errors can occur after you: 1. Install websphere partner gateway. 2. Start the console. 3. Log in as hubadmin, a...
Page 177
Note: alternatively, with crl dp you can retrieve crls from crl dp at runtime. Databinding in jms exports/imports within websphere process server when using websphere partner gateway databinding in jms exports/imports within websphere process server, there are certain messages which are providing th...
Page 178
The preceding messages are not errors and can be safely ignored. Fixing test partner connection for ssl connections if the tools/test partner connection fails when a gateway https url is selected, the following error message displays: exception during http post-: null this error can occur when using...
Page 179
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-type...
Page 180
Websphere partner gateway install dir >/wasnd/profiles/ bcgprofile/logs/server1 v in distributed mode installation, the logs are located in the following directories. – hub installation directory >\wasnd\profiles\bcgprofile\logs\ bcgreceiver – hub installation directory >\wasnd\profiles\bcgprofile\l...
Page 181
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 mess...
Page 182
Loading the native library when websphere partner gateway components are started, the logs might show the following message: java.Lang.Unsatisfiedlinkerror: can't find library aixnative (libaixnative.A or .So) in sun.Boot.Library.Path or java.Library.Path depending on which operating system webspher...
Page 183
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...
Page 184
The validity status of the certificate can be found in the websphere partner gateway console. The websphere partner gateway console displays the validity period of certificates on the certificate list page. The validity period is shown in red if the certificate is expired. If the ca certificate is e...
Page 185
Security.Provider.1=com.Ibm.Crypto.Provider.Ibmjce security.Provider.2=com.Ibm.Jsse2.Ibmjsseprovider2 security.Provider.3=com.Ibm.Jsse.Ibmjsseprovider security.Provider.4=com.Ibm.Security.Jgss.Ibmjgssprovider security.Provider.5=com.Ibm.Security.Cert.Ibmcertpath #security.Provider.6=com.Ibm.Crypto.P...
Page 186
Nested exception is: 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.Transactio...
Page 187
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 ...
Page 188
!Entry org.Eclipse.Osgi 2006-08-24 09:04:14.597 !Message error reading configuration: /home/dwhare/websphere61/profiles/dmgr01/configuration/org.Eclipse.Osgi/.Manager/ .Filetablelock (permission denied) !Stack 0 java.Io.Filenotfoundexception: /home/dwhare/websphere61/profiles/dmgr01/configuration/or...
Page 189
Duplicate document delivery during the processing of large volumes of documents, include the following attributes in the websphere variables of each router instance: 1. Bcg.Dm.Checkfilelatency=true 2. Bcg.Dm.Latencywaittime=3000 rendering of tab headings on displays with resolution greater than 1024...
Page 190
Java.Lang.Noclassdeffounderror with reprocessdbloggingerrors.Bat about this task you might encounter java.Lang.Noclassdeffounderror for the following reason. The reprocessdbloggingerrors.Bat file has the path to ws_runtime.Jar, which is present in the directory: \deploytool\itp\plugins\com.Ibm.Websp...
Page 191
– ensure that the architecture of both websphere application server nd and websphere transformation extender matches. For example, on a 32-bit websphere application server nd architecture, the you must have the 32-bit websphere transformation extender installed. – ensure that the websphere transform...
Page 192
As signature failure for interop content type in system administration > common attributes page of the console, the excludedcontenttypesforcanonicalization property is made editable. While performing as2 transactions, this attribute has all the content types that are excluded from canonicalization. ...
Page 193
Appendix a - performance considerations this appendix contains information to assist you in achieving the best performance for your specific environment. Managing queue overflow websphere partner gateway components use a jms queue to asynchronously invoke each other. However, if the arrival rate of ...
Page 194
188 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 195
Appendix b - failed events when a document fails processing, the websphere partner gateway system generates an event. See table 43 for a list of websphere partner gateway failed events and their corresponding descriptions. See table 44 on page 200 for a list of events that can be generated by the ed...
Page 196
Table 43. Failed events (continued) event code event name internal description severity extended description bcg111001 ftp account create error ftp account create failed for partner {0}. Error message: {1} error bcg112002 failed to create directory failed to create directory: {0} error bcg112002 doc...
Page 197
Table 43. Failed events (continued) event code event name internal description severity extended description bcg200015 internal partner provided rosettanet globalusagecode error {0} error this event is generated when the x-aux-production header value is unusable and the configuration property indica...
Page 198
Table 43. Failed events (continued) event code event name internal description severity extended description bcg210013 connection not fully configured connection not fully configured {0} error this event is generated when the connection for the document is not fully configured. Most likely the desti...
Page 199
Table 43. Failed events (continued) event code event name internal description severity extended description bcg210033 message store failed unable to store document plain text error this event is generated when the system is unable to store the document in plain text. Ensure that the system has suff...
Page 200
Table 43. Failed events (continued) event code event name internal description severity extended description bcg210201 pip load during doctype processing failure unable to load pip for a document during doctype processing critical this event is generated when a spec for the pip cannot be found. Shou...
Page 201
Table 43. Failed events (continued) event code event name internal description severity extended description bcg240005 rnpackager delivery header parser failure delivery header parser error: {0} error this event is generated when the system is unable to parse the rosettanet delivery header during un...
Page 202
Table 43. Failed events (continued) event code event name internal description severity extended description bcg240026 certificate is not yet valid certificate is not yet valid: serial number: {0} subject dn: {1} issuer dn: {2} critical bcg240027 certificate is expired certificate is expired: serial...
Page 203
Table 43. Failed events (continued) event code event name internal description severity extended description bcg240070 xml connection parse failure xml connection parse failed error this event is generated when the system is unable to find connection information for an xml file. Bcg240071 flat file ...
Page 204
Table 43. Failed events (continued) event code event name internal description severity extended description bcg240422 as document not found for this mdn {0} error this event is generated when a mdn is received and the system is unable to locate the corresponding document. Bcg240423 input file failu...
Page 205
Table 43. Failed events (continued) event code event name internal description severity extended description bcg250002 delivery scheduler failed an internal error occurred in the delivery scheduler: {0} critical this event is generated when an uncategorized internal error occurred within the deliver...
Page 206
Table 43. Failed events (continued) event code event name internal description severity extended description bcg800005 internal partner process encounters internal error {0} critical this event is generated because of an internal system error while processing the internal partner’s action. Bcg700002...
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 component {0} failed due to errors parsing the input data error bcgedicm0021 database error an error occurred while trying to access...
Page 208
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediem0104 exception occurred when trying to write the file to be sent to a temporary location exception occurred when trying to write the file to be sent to a temporary ...
Page 209
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediem0150 the document passed does not apply to ediackhandler the document passed does not apply to ediackhandler error bcgediem0151 error processing edi ack error proce...
Page 210
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediev0018 envelope segment not found the {0} enveloper or de-enveloper detected an error: the {1} segment was not found error bcgediev0050 translation table lookup faile...
Page 211
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgedift0110 ftp script processing stopped error caused ftp script processing to stop error bcgedift0111 missing file base name no base name provided for retrieved files er...
Page 212
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgedift0203 invalid argument values invalid values for the arguments, any or all may be null error bcgedift0204 control socket not created control socket not created error...
Page 213
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgedift0227 rmd command failed rmd command failed. Reason: {0} error bcgedift0228 mkd command failed mkd command failed. Reason: {0} error bcgedift0229 pasv command failed...
Page 214
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgedisp0005 interchange iterator is null an internal error occurred. The interchange iterator was not set during a previous call error bcgedisp0006 end of input data the s...
Page 215
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediup0038 missing record delimiter end of record reached without record delimiter detected. Record delimiter expected was {0}. Record number was {1}. Record name was {2}...
Page 216
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediup0100 metadata details not found metadata details not found in document. Dictionary{0}, document{1}, syntax{2} error bcgediup0101 metadata control string not found m...
Page 217
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediup0115 empty structure found child elements not found in metadataelement: {0}, element type structure error bcgediup0116 invalid character in data format invalid char...
Page 218
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediut0041 translation table lookup failed translation table lookup entry {0} not found in {1}. The default value returned was {2}. Error bcgediut0061 invalid value for i...
Page 219
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediut0501 input document for transformation is empty the input document for the transformation is empty error bcgediva0001 mandatory data element missing mandatory data ...
Page 220
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediva0010 failed ’paired’ (p) condition failed ’paired’ (p) condition, the standard defines items {0} as paired, but only item {1} was present. Segment name = {2}, segme...
Page 221
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediva0014 failed ’list conditional’ (l) condition failed ’list conditional’ (l) condition, the standard defines items {0} as conditionally paired, but only {1} is presen...
Page 222
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediva0030 data element failed character set validation data element failed character set validation, element name = {0}, segment name = {1}, segment position = {2}, send...
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, element name = {0}, segment name = {1}, segment position = {2}, sending trading partner id/qualifier = {3}/{4}, rece...
Page 224
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediva0054 loop repeats more times than defined by standard loop repeats more times than defined by standard, loop name = {0}, segment position = {1}, sending trading par...
Page 225
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediva0103 transaction set or message trailer count invalid transaction set or message trailer contains an invalid segment count, transaction set or message control numbe...
Page 226
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediva0202 interchange trailer missing or invalid interchange trailer missing or invalid, interchange header control number = {0}, sending trading partner id/qualifier = ...
Page 227
Table 44. Edi event codes and messages (continued) edi event code event name internal description severity extended description bcgediva0992 no message properties found no message properties found error bcgediva0993 metadata not found metadata not found, dictionary = {0}, document type = {1}, syntax...
Page 228
222 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 229
Appendix c - component-specific system attributes configuring attributes as websphere application server nd environment variables on the system administration page of the websphere partner gateway console, there are configuration attributes for specific subcomponents of the websphere partner gateway...
Page 230
Table 45. Default xpath queries (continued) default xpath queries extracted value requestingdocumentidentifier[0]/proprietarydocumentidentifier[0] warrantyclaimconfirmdata[0]/documentreference[0]/ proprietarydocumentidentifier[0] receiveddocumentidentifier[0]/proprietarydocumentidentifier[0] returnp...
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.Cla...
Page 232
Table 47. Client auth (continued) property name description bcg.Ftp.Config.Listeners. Clientauth.Port port of the ftp server. This is for the default listener bcg.Ftp.Config.Listeners. Clientauth.Implicit-ssl ftp will be used instead of ssl bcg.Ftp.Config.Listeners. Clientauth.Ssl.Class class that h...
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 w...
Page 234
Table 51. Database properties property name description hostname host on which the database is installed. User / password user name and password to connect to the database. Port port on which database server is listening. Other properties: table 52. Other properties property name description bcg.Ftp...
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...
Page 236
Table 53. Attributes shared by one or more components (continued) entry default value possible settings description bcg.Vms_inbound_directory.Signal hub install root >/common/ signal_in a file system path signal router inbound directory. Bcg.Bpe_temp_directory.Signal hub install root >/common/ data ...
Page 237
Table 53. Attributes shared by one or more components (continued) entry default value possible settings description bcg.Crldir hub install root >/common/ security/crl/ string with directory path path to directory where certificate revocation list files are stored. Bcg.Checkrevocationstatus true stri...
Page 238
Table 54. Attributes used for processing edi documents entry default value possible settings description tracelevel.All 0 integer between 0 and 2 this particular attribute (all) affects all of the traces. If you want a more focused trace, set the individual trace(s) for the function(s) of interest. ...
Page 239
Table 54. Attributes used for processing edi documents (continued) entry default value possible settings description tracelevel.Xml-serializer 0 integer between 0 and 2 see the description for tracelevel.All . Tracelevel.Rod-serializer 0 integer between 0 and 2 see the description for tracelevel.All...
Page 240
Table 55. Attributes used to configure the console component (continued) entry default value possible setting description bcg.Console.Db.Debuglevel 0 boolean 0 or 1 a binary setting using 0 and 1 to turn database debug trace on (1) or off (0). Bcg.Console.Appserver. Mgmt.Pool.Maxsize 20 integer inte...
Page 242
Table 56. Attributes used to configure jms for the console component (continued) entry default value possible settings description bcg.Jms.Context_url corbaloc:iiop: localhost:58809 url internal setting that affects inter-component communications. This is for ibm use only. Bcg.Jms.Topic.Name jms/bcg...
Page 243
Table 57. Attributes used to configure the rosettanet simulator (continued) entry default value possible setting description bcg.Console.Certs.Vtp.Certificate no default value file name the name of the certificate file (der, binary format) containing a public key that is used by the simulator. The n...
Page 244
Table 58. Attributes used to configure the alert engine (continued) entry default value possible setting description bcg.Alertnotifications. Maxnotificationintervalinmins 30 integer see description of maxnotificationsininterval. Bcg.Alertnotifications. Minnotificationquietintervalinmins 30 integer s...
Page 245
Table 59. Attributes used to configure the as state engine entry default value possible setting description bcg.Asstate.Thread_count 1 integer number of threads used by the as state engine. Bcg.Asstate.Batchsize 1 integer batch size is always set to 1. Changing this attribute will not have any effec...
Page 246
Table 60. Attributes used to configure the business process engine (bpe) (continued) entry default value possible setting description bcg.Duplicate.Dupfield1 to bcg.Duplicate.Dupfield10 x-aux-system- msg-id string the name of a message header whose value provides a unique identity for a message. Thi...
Page 247
Table 63. Attributes used to configure the delivery manager entry default value possible setting description bcg.Delivery.Gatewaydirectory hub install root >/common/gateways string root directory under which the files and subdirectories used to manage destinations (gateways) are located. Bcg.Deliver...
Page 248
Table 63. Attributes used to configure the delivery manager (continued) entry default value possible setting description bcg.Http.Version 1.1 string http version used by the delivery manager bcg.Router.Ipv6.Address no default value string if the computer where the document manager is installed is co...
Page 249
Table 64. Attributes used to configure jms for the document manager component (continued) entry default value possible setting description bcg.Oaq_bpe_in.Signal jms/bcg/queue/ signal_inboundq jndi name internal setting that affects inter-component communications. This is for ibm use only. Bcg.Oaq_bp...
Page 250
Table 64. Attributes used to configure jms for the document manager component (continued) entry default value possible setting description bcg.Jms.Retry_connect_interval 300000 integer internal setting that affects inter-component communications. This is for ibm use only. Bcg.Jms.Connect_pool_elemen...
Page 251
Table 65. Attributes used to configure the document manager packaging process (continued) entry default value possible setting description bcg.Ediint.Retrywaittmms 5000 integer for as outbound messages (with asynchronous mdn), if the mdn is not received, the as engine retries after this number of mi...
Page 252
Table 66. Attributes used to configure rosettanet processing by the document manager (continued) entry default value possible setting description bcg.Rosettanet. Usebuilderprocessinstanceid 1 string value of 1 or 0 that is interpreted as a boolean. If this value equals 1, we expect the builder to pr...
Page 253
Table 67. Attributes used to configure security in the document manager entry default value possible setting description bcg.Rosettanet.Signature. Digestalgorithm sha1 sha1 or md5 the algorithm that is used to generate message digests. Despite its name including rosettanet, this attribute is used fo...
Page 254
Table 68. Attributes used to configure jms for the receiver component (continued) entry default value possible setting description bcg.Jms.Retry_connect_interval 300000 integer internal setting that affects inter-component communications. This is for ibm use only. Bcg.Jms.Connect_pool_elements 2 int...
Page 255
Table 72. Attributes used to configure the summary engine subcomponent of the document manager entry default value possible setting description bcg.Summary.Processinginterval 15 integer time interval in minutes that determines how often event summary processing occurs. Bcg.Summaryeng.Thread_count 1 ...
Page 256
Table 75. Attributes used to configure processing of ebms documents (continued) entry default value possible setting description bcg.Ebxml.Version 2.0 string the ebxml version used to package payloads as ebxml message. Currently, only 2.0 is supported. Bcg.Ebms.Xsd.Schemaname ebxmlschema.Xsd string ...
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 i...
Page 258
252 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 259: Notices
Notices this information was developed for products and services offered in the u.S.A. Ibm may not offer the products, services, or features discussed in this document in other countries. Consult your local ibm representative for information about the products and services currently available in you...
Page 260
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: ibm burling...
Page 261
Platform for which the sample programs are written. 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, mus...
Page 262
Websphere partner gateway enterprise and advanced editions includes software developed by the eclipse project (www.Eclipse.Org) 256 ibm websphere partner gateway enterprise and advanced editions: administration guide.
Page 263: Index
Index a account admin activities 41 adding partners to the exclusion list 59 b2b attribute, changing 53 changing connection configurations 57 changing partner attribute values 57 changing the destination or return destination 58 connection components 54 connection duplication 55 deleting partners 42...
Page 264
Disabling (continued) receivers 22 document details, document viewer 111 processing values, document viewer 112 document analysis description 89 search criteria 90 viewing documents 90 viewing process and event details 91 document definition configuring 23 document manager stopping 179 document mana...
Page 265
Managing (continued) system configuration data 32 transformation maps 27 xml formats 24 maps managing 27 managing edi 28 managing fa 28 managing transformation 27 updating 27 messages, informational 163 n navigating through community console 16 new action, selecting 58 non-repudiation logging 39 o o...
Page 266
Troubleshooting (continued) creating on another drive 169 crl dp 175 databinding in jms 171 db password required 175 db2 virtual memory 161 define custom transport type 168 document volume report 175 documents not processed 183 documents routed twice 165 downloading crl 170 duplicate document delive...
Page 268
Printed in usa.