Is Dssetup 220.127.116.11 & MS8 Really Required to Run Convergence 3.0.1?
(Doc ID 2142994.1)
Last updated on NOVEMBER 19, 2018
Applies to:Oracle Communications Convergence - Version 3.0.1 and later
Information in this document applies to any platform.
Testing Convergence 18.104.22.168.0 (Mail and Addressbook services only, no Calendar, IM, ISS) in lab and have reached the point where we want to now deploy an instance utilizing our production LDAP and Message stores. Reading through the documentation it is indicated that Convergence 3.0.1.x requires Messaging Server 8.0.0. Consequently, Messaging Server 8.x requires a minimum comm_dssetup version to be active in LDAP which is 22.214.171.124.
Our production environment today is a mix of Messaging Server 126.96.36.199.0 (MMPs), 188.8.131.52.0 (message stores and mshttpd), and 184.108.40.206.0 (MTAs) and Convergence 2 patch7. The production LDAP comm_dssetup is version 220.127.116.11-03 (schema 1).
We would like to avoid a comm_dssetup update to the production LDAP if at all possible.
Can we reliably run Convergence 18.104.22.168 with mail and addressbook services only, supported by a locally installed instance of Messaging Server 22.214.171.124.0 and LDAP with comm_dssetup at version 126.96.36.199-03 (schema 1) ?
Or, is Convergence 188.8.131.52 with locally installed Messaging Server of the latest 8.x version, and still using LDAP comm_dssetup is version 184.108.40.206-03 (schema 1) a better approach?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document