Before configuring Visitor Services, make sure the prerequisite tasks are done.

1. Create a WebCenter Sites – Visitor Services database schema with the Repository Creation Utility, as Creating the Database Schemas describes.
2. Create Managed Servers for Visitor Services using the Configuration Wizard and the Oracle WebCenter Sites Visitor Services — 12.2.1.4.0[wcsites] template, as Configuring the WebCenter Sites Domain describes.

   Note:

   For IBM DB2, Visitor Services does not support the default data source that the Configuration Wizard creates. To create new data source with a driver that DB2 supports:

   1. Add the IBM DB2 Driver JAR files to the class path for the WebLogic domain.

      1. Stop the WebLogic Server Administration Server.

      2. Copy the db2jcc.jar and db2jcc_license_cu.jar files from DB2 to a location that you can add to the domain class path.

      3. Edit DOMAIN_HOME/bin/setDomainEnv.sh and add the following line after # ADD EXTENSIONS TO CLASSPATHS:

         PRE_CLASSPATH="path_to_db2jcc.jar:path_to_db2jcc_license_cu.jar:${PRE_CLASSPATH}"

      4. Start the Administration Server.

   2. Create a new data source using the preceding DB2 driver. For more information, see Specifying JDBC Component Schema Information.

The Visitor Services Configurator supports silent mode and interactive mode.

1. Start the Visitor Services Managed Server.
2. In a web browser, access the Visitor Services Configurator at the following URL: http://visitorservices-host:visitorservices-port/visitors-webapp/bootstrapconfig
3. On the Visitor Services Configurator screen that appears, click Begin.
4. On the screen that appears, complete the Sites Web Application Parameters section as the following table shows.

   Name	Description
   Host name or IP address	Host name or IP address of the target WebCenter Sites instance.
   Port number	Port number of the target WebCenter Sites instance.
   Application context root	Context root of the target WebCenter Sites instance.
   Secure connection?	If your environment is set up for SSL connectivity, select Yes; otherwise, select No.
   Site name	Name of the target WebCenter Sites site.
   Username	Name of the Administrator user account for the target WebCenter Sites instance.
   Password	Password of the Administrator user account for the target WebCenter Sites instance.
   Re-enter the Password	Confirm the password entered in the previous field.

5. Complete the Visitor Services Parameters section as follows:

   Name	Description
   Data Source JNDI Name	Full name of the Visitor Services data source. If you have used the Repository Creation Utility to create the Visitor Services data repository, this is automatically pre-populated.
   Have you configured JMS resources?	If you want to integrate Visitor Services with Java Messaging Service, select Yes; otherwise, select No.
   JMS connection factory JNDI name	Full name of the Java Messaging Service connection factory.
   JMS enrichment queue JNDI name	Full name of the Java Messaging Service enrichment queue.
   JMS profile update queue JNDI name	Full name of the Java Messaging Service profile update queue.
   JMS Transaction support	Select Yes to enable Java Messaging Service transaction support; otherwise, select No.
   JMS Persistence support	Select Yes to enable Java Messaging Service persistence support; otherwise, select No.

6. Click Test to test connectivity with the WebCenter Sites instance.
7. When the connectivity test succeeds, click OK to initiate the configuration process and wait for the confirmation screen to appear.
8. In the confirmation screen, you must click Close to commit your configuration; if you do not click Close, your configuration will be lost.
9. Restart the Visitor Services Managed Server.
10. Log in to the WebCenter Sites Admin interface.
11. Configure a Visitor Services Administrator user name and password in the WebCenter Sites Property Management Tool:

    1. Select the Admin interface icon.

    2. In the Admin tree, expand System Tools, and then double-click Property Management.

    3. Edit the wcsites.visitors.auth.user and wcsites.visitors.auth.password properties to set the user name and password.

12. Restart the WebCenter Sites Managed Server.
13. Create and enable an identity provider to use with Visitor Services. An identity provider authenticates site visitors to Visitor Services. Visitor Services ships with an Oracle Access Manager identity provider for integration with Oracle Access Manager.
14. (Optional) Create and enable an access provider to use with Visitor Services. An access provider authenticates REST calls made between Visitor Services and WebCenter Sites. Oracle recommends using an access provider to maintain a secure connection between Visitor Services and WebCenter Sites. Visitor Services ships with a basic LDAP access provider for authentication against an LDAP directory.
    You also need to set the following properties:

    • wcsites.visitors.auth.password

    • visitors.rest.authalias

    • visitors.rest.authtype

    • visitors.rest.authheader

    • wcsites.visitors.auth.user

15. Create and enable one or more profile providers. A profile provider allows the association of a visitor identity with a visitor profile. Visitor Services ships with an Eloqua profile provider for integration with the Eloqua Cloud Marketing Service, and an Oracle Access Manager profile provider for integration with Oracle Access Manager. Eloqua integration name should be the same in Management and Delivery system, and is case sensitive.
16. Create an aggregation template. An aggregation template determines what data, based on visitor profiles, is returned to the site visitors.
    For more information, see Developing WebCenter Sites: Visitor Services in Developing with Oracle WebCenter Sites.
17. Restart the WebCenter Sites and Visitor Services Managed Servers.

The Oracle WebCenter Sites: Visitor Services OAMIdentityProvider is supported for Oracle Access Manager 11.1.2.2.0 and 11.1.2.3.0.

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.

Configure JMS Cluster setup for Visitor Services using Persistent Store, JMS Server, and JMS Module.

Configuring Persistent Store

Using the VSjms Support wizard, configure the Persistent Store:

1. In the Persistent Stores, locate WL left nav services.

2. Select Persistent Store and then Vsjms Support.

3. In Directory field, point to valid shared filesystem, for example:/u01/oracle/12.2.1/tmp/prod/.

4. In the location on disk /u01/oracle/12.2.1/tmp/prod/ selected earlier, create rs_daemons.cfg file.

5. Save the changes to the Persistence Store.

   Note:

   On saving the changes, an error occurs click Ignore and complete the process.

6. Edit the rs_daemons.cfg file and enter the values. The following example shows the values that needs to be set for the servers:

   #ipaddress	portno	shmkey	memlmt
   111.222.2.333	14545	4545	1G
   111.666.2.111	14546	4545	1G

7. Save the file rs_daemons.cfg file.

For more information on rs_daemons.cfg file, see Messaging Services.

Figure 10-1 Persistent Store Configure for Oracle WebCenter Sites: Visitor Services

Description of "Figure 10-1 Persistent Store Configure for Oracle WebCenter Sites: Visitor Services "

Configuring JMS Servers

To update the JMS Server :

1. In configuration wizard you will see that it contains VSjms Server already created.

2. On the Persistent Stores, locate WL left nav services.

3. Select JMS Servers>VSjms Server.

4. In the Setting for VSJMS Server, select Targets tab.

5. Select Visitor Services Cluster from the drop-down list. Figure 10-2 shows the example for wcvisitor

6. Click Save.

   Note:

   On saving the changes, an error occurs click Ignore and continue and complete the process.

Figure 10-2 JMS Servers Configuration for Oracle WebCenter Sites: Visitor Services

Description of "Figure 10-2 JMS Servers Configuration for Oracle WebCenter Sites: Visitor Services "

Configuring JMS Module

To update the JMS Module .

1. The configuration wizard you will see that it contains VSjms Module already created.

2. Locate WL left nav services.

3. Select JMS Modules>VSjms Module>VSjms Server.

4. Click Targets tab and select the entire cluster.

5. Click Save.

   Note:

   On saving the changes, an error occurs click Ignore and continue and complete the process.

6. Click Subdeployments tab.

7. View the subdelpoyment, Vsjms Module Sub.

8. Here it should points to Vsjms Server. Do not modify when it points to Vsjms Server.

9. Click Configuration tab.

10. Select wcsitesVisitorsEnrichQueue and wcsitesVisitorsUpdateQueue.

11. Click Delete, as these are standalone queues and does not work for the cluster.

12. Click New .

13. Select Distributed Queue and click Next.

14. Under Name filed enter wcsitesVisitorsEnrichQueue and under JNDI Name enterjms/wcsitesVisitorsEnrichQueue.

15. Click Save.

16. Return to the JMS Module Configuration tab.

17. Click New.

18. Select Distributed Queue and click Next.

19. In the Name filed enter wcsitesVisitorsUpdateQueue.

20. In the JNDI Name enter jms/wcsitesVisitorsUpdateQueue.

21. Click Save.

22. The configuration page should now appear similar to Figure 10-3.

    Note:

    Ensure that after completing this step you should not get any errors displayed in red on the top bar.

Figure 10-3 Settings for VSjms Server for Oracle WebCenter Sites: Visitor Services

Description of "Figure 10-3 Settings for VSjms Server for Oracle WebCenter Sites: Visitor Services"