Versions Compared

Old Version 1

changes.mady.by.user Jenni Wallin

Saved on

compared with

New Version Current

changes.mady.by.user Jenni Wallin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Image Removed

Couchbase Software

Image Added

Couchbase services required by Image Removed are
Excerpt


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

In order for Image Removed to for Usage Engine to communicate with the Couchbase database, the couchbase.mzp package the PCC Couchbase Storage option must be included in your Image Removed installation.When the couchbase.mzp package is installed in Image Removed, your license.

You can then install the Couchbase database can be installed by following these steps:

Open a web browser and go to http://www

the steps described in the Couchbase documentation, docs.couchbase.com.

Click Downloads.

 

  • Select the Enterprise edition for  your operating system.
     

    • Click on Install Instructions to view information on how to install Couchbase. 

    Note
    titleNote!
    It is important that you perform the steps that are specific to your operating system. For instance, when you install

    Couchbase

    on an operating system that is based on Red Hat Enterprise Linux, Transparent Huge Pages (THP) should be disabled on all server nodes.  

     

    Note
    titleNote!

    services required by Usage Engine are:

    • Data
    • Index
    • Query
    These links may refer to another version of Couchbase than the one you install. If you install a different version, refer

    Refer to docs.couchbase.com for

    the corresponding documentation version

    information about these services. 

    In the Couchbase documentation, review the subtopics under Deployment Considerations in Administration.


    Note
    titleNote!

     For the optimal Couchbase Server operations, you must set swappiness to 0 (zero)

    as described in the topic about swap space.Start a web browser and go to http://localhost:8091. The Couchbase Web Administration interface opens

    .

    Click the Setup New Cluster button and follow the instructions https://docs.couchbase.com/server/6.0/install/init-setup.html#set-up-a-new-cluster. The Couchbase Web Console opens displaying the Dashboard.
    Image Removed
    The Couchbase Dashboard
    In the Dashboard, select Settings and click on the Auto-Compaction tab. Select the checkbox Compact Buckets and View indexes in parallel.

    When

    you have a large number of documents in the database, creating iterators may sometimes fail. Enabling this setting may help to mitigate this problem.
    Repeat the installation on all the Couchbase nodes in the cluster, and ensure that you select the option Join Existing Cluster during the installation of the remaining nodes.
    In the Dashboard on any of the nodes, select Servers and click the Rebalance button to distribute the data between the nodes evenly.
    Image Removed

    Couchbase

    Dashboard showing the Rebalance button
    Couchbase

    is

    now

    installed,

    and

    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 these Couchbase profiles:
     

    1. Click on the New Configuration button in the upper left part of the Image Removed Desktop windowthe Desktop, and then select double-click on the Couchbase Profile from in the menulist.

      A Couchbase Profile configuration opens.

      In this dialog Here 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 configurationsrules, products and periods defined.
       

    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-overfailover.

      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 Execution Context, open Open the pcc.properties file, located in the MZ_HOMEthe /etc/pcc/pcc.properties directory, and enter the names of your newly created profiles in with the following properties:

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


      Info
      titleExample - pcc.properties


      Code Block
      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 ECs to ECDs to be able to locate the pcc.properties file, you must set add the Execution Context property mz.pcc.properties.

      Info
      titleExample - Setting mz.pcc.properties
      Code Block

      following system property:

      Code Block
      mz.pcc.properties=
      '${mz.home}
      /
      "
      etc/pcc/pcc.properties
      "'
      Note
      titleNote

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

    9. Restart the ECs.


    10. for each ECD, see Configuring ECD(s) with PCC Properties (3.1).
    For further information about the settings in the Couchbase profile, see Couchbase (3.01).