Changing EBSDataSource to restrict connections

Posted by on Oct 28, 2022; 3:45pm
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Changing-EBSDataSource-to-restrict-connections-tp11172.html

We are setting up EBS R12.2 environment with 7 Node RAC and 6 application nodes (1st 3 are application services nodes and remaining 3 are concurrent processing nodes). There is one to one relationship btw 1st 6 RAC nodes and 6 application nodes to avoid excessive block shipping over interconnect. 7th RAC node is for adhoc and 3rd party s/w connections.

The EBSDataSource is defined in Weblogic using SCAN VIP

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=acme.corp.com)(PORT=1522)))(CONNECT_DATA=(SERVICE_NAME=ebs_xxx)))

As service "ebs_xxx" is active on all 7 RAC nodes, application services (forms_server, oacore_server) and logons to application can spawn connections to any of the 7RAC nodes.

We want to restrict application services (forms_server, oacore_server) and logons to application to 1st 3 nodes defined for application.

Can we recreate EBSDataSource using custom service that is active on just 1st 3 RAC nodes to restrict connections to them?

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=server1.corp.com)(PORT=1522))(ADDRESS=(PROTOCOL=tcp)(HOST=server2.corp.com)(PORT=1522))(ADDRESS=(PROTOCOL=tcp)(HOST=server3.corp.com)(PORT=1522)))(CONNECT_DATA=(SERVICE_NAME=ebs_new)))