Comm Suite 6 Beta: Answering a Few Questions
By Joesciallo-Oracle on Mar 13, 2008
A few questions about the Communications Suite 6 release have come up this week, thought I'd pass them along.
Q. Can I simulaneously deploy the new Web client, Communication Center, alongside the existing web client, Communications Express?
A. The plan is that the new Communication Center and the existing Communications Express will be able to co-exist. We understand that some customers will need to continue using Communications Express for various reasons before completely switching over to Communication Center. We have conducted in-house testing of this co-existence scenario. Unofficially, we have had two setups: one in which CE is deployed in Web Server 7.0 and CC in Application Server 9.1 U1, as their respective web containers; and a second in which both are deployed in single Application Server 9.1 U1 web container. I repeat, these are unofficial, not fully tested/qa'd at this point.
Q. I've noticed that both the Identity Suite and the Communications Installer install the comm_dssetup.pl script, for modifying the LDAP directory schema. Which should I be using?
A. You want to use the comm_dssetup.pl script installed by the Communications Installer. The version provided by Identity Suite is out of date. However, if you install Identity Suite before the Communications Suite components, there is an issue. You will need to run the commpkg upgrade command to force an upgrade of the existing comm_dssetup.pl installed by Identity Suite, to the newer version bundled with the Communications Installer and Communications Suite 6 components. (If you just run commpkg install, and it already detects comm_dssetup, it will not install the newer version.) See the Note at the bottom of this page for more information.
Q. I am working on installing Communications Express in the beta program with IM Server integration. The section "Configure IM Components to Enable Communication with the Instant Messaging Server" mentions the following:
Provide the Httpbind JID and password. The Httpbind JID should be a meaningful string.What relationship does the JID have with a DNS name/hostname? Also, is the password mentioned here relative to a JCS component or something arbitrary for this portion of the configuration?
A. As far as the JIDs are concerned, they can be any arbitrary string. We have been embedding the host and domain in the string by convention but it doesn't have to be that way. Because the server can be distributed from the gateway the only stipulation is that the entries in the server's iim.conf file and in the gateway config files should match. That goes for passwords too. So when you view the httpbind jid in the iim.conf and the httpbind.conf files they should match. The JID is our way of providing component authentication with the server. Naming all JIDs the same (such as hostname) will probably cause problems especially when the server is talking to multiple components which may be running on the same host. Hence we use "httpbind" and "avatar" in our examples to distinguish the two.