I'm aware that OTM 6.3.5 does not support Python, but this is why I come here in hope.
Out current production set-up is OTM 6.1.2 using Python to send OrderRelease (as XML file) to OTM. That works fine.
After the upgrade to 6.3.5, the same Python set up doesn't work anymore. We can take the XML file Python generated and upload manually, and OTM would process successfully. However, when Python tried to post it, OTM would acknowledge with:
<?xml version="1.0" encoding="UTF-8"?><TransmissionAck xmlns="http://xmlns.oracle.com/apps/otm"><E...></Transmissio
nHeader></EchoedTransmissionHeader><TransmissionAckStatus>RE JECTED</TransmissionAckStatus><TransmissionAckReason>MISSI NG_GLUSERGID_OR_GLPASSWORD</Transmiss
ionAckReason><TransmissionText><![CDATA[]]></TransmissionText><!-- SenderHostName: 127.0.0.1 --></TransmissionAck>
We have tried many things (including making sure user id and password are correct of course) but still getting the same error.
When posting to OTM, this is the Python segment of code used:
xmlInputDir = config.get("folders","outputFolder")
OTMPostURL = config.get("otm","post_url")
xmlFile = open(os.path.join(xmlInputDir,f),"r")
xmlContent = xmlFile.read()
xmlFile.close()
logger.info("About to post [" + f + "]")
request = urllib2.Request(OTMPostURL,xmlContent)
response = urllib2.urlopen(request)
responseXML = response.read()
Where xmlInputDir, OTMPostURL have been defined in a config.ini file as followed:
[folders]
outputFolder=/export/home/otmeai2/data/orderRelease/out
[otm]
post_url=http://10.149.12.219:7181/GC3/glog.integration.servlet.WMServlet
For some reason I could not upload the entire XML message, so I just put the header here, where the user id and password are defined.
<TransmissionHeader>
<UserName>NCI.INTEGRATION</UserName>
<Password>CHANGEME</Password>
<AckSpec>
<ComMethodGid>
<Gid>
<DomainName>PUBLIC</DomainName>
<Xid>EMAIL</Xid>
</Gid>
</ComMethodGid>
<EmailAddress>tdanley@ncigroup.com</EmailAddress>
<AckOption>ERROR</AckOption>
</AckSpec>
</TransmissionHeader>
Hopefully someone had come across similar error.
Thanks
P.S. Part of the XML acknowledgement from OTM is truncated after posting. It might be a bug with this site, but the original is not like that.
Out current production set-up is OTM 6.1.2 using Python to send OrderRelease (as XML file) to OTM. That works fine.
After the upgrade to 6.3.5, the same Python set up doesn't work anymore. We can take the XML file Python generated and upload manually, and OTM would process successfully. However, when Python tried to post it, OTM would acknowledge with:
<?xml version="1.0" encoding="UTF-8"?><TransmissionAck xmlns="http://xmlns.oracle.com/apps/otm"><E...></Transmissio
nHeader></EchoedTransmissionHeader><TransmissionAckStatus>RE JECTED</TransmissionAckStatus><TransmissionAckReason>MISSI NG_GLUSERGID_OR_GLPASSWORD</Transmiss
ionAckReason><TransmissionText><![CDATA[]]></TransmissionText><!-- SenderHostName: 127.0.0.1 --></TransmissionAck>
We have tried many things (including making sure user id and password are correct of course) but still getting the same error.
When posting to OTM, this is the Python segment of code used:
xmlInputDir = config.get("folders","outputFolder")
OTMPostURL = config.get("otm","post_url")
xmlFile = open(os.path.join(xmlInputDir,f),"r")
xmlContent = xmlFile.read()
xmlFile.close()
logger.info("About to post [" + f + "]")
request = urllib2.Request(OTMPostURL,xmlContent)
response = urllib2.urlopen(request)
responseXML = response.read()
Where xmlInputDir, OTMPostURL have been defined in a config.ini file as followed:
[folders]
outputFolder=/export/home/otmeai2/data/orderRelease/out
[otm]
post_url=http://10.149.12.219:7181/GC3/glog.integration.servlet.WMServlet
For some reason I could not upload the entire XML message, so I just put the header here, where the user id and password are defined.
<TransmissionHeader>
<UserName>NCI.INTEGRATION</UserName>
<Password>CHANGEME</Password>
<AckSpec>
<ComMethodGid>
<Gid>
<DomainName>PUBLIC</DomainName>
<Xid>EMAIL</Xid>
</Gid>
</ComMethodGid>
<EmailAddress>tdanley@ncigroup.com</EmailAddress>
<AckOption>ERROR</AckOption>
</AckSpec>
</TransmissionHeader>
Hopefully someone had come across similar error.
Thanks
P.S. Part of the XML acknowledgement from OTM is truncated after posting. It might be a bug with this site, but the original is not like that.