If you use the offline mapping method with their WSDL saved to disk, your PC
should not need to make a connection to their server.  Trying to map using
the URL will require a connection be made to load the WSDL definition.
Offline you have have the definition and can do all the work from your admin
tool/workstation.  Then when you save the filter with the mappings the ARS
server will make the connection to their server when the filter is
triggered.

Is there an ACL (Access Control List) or firewall rules setup to allow the
servers to communicate where a connection can not normally be made?  When
trying to load their WSDL using a URL from  their server your PC where the
Admin Tool is running will need to have the same access to their server
hosting the web service as your ARS server does.

I guess if you really needed to you might be able to use an SSH tunnel from
your PC to route admin tool traffic through you ARS server.  By doing this
your Admin tool would be using the same ACLs and/or firewall rules as the
ARS server.  BE WARNED!!!  This may be against security policies on either
side (and shouldn't be necessary if you go the loading the WSDL from a saved
file route).  You may want to do a little research before you go this route.

Jason

On Mon, Aug 3, 2009 at 2:55 AM, Sean Harrodine <[email protected]>wrote:

> ** Hi Jason,
>
> Thanks also for your input.
>
> We have had a look at the KM entry and extracted their certificate and
> saved it using Keytools into our Java certificates and can see it, but when
> i try to Load the HTTPS WSDL in a Set Field, i now get .......
>
> Additional Details:
> Connection timed out: connect
> com.remedy.arsys.ws.util.ARWSException: URI not found
> https://xxx.xxx.xxx.xxx/yyyyyy/DocHandler?wsdl
>     at com.remedy.arsys.ws.util.WsdlUtil.newDocument(WsdlUtil.java:151)
>     at com.remedy.arsys.ws.util.WsdlUtil.newDocument(WsdlUtil.java:165)
>     at com.remedy.arsys.ws.wsdl.WsdlParser.<init>(WsdlParser.java:88)
>     at
> com.remedy.arsys.ws.util.WsdlAdminInterface.parseWsdl(WsdlAdminInterface.java:327)
>     at
> com.remedy.arsys.ws.util.WsdlAdminInterface.parseWSDLIntoMappingString(WsdlAdminInterface.java:191)
>
> This was after reading a reply fron Dennis who said i may need the proxy
> settings in the Admin tool.
>
> I think the real crux of the problem is that the servers can talk on port
> 443.....we have been able to prove that, but the PC admin tool cant load the
> WSDL.
>
> This is a baffler.....well for me anyway !
>
> Sean
>
> ------------------------------
> *From:* Jason Miller <[email protected]>
> *To:* [email protected]
> *Sent:* Saturday, 1 August, 2009 9:45:01
> *Subject:* Re: Webservice - HTTPS problem :o(
>
> ** Hi Sean,
>
>
> Have you tried it without using SSL to make sure that the issue is really
> with SSL?
>
> What I found that worked better for us was to save the WSDL and load into
> the filter from disk versus the remote web server.  It should allow you to
> setup the filter and mappings offline without errors trying to make a
> connection.  Obviously you will need to resolve the connection issues but
> this allows you to isolate WSDL and connection issues.
>
> You will have to do the mapping twice but you may want to try it without
> SSL first just to rule out WSDL issues, etc.  Change the URL specified in
> the "soap:address location=" in the WSDL file.  If that works set the WSDL
> back up for SSL (and reload/remap).
>
> It sounds like their cert is not signed by a CA trusted by your Linux box
> since you have to accept it.  That can also cause issues if your Linux box
> doesn't trust the issuer of their cert.  The ARS web service call cannot
> perform the intermediate step of accepting.  Your server will need to trust
> the cert without that manual accepting step.  You will need to add their
> cert to your java keystore on the ARS server.  Look up KM-000000020740
> titled "Problems loading or running a webservice from a site hosting the
> WSDL on an SSL webserver." in the BMC knowledgebase.
>
> Hope this helps.  I am by no means a web service guru but we just went
> through this recently so what we did is fresh in my mind.
> Jason
>
> On Fri, Jul 31, 2009 at 10:01 AM, Sean Harrodine 
> <[email protected]>wrote:
>
>> ** Hi everyone !
>>
>> (Remedy 6.3)
>>
>> I am trying to access a HTTPS WSDL from within a filter but am receiving
>> the following error when i click to "Load" the WSDL.....
>>
>>
>> Failed to create internal mapping from wsdl. (ARERR 7012)
>>
>>
>> ERROR: URI not found https://xxxx.yyyy.zzzz.com/nnnnnWS/DocHandler?wsdl
>>
>> Additional Details:
>> xxxx.yyyy.zzzz.com
>> com.remedy.arsys.ws.util.ARWSException: URI not found
>> https://xxxx.yyyy.zzzz.com/nnnnnWS/DocHandler?wsdl
>>     at com.remedy.arsys.ws.util.WsdlUtil.newDocument(WsdlUtil.java:151)
>>     at com.remedy.arsys.ws.util.WsdlUtil.newDocument(WsdlUtil.java:165)
>>     at com.remedy.arsys.ws.wsdl.WsdlParser.<init>(WsdlParser.java:88)
>>     at
>> com.remedy.arsys.ws.util.WsdlAdminInterface.parseWsdl(WsdlAdminInterface.java:327)
>>     at
>> com.remedy.arsys.ws.util.WsdlAdminInterface.parseWSDLIntoMappingString(WsdlAdminInterface.java:191)
>>
>>
>> The URL is an HTTPS secure connection to a company who are doing some
>> hosting work for us.
>>
>> From my Linux server, i can run a telnet to the "xxxx.yyyy.zzzz.com"
>> server on port 443......
>>
>> results...
>>
>> # telnet "xxxx.yyyy.zzzz.com" 443
>>
>> Trying xxx.xxx.xxx.xxx...
>> Connected to xxxx.yyyy.zzzz.com.
>> Escape character is '^]'.
>>
>> Ther are also able to perform the same tests in reverse so i am presuming
>> that the network is fine.
>>
>>
>> I can also access their WSDL using a browser with "no proxy settings set
>> !" on my Linux Remedy server, i can accept the certificate and see the
>> contents of their WSDL
>>
>>
>> But, when i try to create a Filter / WebService / Set Field (WEBSERVICE),
>> i get the error message detailed at the top of this email.
>>
>>
>> So, is anyone able to advise what the issue may be please ???
>>
>> thanks in advance to anyone who is able to offer some support !
>> Sean
>>
>>
>>  _Platinum Sponsor: [email protected] ARSlist: "Where the Answers
>> Are"_
>
>
> _Platinum Sponsor: [email protected] ARSlist: "Where the Answers
> Are"_
>
>  _Platinum Sponsor: [email protected] ARSlist: "Where the Answers
> Are"_
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to