Changing EBSDataSource to restrict connections

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)))

[ErmanArslansOracleBlog]

7 node RAC and 6 nodes application, a big system :)

Yes, you can.. You can modify it.. Also check the two_task(s)..

Note that, you got to manage it yourself .. I mean; patching actions, autoconfig and stuff like that may overwrite that modification of yours.. s_weboh_twotask, s_weboh_twotask, jdbc_url and all that..


See -> Using Oracle 12c Release 1 (12.1) Real Application Clusters with Oracle E-Business Suite Release 12.2 (Doc ID 1626606.1) --> Get the standard and try to derive your action plan.

See -> Can Be The EBSDataSource in 12.2 Be Replaced By A MultiDataSource Or GridLink Datasource? (Doc ID 2017419.1)

Also see -> http://ermanarslan.blogspot.com/2021/01/ebs-122-configuring-application.html --> mine... interesting.

You may find a way to make autoconfig do it for you. I mean modifying the EBSDataSource.. for instnace changing the jdbc_url in the apps context file and running autoconfig on that node... It may help you on that.. ("but I didn't test it yet, you should test it!")

*Also take Oracle's approval by creating a SR to Oracle Support.