Master/slave Database

[Former Member]

Dear Friends

Scenario is JDBC-RFC.

Sometime the database goes down and for the time being another database becomes operational.

the only thing that is going to change is the connection string of the JDBC Sender channel .

For example

jdbc:oracle:thin:@192.96.24.61:1521:test

will become

jdbc:oracle:thin:@172.xx.xx.xx:1521:test

Is there any way by which we can achieve the same without creating the same scenario again with different ip.

i want to have only one scenario.

Regards

Monika

[MichalKrawczyk · Accepted solution]

hi Monika,

>>>>Is there any way by which we can achieve the same without creating the same scenario again with different ip.

this is possible:

a) you need to create an alias domain for your DBs - like "oracledomain"

b) put it in the communication channel instead of the IP

c) once the DB goes down a script needs to be invoked which will change the alias IP from one to another

then you don't need to change anything in the channel

how does it sound ?

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Thanks Michael

I would recommend this to the Client's DB team.

Regards

Monika

[rajasekhar_reddy14]

no standard mechanism available to change connection parameter detaills.

Adapter module might be possible.