Using Remote Intradoc Client RIDC 9-3
An example of using the IDC protocol over a secure socket SSL follows: build a secure IDC client as cast to specific type
IntradocClient idcClient = IntradocClient manager.createClientidcs:localhost:54444;
set the SSL socket options config.setKeystoreFileketstoreclient_keystore; location of keystore file
config.setKeystorePassword password; keystore password config.setKeystoreAliasSecureClient; keystore alias
config.setKeystoreAliasPasswordpassword; password for keystore alias
For more information, see Section 9.11, Configuring SSL Communication with Oracle
Content Server.
9.1.3 MBeans Implementation
RIDC provides an MBeans implementation allowing administrators to change properties of an RIDC connection at runtime using JMX and MBeans.
To register and enable MBeans, add the following to your code: import oracle.stellent.ridc.convenience.adf.mbeans.IdcMBeanManager;
... connection name is the connection in the ADFContext you want to manage
IdcMBeanManager mbeanManager = IdcMBeanManager.getInstanceconnectionName; mbeanManager.register;
Once the application has started, edit the connection using a tool such as JConsole to connect to your application and change connection information while the application
is running.
9.2 Initializing RIDC
To initialize RIDC, you will need the ECM Client libraries, which are shipped with the RIDC distribution, in your class path.
For the JAX-WS protocol, you also need to configure Oracle WebLogic Server security for the Oracle UCM web services. The security configuration includes these tasks:
■
Setting up the policy for the login service
■
Creating a new keystore file or adding credentials to your existing keystore, which will be used by both the server and the client
■
Setting up an Oracle wallet by adding the credentials The client requires the following items:
■
The JPS configuration file
■
The keystore
■
The Oracle wallet from the server For information about configuring the server and client for web services, see the Oracle
Fusion Middleware Services Reference Guide for Oracle Universal Content Management. The following table shows the URL formats that are supported.
9-4 Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management
This example code initializes RIDC for an Intradoc connection: create the manager
IdcClientManager manager = new IdcClientManager; build a client that will communicate using the intradoc protocol
IdcClient idcClient = manager.createClientidc:localhost:4444; This example code initializes an HTTP connection the only difference from an
Intradoc connection is the URL: create the manager
IdcClientManager manager = new IdcClientManager; build a client that will communicate using the HTTP protocol
IdcClient idcClient = manager.createClienthttp:localhostidcidcplg; This example code initializes a JAX-WS client. These two web services are exposed by
Oracle Content Server: the login service and the request service. You will need the web context root that these web services use. By default, this is idcnativews.
create the manager IdcClientManager manager = new IdcClientManager;
build a client that will communicate using the JAXWS protocol IdcClient idcClient = manager.createClienthttp:wlsserver:7044idcnativews;
9.3 Configuring Clients
