Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


Note!

Refer to /wiki/spaces/3PP/pages/1671475 for supported Couchbase versions.

In order for Usage Engine to communicate with the Couchbase database, the couchbase.mzp package must be included in your Usage Engine installation.

When the couchbase.mzp package is installed in Usage Engine, the Couchbase database can be installed by following the steps described in the Couchbase documentation, http://www.couchbase.com.

 

Note!

Couchbase services required by Usage Engine are:

These links may refer to another version of Couchbase than the one you install. If you install a different version, refer to docs.couchbase.com for the corresponding documentation version. 

Note!

 For the optimal Couchbase Server operations, you must set swappiness to 0 (zero) as described in the topic about swap space.

When Couchbase is installed, buckets for each created Couchbase profile will be generated and visible in the Couchbase Web Console, as soon as the data buckets are called.

Couchbase Profiles Required by PCC

You should now create two Couchbase Profiles; one for the static configurations in the Data Repository, and one for the runtime data in the Data Repository.

To create the Couchbase profiles:
 

  1. Click on the New Configuration button in the upper left part of the Usage Engine Desktop window, and then select Couchbase Profile from the menu.

    A Couchbase Profile configuration opens.

    In this dialog you have three tabs; Connectivity, which contains settings for the connections between the buckets in the cluster(s), Management , which contains the user name, password, size, and monitoring settings for the bucket, and Advanced, which contains the advanced properties.
     

  2. Create one profile for the configurations bucket, where:

    • The Bucket Name is config or something similar.

    • Set the Bucket User and User Password as a user who has access to the bucket and their password.

    • The Cluster Nodes section contains the IP-address/host name for each of the Couchbase nodes in the cluster.

    • The user name and password for the administrator created during Initial Server setup is added in the Management tab.

    • You can select the Monitoring checkbox if you want to use monitoring functions for detecting unresponsive nodes and performing fail-over.

    This profile will create a bucket called config (or similar), which will be used for static data in the Data Repository, such as the different configurations.
     

  3. Create another profile for the usage bucket, where:

    • The bucket name is bucket or something similar.

    • Set the Bucket User and User Password as a user who has access to the bucket and their password.

    • The Cluster Nodes section contains the IP-address/host name for each of the Couchbase nodes in the cluster.

    • The user name and password for the administrator created during Initial Server setup is added in the Management tab.

    • You can select the Monitoring checkbox if you want to use monitoring functions for detecting unresponding nodes and performing fail-over.

    This profile will create a usage bucket called bucket (or similar), which will be used for the runtime data in the Data Repository, that is, the actual usage of the subscribers.
     

  4. In each ECD Execution Context, open the pcc.properties file, located in the MZ_HOME/etc directory, and enter the names of your newly created profiles in the following properties:

    mz.pcc.storage.couchbase.config.profile=
mz.pcc.storage.couchbase.buckets.profile=

    Example - pcc.properties

    mz.pcc.storage.couchbase.config.profile=MyFolder.config
mz.pcc.storage.couchbase.buckets.profile=MyFolder.bucket

  5. In the PCC Config Storage Properties group, ensure that the property mz.pcc.config.storage.class is set to com.digitalroute.pcc.storage.config.couchbase.CouchbaseConfigStorage.
     

  6. In the PCC Bucket Storage Properties group, ensure that the property mz.pcc.bucket.storage.class is set to com.digitalroute.pcc.buckets.storage.couchbase.CouchbaseBucketStorage.

     

  7. Save the pcc.properties file.
     

  8. In order for the ECDs to be able to locate the pcc.properties file, you must set the property mz.pcc.properties.

    Example - Setting mz.pcc.properties

     mz.pcc.properties='${mz.home}/"etc/pcc.properties"'

    Note

    It is important that the pcc.properties property file is located in the stated directory in all Execution Contexts.

  9. Restart the ECs.

For further information about the settings in the Couchbase profile, see Couchbase (3.0).



  • No labels