10 Replies Latest reply on Jun 10, 2018 5:39 PM by Carl Wilson

    AR AO web service  ERROR (9130): Error encountered while executing

      I am tring
      to consume a webservice expose by a custom remedy form using the AO SOAP method
      two.


      For testing
      from the  AO dev studio

      by providing
      the SOAPAdapter name,SOAPheader and SOAP body


      I am able
      to create a new record on the remedy form.

       

      But when I integrate
      this from the ARS Dev Studio ,filter setfield , Choosing the  BAO
      and selecting the

      SOAP Method
      two


      provided
      all the above information   it is giving when i try to submit a record from the form.

       

      ERROR
      (9130): Error encountered while executing a Web Service; ; nested exception is:

                      javax.net.ssl.SSLHandshakeException:
      sun.security.validator.ValidatorException: PKIX path building failed:
      sun.security.provider.certpath.SunCertPathBuilderException: unable to find
      valid certification path to requested target

       

       

      I have attached java plugin log(error ) and the AO PRocess log(it is working fine )

       

      Please comment on it.

        • 1. Re: AR AO web service  ERROR (9130): Error encountered while executing
          Carl Wilson

          Hi,

          the error you are seeing is related to SSL handshaking, which tends to indicate that your BAO CDP (ORCA Web Service) is configured for "https".

          If so, you need to install the associated certificates to the Java store for your Developer Studio.  You can obtain the relevant information from this thread:

           

          Unable to Configure Atrium Orchestrator Configu... | BMC Communities

           

          Cheers

          Carl

           

          http://www.missingpiecessoftware.com/

          • 2. Re: AR AO web service  ERROR (9130): Error encountered while executing

            Hi Carl,

            Thanks for your replay,

             

            i am not facing any issues in the devlopment of the filter  nor in AO Dev studio.

             

            i am facing issues when i am calling the webservice( i mean  when i submit a record on submit event i am facing this issue.

             

            Please comment

            • 3. Re: Re: AR AO web service  ERROR (9130): Error encountered while executing
              Carl Wilson

              Hi,

              here is your error log:

               

              2013-12-02 08:06:39,147 ERROR [pool-4-thread-3] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <ARSYS.ARF.WEBSERVICE>java.lang.NumberFormatException: For input string: ""

              2013-12-02 08:06:39,148 ERROR [pool-4-thread-3] com.bmc.arsys.pluginsvr.plugins.ARFilterAPIPluginRepository (?:?) - ARFilterApiCall FAILs in plugin: ARSYS.ARF.WEBSERVICE

              ERROR (9130): Error encountered while executing a Web Service; ; nested exception is:

              java.lang.NumberFormatException: For input string: ""

              at com.bmc.arsys.ws.plugin.WSPlugin.ThrowException(Unknown Source)

              at com.bmc.arsys.ws.plugin.WSPlugin.filterAPICall(Unknown Source)

              at com.bmc.arsys.pluginsvr.plugins.ARFilterAPIPluginRepository.ARFilterApiCall(Unknown Source)

              at com.bmc.arsys.pluginsvr.a.ArEsFilterApi_5(Unknown Source)

              at com.bmc.arsys.pluginsvr.a.ArEsFilterApi_4(Unknown Source)

              at com.bmc.arsys.arrpc.ARPluginServerDispatcher.dispatchOncRpcCall(Unknown Source)

              at com.bmc.arsys.arrpc.nio.ArRpcCallHandler.dispatchCall(Unknown Source)

              at com.bmc.arsys.arrpc.nio.ArRpcCallHandler.if(Unknown Source)

              at com.bmc.arsys.arrpc.nio.ArRpcCallHandler.processRpcCall(Unknown Source)

              at com.bmc.arsys.arrpc.nio.ArRpcCallHandler$Processor.run(Unknown Source)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

              at java.lang.Thread.run(Thread.java:744)

              2013-12-02 08:27:03,012 ERROR [pool-4-thread-2] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <ARSYS.ARF.WEBSERVICE>javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

              2013-12-02 08:27:03,012 ERROR [pool-4-thread-2] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <ARSYS.ARF.WEBSERVICE>WS timeout setting  = 40 sec

              2013-12-02 08:27:03,013 ERROR [pool-4-thread-2] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <ARSYS.ARF.WEBSERVICE>AxisFault during  = 220 millisec

              2013-12-02 08:27:03,013 ERROR [pool-4-thread-2] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <ARSYS.ARF.WEBSERVICE>soapService = Orchestrator

              2013-12-02 08:27:03,013 ERROR [pool-4-thread-2] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <ARSYS.ARF.WEBSERVICE>soapMethod = executeProcess

              2013-12-02 08:27:03,013 ERROR [pool-4-thread-2] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <ARSYS.ARF.WEBSERVICE>soapURL = https://bld05574003.iuser.iroot.adidom.com:38080/baocdp/orca

              2013-12-02 08:27:03,013 ERROR [pool-4-thread-2] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <ARSYS.ARF.WEBSERVICE>soapNamespace = http://bmc.com/ao/xsd/2008/09/soa

              2013-12-02 08:27:03,013 ERROR [pool-4-thread-2] com.bmc.arsys.pluginsvr.plugins.ARPluginContext (?:?) - <ARSYS.ARF.WEBSERVICE>soapInputDocument = <?xml version="1.0" encoding="utf-8"?>


              From this you can see 2 errors:

               

              1. Number Format Exception
              2. "https" used in the soapURL

               

              I would do the following as you are required to pass a large amount of parameters into the "Make SOAP Request Method Two" process (which you are not doing):

               

              • Simplify the design to validate the connections - i.e. wrap the "Make SOAP Request Method Two" process into your own and set all the values within your custom Process as opposed to passing them in from ARS.
              • Create any input parameters as required to be passed on to the "Make SOAP Request Method Two" in your custom Process

               

              Your call to BAO is as follows:

               

              <ns0:processName>:AutoPilot-AD-Utilities:Web_Service:Make SOAP Request Method Two</ns0:processName>
              <ns0:parameters>
                <ns0:Input>
                 <ns0:Parameter>
                  <ns0:Name required="true">adapter name</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text>SOAPAdapter</ns0:Text>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">allow unsigned certificate</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">chunked encoding</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">connection name</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">http request headers</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">install certificate</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">pass phrase</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">password</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">soap action</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">soap body content</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text>&lt;urn:xml-fragment xmlns:urn=&quot;urn:AKCreate&quot;&gt;
                          &lt;urn:New_Create_Operation_0&gt;
              &lt;urn:Submitter__c&gt;Akram&lt;/urn:Submitter__c&gt;
                          &lt;!--Optional:--&gt;
                          &lt;urn:Assigned_To__c&gt;Akram&lt;/urn:Assigned_To__c&gt;

                          &lt;urn:Status__c&gt;New&lt;/urn:Status__c&gt;
                          &lt;urn:Short_Description__c&gt;Akram&lt;/urn:Short_Description__c&gt;
              &lt;/urn:New_Create_Operation_0&gt;
                &lt;/urn:xml-fragment&gt;</ns0:Text>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">soap header content</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text>&lt;urn:AuthenticationInfo xmlns:urn=&quot;urn:AKCreate&quot;&gt;
                          &lt;urn:userName&gt;appadmin&lt;/urn:userName&gt;
                          &lt;urn:password /&gt;
                          &lt;!--Optional:--&gt;
                          &lt;urn:authentication /&gt;
                          &lt;!--Optional:--&gt;
                          &lt;urn:locale /&gt;
                          &lt;!--Optional:--&gt;
                          &lt;urn:timeZone /&gt;
                        &lt;/urn:AuthenticationInfo&gt;</ns0:Text>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">soap url</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text>http://10.52.8.47:8080/arsys/services/ARService?server=10.52.8.27&webService=AKCreate</ns0:Text>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">soap version</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">terminate on exit</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">use ssl certificate</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                 <ns0:Parameter>
                  <ns0:Name required="true">username</ns0:Name>
                  <ns0:Value ns0:type="xs:string">
                   <ns0:Text/>
                  </ns0:Value>
                 </ns0:Parameter>
                </ns0:Input>
                <ns0:Output ns0:type="xs:string"/>
              </ns0:parameters>

               

              You have not supplied values  (marked in Red) that are indicated as "Required" - therefore you are receiving the first error.

              Correct the first issue by either supplying the values in your ARS Filter or using a custom Process "wrapper", then address the second issue once these have been corrected.  It maybe masked by the first issue - ARS Web Services throw a number of errors up the the generic "9130" error number.

               

              Cheers

              Carl

               

              http://www.missingpiecessoftware.com/

              1 of 1 people found this helpful
              • 4. Re: Re: AR AO web service  ERROR (9130): Error encountered while executing

                Hi Carl,

                 

                i was working on importing the SSL certificate we genrated the certificate and added it to the ARserver and AO CDP and AO DEV studio.

                 

                 

                but the outcome is now i am getting the below on my browser

                 

                 

                error on

                 

                BMCSSG1757E: Integration with Atrium SSO is failing.
                Please contact the product's support team for help with resolving this
                integration problem (BMCSSG1508E: Atrium SSO server is currently not
                available.).

                • 5. Re: Re: AR AO web service  ERROR (9130): Error encountered while executing
                  Carl Wilson

                  Hi,

                  your issue was not with AO (only ARS), so I am not sure why you then changed anything in this environment when it was working correctly.

                  The issue is that you are using Atrium SSO, therefore I would assume you are using version 7.7.x which is installed using "https" (required by Atrium SSO)?  The certificates for the AO environment would have already been in place when you did the installation (as this is feature of this version) and therefore there is no changes required on this.

                   

                  I cannot help you with the above error - Atrium SSO is a huge black hole when it comes to troubleshooting.

                   

                  I would reverse out your changes to AO and address the original problem - which is ARS > BAO and not the BAO environment.  ARS (Plugin) needs the certificate to be able to connect to Atrium SSO via SSL which is now the Repository and the Access Manager (BAO redirects to the AM then the CDP - both of which are using "https").

                   

                  Cheers

                  Carl

                   

                  http://www.missingpiecessoftware.com/

                  • 6. Re: Re: AR AO web service  ERROR (9130): Error encountered while executing


                    Hi Mark,

                    Thanks for the update ,

                     

                    this is a dev box.i can try

                    can you give me some input how to remove  the ceritificate

                     

                     

                    becoz this issues just come after the addition of the new certificate.

                     

                    can we remeove the cerificate so that the system is on its privous state?

                     

                     

                     

                    Thanks for all your support.

                     

                     

                    Regards,

                    MohammedAkram Shaikh

                    • 7. Re: Re: AR AO web service  ERROR (9130): Error encountered while executing

                      Hi Carl

                       

                      BMCSSG1757E: issue got resolved .

                       

                      just restarted the AO Conteent,CDP

                       

                       

                      Thanks for all your support.

                       

                       

                       

                      • 8. Re: AR AO web service  ERROR (9130): Error encountered while executing


                        Hi carl,

                        we have resolved the ssl issues.

                         

                        now i am fasing new isseu :Summary: Must provide soap-body key in absence of soap-message key

                         

                        in summery  i am providing the

                         


                                  <urn:xml-fragment xmlns:urn="urn:AKCreate">
                                    <urn:New_Create_Operation_0>
                        <urn:Submitter__c>Akram</urn:Submitter__c>
                                    <!--Optional:-->
                                    <urn:Assigned_To__c>Akram</urn:Assigned_To__c>

                                    <urn:Status__c>1</urn:Status__c>
                                    <urn:Short_Description__c>Akram</urn:Short_Description__c>
                        </urn:New_Create_Operation_0>
                          </urn:xml-fragment>

                         

                        Please comment on this.

                         

                        Regards

                        mohammedAkram shaikh

                        • 9. Re: AR AO web service  ERROR (9130): Error encountered while executing
                          Artur Tkaczyk

                          Hi Carl

                           

                          Can you tell me where i can find such call in logs?

                          Is it Remedy or AO logs?

                           

                          Cheers

                          Artur

                          • 10. Re: AR AO web service  ERROR (9130): Error encountered while executing
                            Carl Wilson

                            Hi Artur,

                            Is the call failing from AR to AO?

                            If so, then the plugin log in ARS is where to look.

                             

                            A couple of thing to note when using ARS <> AO via the inbuilt ARS AO Configuration:

                             

                            • ARS uses the plugin server (WS plugin) to make the call to AO via WS, so all ARS Servers will need to have the AO certificate installed into the Java keystore that is used by the plugin server (armonitor file will tell you what Java path)
                            • AR Dev Studio, needs to have the AO certificate installed into the Java keystore that the Dev Studio is using (Java path can be found in the devstudio.ini file)

                             

                            If building a ARS Filter to call AO via the inbuilt configuration, the ARS Developer Studio application (usually run locally) needs to be able to query the AO CDP WS Endpoint (real time) and also have the AO certificate installed in the Java keystore that the ARS Developer Studio is using.  This allows the Filter to be saved to the AR System (and Remedy to "build" the Web Service call in the AR DB tables), but as the Filter is executed on the ARS Server(s) there is additional configuration required for when the Filter is actually executed.

                             

                            This configuration is separate from the ARS Servers, where each ARS Server needs to have the AO certificate installed in the Java keystore that is running the ARS Plugin Server (the path as found in the armonitor file) to run the ARS Filter.

                             

                            These are 2 completely independent configurations that need to be completed.

                             

                            Cheers

                            Carl

                             

                            Home