/
OTS - Setup MTOM FileNet Connection

OTS - Setup MTOM FileNet Connection

Output Transformation Server - Is there a way to setup MTOM FileNet connection



Applies to

  • Output Transformation Server 5.0

 

Summary

In Output Transformation Server, is there a way to setup MTOM FileNet connection

 

Resolution

Yes, MTOM FileNet connection has been used by OTS (in the past). The Content Engine server determines the content transfer method based on the endpoint used.

  1. To access MTOM use the following format:

http://<hostname>:<port>/wsi/FNCEWS40MTOM/wsdl where:
<hostname> is the name of the Content Engine host machine
<port> is the port number assigned to the Content Engine application server

For example: http://localhost:9080/wsi/FNCEWS40MTOM/wsdl

  1. To access SOAP use the following format:

http://<hostname>:<port>/wsi/FNCEWS40SOAP/wsdl where:
<hostname> is the name of the Content Engine host machine
<port> is the port number assigned to the Content Engine application server

For example: http://localhost:9080/wsi/FNCEWS40SOAP/wsdl

Related content

OTS - Error - Schedule Jobs missing in OTS Manager/Apache Tomcat
OTS - Error - Schedule Jobs missing in OTS Manager/Apache Tomcat
More like this
Kofax - What Ports do the Kofax Capture Server and Capture Clients Require?
Kofax - What Ports do the Kofax Capture Server and Capture Clients Require?
More like this
OTS - OutPut Transformation Server - Error - Unable to load XenosEngine.config
OTS - OutPut Transformation Server - Error - Unable to load XenosEngine.config
More like this
Teleform - Remote Capture Station Not Synchronizing Job Settings
Teleform - Remote Capture Station Not Synchronizing Job Settings
More like this
ECMToolBox AIM- Secure Connections
ECMToolBox AIM- Secure Connections
More like this
ApplicationXtender - Ports for ApplicationXtender and Related Modules
ApplicationXtender - Ports for ApplicationXtender and Related Modules
More like this

Copyright © CASO Document Management

All product names, logos, brands, and trademarks featured or referred to on this page are the property of their respective trademark holders. These trademark holders are not affiliated with, nor do they sponsor or endorse this website or the products/services offered unless explicitly stated otherwise.