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.
This applies the EDI handler and the document gets processed as EDI. These
content types value should be separated by a comma.
The Content-Types attribute is used for a particular set of handlers. These handlers
are
v
BinaryChannelParseHandler
v
XMLRouterBizHandler
v
EDIRouterBizProcessHandler
v
cXMLChannelParseHandler
These handlers are populated with a default list of content types. To modify the
content types, perform 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 the handler and click
Configure
.
5.
Edit the Content-Types attribute by adding the new content type. Ensure that
the content-type values are separated by a comma.
Note:
It is recommended not to change these content-type values unless advised.
Fixing BCG210013 error
About this task
Unable to receive inbound document because of the following error:
BCG210013 - Connection Not Fully Configured
If all other configurations appear to be correct, the most common cause of this is
an incorrect receiver specification.
1.
Check that there are no spaces in front of the receiver URL definitions.
2.
Try to narrow down the problem trying to send a test EDI message using other
business IDs available for the partners. Try to see if this is a business ID
specific problem.
3.
If the previous step fails, then take a debug trace of the error scenario as
follows:
a.
Shut down WebSphere Partner Gateway.
b.
Change the debug setting for the receiver and router to FINEST for
WebSphere Partner Gateways using the following command:
"*=info:com.ibm.bcg.*=finest"
c.
Delete (or backup to a different folder), the current logs in these directories:
v
In simple mode installation, the logs are located in the following
directory:
Chapter 17. Troubleshooting
173
Summary of Contents for E02HRLL-G - WebSphere Partner Gateway Express
Page 20: ...14 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 66: ...60 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 80: ...74 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 86: ...80 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 90: ...84 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 134: ...128 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 154: ...148 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 194: ...188 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 228: ...222 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 258: ...252 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide ...
Page 267: ......
Page 268: ... Printed in USA ...