- 3,708,965 Users
- 2,241,167 Discussions
- 7,840,723 Comments
Forum Stats
Discussions
Categories
- 22 Industry Applications
- 3.2K Intelligent Advisor
- 4 Insurance
- 754 On-Premises Infrastructure
- 253 Analytics Software
- 22 Application Development Software
- 1.7K Cloud Platform
- 700.4K Database Software
- 17.4K Enterprise Manager
- 5 Hardware
- 110 Infrastructure Software
- 70 Integration
- 45 Security Software
How to properly quiesce B2B 12c?

What is the best way to "pause" Production B2B when remote trading partner needs to update password? Need to make sure inbound and outbound B2B wait until remote partner confirms that the password change has completed. In 10g B2B it was possible to quiesce B2B, but that option is not in B2B 12c.
Answers
Hi Jimhim,
You could pause consumption on the queues. In Weblogic JMS you can do that on the JMS Server, if you use those.
In AQ you can do dbms_aqadm.startqueue (https://docs.oracle.com/database/121/ARPLS/d_aqadm.htm#ARPLS113 ) where you set dequeue=false for the ip queues. Then afterwards call it again with dequeue=true.
Then enqueueing is possible, but the messages aren't processed. At my current customer we use a second set of queues and use OSB to move the messages back and forth. That way they can disable the particular proxy services.
Regards,
Martien
There is a feature in B2B to schedule downtime, using which we can achieve this - https://docs.oracle.com/cd/E15586_01/integration.1111/e10229/b2b_tpdowntime.htm
Regards,
Dheeraj