Question:
Hi all!
I too am new to business connector. Can anyone tell me if they have had problems connecting to another business that uses the Extricity software instead of business connector? How did you solve the problems.
Thanks
Deirdre
Answer:
It shouldn't matter what other middleware you are connecting to.
using the XML standard over http - you should be able to connect to anything ...
What specific problems are you having ...
j
Answer:
It seems that any company that has Extricity can't connect - they see and we see in the logs "Access denied" but it doesn't give a reason why the access is denied. We are able to connect from a separate machine to our business connector both inside and outside our firewall. As far as we can tell, we have everything set up the way it should be, but we must be missing something. Thanks for your help!
Deirdre
Answer:
Also we are trying to have them connect to https port using certificates, not the http port.
Answer:
Hi,
did you create a https port under you Business Connector ???
I think you should maintain data for certificate !!!
AND verify that the service that will be called can be called by the user to connect to the server !!
SSII
Answer:
The error 403 is very misleading.
you get this error when an error is thrown when a system is trying to connect. It is not necessarily the main problem.
I assume that your port config is set up to allow access from their IP etc.
Is it possable to test without the HTTPS ?
Have you tried getting them to call a service which has savePipelinetofile or Tracepipeline as the first service ? so that you can see what they are sending you ?
Let me know how you get on
J
Answer:
Hi again!
Yes we have an https port created and setup. All data is maintained for the certificate and services are allowed by the users who are trying to connect. Their IP addresses are allowed to connect as well.
However we are seeing the error "401 Access Denied" in the server log when they try to connect with POST /invoke/Inbound/ProcessRNO. This error was seen with both the user name set to "DEFAULT" and to a valid username. This server is not setup as reverse proxy and is setup outside our firewall for testing right now. We have successfully connected to it ourselves from both inside and outside our firewall with a temporary certificate from Verisign. We have even applied the BC46_SR4 to the test server to see if this would help. So far the errors are the same, and we are still able to connect with our temporary certificate.
Any suggestions would be appreciated.
Thanks again!
Deirdre
Answer:
Hi,
Go to Packages Management.
select Browse Folders.
Verify the ACL of your folder (I think it's Inbound).
Go to your folder.
Verify the ACL of your Service (I think it's ProcessRNO).
The user that you should use should be a member of the ACL of the service or of the folder if the service inhirit it from the folder.
I hope this can help.
SSII
Answer:
Hello!
ACL's are all correct- on the folder and service and the user is part of the ACL assigned. That is why we don't understand why they just get an error "401 access denied". If the user is not part of the ACL they would get the "username access denied on port 443" error. We tested for this as well. Thanks for your help!
Deirdre