“localhost:6021: Connection refused” recurring in OAM system

The  OAM components such as Identity server and Access Server are running on ports 6034 and 6035 respectively in my environment. As everyone know that port 6021 will be used for Access Server in general. So, if you are using a different port and configured Access Server flush in Identity Server, then you may witness the error “localhost:6021: Connection refused” in your OAM machine.

To know more about configuring automatic Access Server flush in OAM, refer this post.

You can see the port 6021 in the ObAccessClient.xml.

All I changed is the parameter doAccessServerFlush to true present in the file baseddbparams.xml in the location IdentityServer/oblix/data/common and bounced the identity server.  However that was not just enough to do Automatic Access Server flush.

Few additional steps required are:

1. Create a dummy Access Gate in OAM Access Console without specifying any port. Associate it with an access server.

2. Run the configureAccessGate command present in the location /identity/AccessServerSDK/oblix/tools/configureAccessGate pointing to point to the dummy Access gate created.

3. Check the port in ObAccessClient.xml. You should see actual Access Server port instead of 6021.

4. Restart identity server.

That’s it. You will not see the error “localhost:6021: Connection refused” anymore.

Helpful Docs:

Oracle  documentation

About the Author Mahendra

I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com

Leave a Comment:

1 comments
Twitter Trackbacks for » “localhost:6021: Connection refused” recurring in OAM system Online Apps DBA: One Stop Shop for Apps DBA’s [onlineappsdba.com] on Topsy.com says February 10, 2011

[…] » “localhost:6021: Connection refused” recurring in OAM system Online Apps DBA: One Stop Shop f… onlineappsdba.com/index.php/2011/02/10/localhost6021-connection-refused-recurring-in-oam-system/ – view page – cached The OAM components such as Identity server and Access Server are running on ports 6034 and 6035 respectively in my environment. As everyone know that port 6021 will be used for Access Server in general. So, if you are using a different port and configured Access Server flush in Identity Server, then you may witness the error “localhost:6021: Connection refused” in your OAM […]

Reply
Add Your Reply

Not found