I am setting up a RI/internal server architecture. I installed SAP BC 46 on both servers. I created a SOCK listener at port 443 on the RI server (in my DMZ) . Now I am trying to register it on the internal server. If i try to register it the Internal server tells me “Unable to register any Reverse Connection with alias”. I can telnet the RI from then internal on 443, but for some reason I am not able to register it.
Can anybody help me with this issue?
You will need to create a SOCK listener on another port then 443, since this port is used by the internal server to connect over. 443 will be the proxy port you create on the RI server for external parties to connect to. You will also need to create a remote alias that points to your RI server (using the port registered for SOCK).
My RI server has two ports: 443 SOCK where the listener is running and a 5556 HTTP listening for external parties.
My Internal server has a remote alias configured to talk to the RI (IP address) on port 443 (where the RI is listening). The authetication method used by the remote alias is User/password.
Still I can’t register the Reverse Connection.
Is there an issue if I listen to extenal parties with 5556?
Why the registration doesn’t take place…is there something extra I have to do?
I think we need to see more detail of the error you are getting, right now you are only sharing the error seen on the Admin UI when trying to register a reverse invoke conn. Could you increase the logging and see what the underlying error is? Also have you tried to register another port than 443? This since 443 is usually for HTTPS traffic.
There could be another conflicting alias that is not working properly that it’s trying to use underneath. What you could do is remove the cnf files (revInvoke-connList) or something similar from the config folder (first shutdown) I think there are 2 related files. Then re-register the connections (creating the alias again). Safest way is to make a backup of the cnf files.
I stop the SAP BC, I deleted two files
remote.cnf
revinvoke-auth.cnf
I restarted the SAP BC.
I created the remote serever and repeated the registration unsuccessfully. I noticed that just the remote.cnf have been recreated (!?).
I created also with a fancy remote sever with a fancy IP address and the system is correctly complaining in the log about it, when I try to register it…
Might be that the authentication method is wrong? In the IS I specified Administrator/password of the RI box…is this correct?