ibm mobilefirst - Worklight SAP Netweaver GateWay Adapter - Client ID -


currently using worklight sap netweaver gateway adapter connect our development environment of sap. our customer has configured 2 client environments 101 , 211. default 101.

when creating connection based on following adapter configuration...

<?xml version="1.0" encoding="utf-8"?> <wl:adapter xmlns:wl="http://www.worklight.com/integration" xmlns:nwgateway="http://www.worklight.com/integration/nwgateway" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" name="sapadapter1">     <displayname>sapadapter1</displayname>     <description></description>     <connectivity>         <connectionpolicy xsi:type="nwgateway:nwgatewayhttpconnectionpolicytype">             <protocol>http</protocol>             <domain>10.9.5.27</domain>             <port>8000</port>             <servicerooturl>/sap/opu/odata/sap/services_x_y_z/</servicerooturl>             <authentication>                 <basic/>                 <serveridentity>                     <client>211</client>                     <username>xyz</username>                     <password>123</password>                 </serveridentity>             </authentication>         </connectionpolicy>         <loadconstraints maxconcurrentconnectionspernode="10"/>     </connectivity>     <procedure name="getshipments"/> </wl:adapter> 

we assume connect client 211, apparently connected 101.

how client-id handled worklight sap nwg adapter?

this has been identified defect in product.
there no available workaround.

to receive ifix containing fix defect, need open pmr (support ticket).
please mention question apar #pi31148 in query reference.


Comments

Popular posts from this blog

ruby on rails - RuntimeError: Circular dependency detected while autoloading constant - ActiveAdmin.register Role -

c++ - OpenMP unpredictable overhead -

javascript - Wordpress slider, not displayed 100% width -