What are some of the issues in using IIOP with a combined WebSphere and Domino system? As with servlets, IIOP was discussed in both Chapters 9 and 10, and there were few if any issues related to "IIOP vs. XML." This section gives a short summary of the discussions in Chapters 9 and 10 on IIOP and XML.
Connecting to Domino Using IIOP
As described in Chapter 10, remote sessions to Domino are established using a CORBA mechanism via IIOP. The HTTP and DIIOP server tasks must be running on the Domino server, which is the target of a remote session. The type of access for a lotus.domino session is determined by the signature of the createSession method of the Session class.
SSL Enabling of IIOP Session
As with all WAS configuration files, the plug-in configuration file has XML syntax and thus can be edited with any text editor. The LogName element specifies the file name of the log file written by the plug-in and the level of logging desired. The ServerGroup element specifies the WAS server(s) to which URLs are routed and the protocol used. The default is to route to the local WAS server at port 9080 (the embedded WAS HTTP server) over HTTP. Additional servers can be specified here, as well as HTTPS instead of HTTP. If more than one server is specified within a server group , the plug-in routes to the servers in a round- robin fashion. If HTTPS is used, additional system environment variables must be set pointing to the SSL libraries and the certificate and encryption key files required by the plug-in for HTTPS.
