After you set up the Oracle WebCenter Sites: Visitor Services Managed Servers, you can configure Visitor Services with the browser-based Visitor Services Configurator. Visitor Services runtime consists of visitors-webapp
applications (WAR files), a config
directory, a database instance, sample bundle code, providers, and a visitors client.
The following topics describe configuring Visitor Services:
OAMIdentityProvider
is supported for Oracle Access Manager 11.1.2.2.0 and 11.1.2.3.0.Before configuring Visitor Services, make sure the prerequisite tasks are done.
The Visitor Services Configurator supports silent mode and interactive mode.
To configure Visitor Services in silent mode:
Edit the DOMAIN_HOME/wcsites/visitorservices/config/wcs_svs_properties_bootstrap.properties
file and update it with Oracle WebCenter Sites: Visitor Services details.
If Java Messaging Service (JMS) needs to be configured, update the JMS details; otherwise, keep visitors.jms_service_in_use=false
.
Start the Visitor Services Managed Server.
Complete the bootstrap process of Visitor Services using this URL: http://visitorservices-server:visitorservices-port/visitorservices-webcontext/bss
Restart the Visitor Services Managed Server.
The Oracle WebCenter Sites: Visitor Services OAMIdentityProvider
is supported for Oracle Access Manager 11.1.2.2.0 and 11.1.2.3.0.
For information about installing Oracle Access Manager, see the Oracle Identity and Access Management Installation Guide.
To get the visitorId
value using OAMIdentityProvider
:
Log in to WebCenter Sites at http://site-host:site-port/sites/
.
Select AdminSite, Select the Admin interface icon, and click Hide Left Hand Navigation, Admin, and then Identity Providers List.
Upload the identity-provider-oam.jar
file located under ORACLE_HOME/wcsites/visitorservices/providers/identity-providers/
, with appropriate configuration data in the configuration field.
Copy the configuration located under ORACLE_HOME/wcsites/visitorservices/providersConfig/identity-provider-oam/identity-provider-oam.properties
.
Click Profile Provider List
.
Make sure that the User Identity Store is configured for User profiles in Oracle Access Manager. (For User Identity Store configuration, see the Oracle Identity and Access Management Installation Guide.
Upload the profile-provider-ldap.jar
file with the name UserIdentityStore1
located under ORACLE_HOME/wcsites/visitorservices/providers/profile-providers/
with appropriate configuration data in the configuration field.
Copy the configuration located under ORACLE_HOME/wcsites/visitorservices/providersConfig/profile-provider-ldap/profile-provider-ldap.properties
.
The get visitorId for user ex
test belongs to the Oracle Access Manager embedded LDAP using the following URL in a REST client:
http://OHS-host:OHS-port/visitor-services-context/rest/v1/visitor/getId
Add the headers content-type
andapplication/x-www-form-urlencoded
, and provide the request body:
request={ "parameters":"{}", "headers":"{}", "cookies":"[{}]" "header":"{\"oam_identity_domain\":\"UserIdentityStore1\",\"oam_remote_user\":\"test\"}" }
To get the visitorId
value using SampleIdentityProvider
:
Log in to WebCenter Sites at http://sites-host:sites-port/sites/
Select AdminSite, Select the Admin interface icon, and click Hide Left Hand Navigation, Admin, and then Identity Providers List.
Upload the identity-provider-oam.jar
file located under ORACLE_HOME/wcsites/visitorservices/providers/identity-providers/
, with appropriate configuration data in the configuration field.
Copy the configuration located under ORACLE_HOME/wcsites/visitorservices/providersConfig/identity-provider-sample/identity-provider-sample.properties
.
Click Profile Provider List
. (Make sure that Oracle Internet Directory or another LDAP authentication provider is installed and configured.
Upload the profile-provider-ldap.jar
file located under ORACLE_HOME/wcsites/visitorservices/providersConfig/profile-provider-ldap/profile-provider-ldap.properties
.
Copy the configuration located under ORACLE_HOME/wcsites/visitorservices/providersConfig/profile-provider-ldap/profile-provider-ldap.properties
.
The get visitorId for user
test belongs to the Oracle Internet Directory LDAP using the following URL in a REST client:
http://visitorservices-host:visitorservices-port/visitorservices-context/rest/v1/visitor/getId
Add the headers content-type
andapplication/x-www-form-urlencoded
, and provide the request body:
request={ "parameters":"{\"external_id\":[\"ssoid1\"]}", "headers":"{}", "cookies":"[{}]" "header":"{}" }
Visitor Services is a completely stateless web application, so there is no need for session replication or session management at the cluster level. Cluster configuration of Visitor Services mainly involves taking care of configuration data.
After the first node (primary cluster node) has been created, all other nodes should use the configuration files from the primary cluster node. Of particular importance is the visitors.properties
file. The main configuration file for Visitor Services is visitors.properties
. This file contains details about the data source in the Visitor Services database, JMS objects, and a URL to a WebCenter Sites instance (either one node or if there is a WebCenter Sites cluster, the load-balancer URL). The secondary nodes can use the visitors.properties
file from the primary cluster node in either of two ways:
All nodes in the Visitor Services cluster can have a replica of the same Visitor Services file in their class path.
All nodes can point to single visitors.properties
file with file path being in a shared folder.
There is a single database for the entire Visitor Services cluster. The data source property in the visitors.properties
file for each node should point to this single database.
Other Visitor Services configuration files are not meant for modification. Copy them as is from the primary node to the secondary nodes.
Although JMS is optional, Oracle recommended that JMS be used. Each node should point to same JMS objects. A nodes should not configure a different JMS queue because having that node down would result in losing out on messages present in that queue.
The visitors-cache.xml
file provides distributed caching configuration for managing a cache of visitors objects (identity provider
, access provider
, profile provider
, aggregation templates
, and visitor configuration
). Because this is a distributed cache, all the nodes should have same values for the following properties inside this file:
multicastGroupPort
multicastGroupAddress
Oracle recommends that you set the values for these properties in the visitors-cache.xml
file on the primary cluster node and then copy the file to each secondary node. You could also do this manually, by making the change in the file locally, on each secondary node.
The visitors-logging.xml
file provides log-level setting for different loggers. To have a consistent logging experience across nodes, Oracle recommends that all nodes use same file or propagate changes made on one node manually to local copies of this file on all nodes.
Note:
Because changes you make to a WAR file are not retained during redeployment, WAR file changes need to be copied over after each redeployment of the web applications. It is generally recommended to deploy the static artifacts such as images and stylesheet files onto the web server.