We use OSB test console application to test Proxy/Business services before moving them to production.
When we install OSB for production mode then there is a separate 'osb_server1' managed server is installed.
Starting this server is mandatory to use 'test console'.
If you start working on designing OSB services without starting 'osb_server1' then all your changes are partially activated. You can check this on OSB console.
So when you 'click test console' before starting osb_server1 we see an error like
Error Accessing Test Configuration
"Test Console" service is not running. Contact administrator to start this service.
Solution to this is starting osb_server1.
If you still see error, then follow below step too.
Try setting the Admin server listen address to a specific valid address, such as localhost.
In the Oracle WebLogic Server Console, go to Environment > Servers > admin_server_name > Configuration > General to set the Listen Address.
If OSB server is installed for development mode, then you will not have this problem.
When we install OSB for production mode then there is a separate 'osb_server1' managed server is installed.
Starting this server is mandatory to use 'test console'.
If you start working on designing OSB services without starting 'osb_server1' then all your changes are partially activated. You can check this on OSB console.
So when you 'click test console' before starting osb_server1 we see an error like
Error Accessing Test Configuration
"Test Console" service is not running. Contact administrator to start this service.
Solution to this is starting osb_server1.
If you still see error, then follow below step too.
Try setting the Admin server listen address to a specific valid address, such as localhost.
In the Oracle WebLogic Server Console, go to Environment > Servers > admin_server_name > Configuration > General to set the Listen Address.
If OSB server is installed for development mode, then you will not have this problem.
