Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8430

Re: B1iF RESTful To gocanvas.com

$
0
0

The message I get is only in the debug.  I cannot successfuly activate the package because it says there is no suitable system in the SLD available.  I am not sure if this is becuase I have a void on the inboud and outbound. So currently I juse use the test in the processing step area to trial out the atom using the inbound message from atom2.xsl. 

 

When I try to view the degub message now I get a RUN could not be triggered error so here is the atom2.xsl I send to the http call I reference this in the http call as the reference for connectivity parameter

 

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet xmlns:b1e="urn:com.sap.b1i.sim:b1event" xmlns:b1ie="urn:com.sap.b1i.sim:b1ievent" xmlns:b1im="urn:com.sap.b1i.sim:b1imessage" xmlns:bfa="urn:com.sap.b1i.bizprocessor:bizatoms" xmlns:jdbc="urn:com.sap.b1i.adapter:jdbcadapter" xmlns:rfc="urn:sap-com:document:sap:rfc:functions" xmlns:sim="urn:com.sap.b1i.sim:entity" xmlns:utils2="com.sap.b1i.bpc_tools.Utilities" xmlns:vpf="urn:com.sap.b1i.vplatform:entity" xmlns:xci="urn:com.sap.b1i.xcellerator:intdoc" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" bfa:force="" vpf:force="" jdbc:force="" rfc:force="" b1ie:force="" b1e:force="" xci:force="" sim:force="" utils2:force="" b1im:force="">

  <xsl:output method="xml" encoding="UTF-8" indent="yes"/>

  <xsl:param name="atom"/>

  <xsl:param name="sessionid"/>

  <xsl:variable name="msg" select="/vpf:Msg/vpf:Body/vpf:Payload[./@Role=&apos;S&apos;]"/>

  <xsl:variable name="vpSender" select="/vpf:Msg/vpf:Header/vpf:Sender/@Id"/>

  <xsl:variable name="vpObject" select="/vpf:Msg/vpf:Header/vpf:Sender/@ObjId"/>

  <xsl:variable name="vpReceiver" select="/vpf:Msg/vpf:Header/vpf:ReceiverList/vpf:Receiver[./@handover=&apos;P&apos;]/@Id"/>

  <xsl:template match="/">

  <Msg xmlns="urn:com.sap.b1i.vplatform:entity">

  <xsl:copy-of select="/vpf:Msg/@*"/>

  <xsl:copy-of select="/vpf:Msg/vpf:Header"/>

  <Body>

  <xsl:copy-of select="/vpf:Msg/vpf:Body/*"/>

  <Payload Role="X" id="{$atom}">

  <xsl:call-template name="transform"/>

  </Payload>

  </Body>

  </Msg>

  </xsl:template>

  <xsl:template name="transform">

  <call xmlns="">

  <query id="identifier" value="value"/>

  <!--optional - define your own query parameters - multiple elements allowed-->

  <connect>

  <!--the connect section is optional - you can also define a reference to the sld-->

  <destProtocol>https</destProtocol>

  <destHost>gocanvas.com</destHost>

  <destPort>443</destPort>

  <destPath>apiv2/</destPath>

  <query>reference_datas</query>

  <proxyHost/>

  <proxyPort/>

  <method>POST</method>

  <authentification>none</authentification>

  <user/>

  <password/>

  <user2query/>

  <password2query/>

  <trustStoreURI/>

  <keyStoreURI/>

  </connect>

  <dtd>

  <!--optional - document type definition-->

  </dtd>

  <pltype>

  <!--optional - default is xml-->

  </pltype>

  <payload>

  </payload>

  <htta>

  <par id="httpheader.???" value="">

  <!--optional - you can specify here your own http header definitions - multiple elements allowed-->

  </par>

  <par id="htta.returnpltypeforce" value="">

  <!--optional-->

  </par>

  <par id="htta.returnpltypedefault" value="">

  <!--optional-->

  </par>

  </htta>

  </call>

  </xsl:template>

</xsl:stylesheet>

 

 

 

To give you an update I successfully created a H.any system SLD and it reports that it connected successfully to go canvas.

 

To do this I had to follow this forum thread:

 

http://scn.sap.com/thread/3523766

 

In which I did not use the keytool to add the certificate to the keystore.  I then removed all the certificates I had added to the keystore using the keytool.

 

So once I done the above I could see the certificates from the local tomcat https B1iF server and  I also added the https ssl cert from the https://gocanvas.com:443  website.  Now it appears it does connect in the SLD!

 

So I have read through many examples and it would appear everyone uses the atom http call instead to pass the parameters, for me personally I would like to know how to reference the SLD in the connect area instead as then I only need to change one parameter going forward if anything changes.

 

So now if I can work out:

 

-whats wrong with the atom2.xsl  I think it can successfully connect to the gocanvas in the atom as it works in an SLD.

 

-Why I cannot choose a sender and receiver system as it complains a system doesnt exists thats suitable.

 

Thank you very much


Viewing all articles
Browse latest Browse all 8430

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>