1.Log in to the primary node of the Oracle E-Business Suite instance.
2.Start the Oracle WebLogic Admin Server from the run file system, if it is not already running.
3.Take a backup of the run file system context file.
4.Edit the run file system context file to set the value for the
2.Start the Oracle WebLogic Admin Server from the run file system, if it is not already running.
3.Take a backup of the run file system context file.
4.Edit the run file system context file to set the value for the
s_wls_admin_console_access_nodes context variable to the list of trusted hosts that are allowed to access the Admin Server.
<s_wls_admin_console_access_nodes oa_var="s_wls_admin_console_access_nodes">ws1.myco.com,ws2.myco.com</s_wls_admin_console_access_nodes>
<s_wls_admin_console_access_nodes oa_var="s_wls_admin_console_access_nodes">ws1.myco.com,ws2.myco.com</s_wls_admin_console_access_nodes>
5.Run AutoConfig.
6.Stop and restart the Oracle WebLogic Admin Server.
If you need to make changes without having access to the Oracle WebLogic Server Administration Console, you can update or remove the connection filter rules by editing the $DOMAIN_HOME/config/config.xml file. However, changes added this way will be overwritten by the next AutoConfig run.
6.Stop and restart the Oracle WebLogic Admin Server.
If you need to make changes without having access to the Oracle WebLogic Server Administration Console, you can update or remove the connection filter rules by editing the $DOMAIN_HOME/config/config.xml file. However, changes added this way will be overwritten by the next AutoConfig run.
No comments:
Post a Comment