Skip to main content

Longview Adapter - Setting Up with CXO

Installation Prerequisites

  • CXO Version 24.1.3 (or higher)

  • .NET 6.0 or higher has to be installed

  • CXO Identity provider

  • Longview version 24.2.0 or newer

Important: Restart server after installing .NET core hosting bundle.

Setting up

  1. Install Longview Tidemark Adapter.

  2. Open CXO Configurator > Maintenance and click Register Services and Website.

  3. Select Register Longview Adapter Api to add service account details.

  4. Create Client in the CXO Identity Provider.

Identity Provider Configuration

  1. Create new Generic Client.

  2. Select Allow Offline Access.

  3. Add the following scopes:

    • User profile

    • User groups

  4. Add Redirect URL(s) in the following format:

    {LongviewTidemarkAdapterUrl}/signin-oidc

  5. Add Post Logout Redirect URL(s) in the following format:

    {LongviewTidemarkAdapterUrl}/signin-oidc-auth

Tip: RedirectUri’s are case sensitive so it’s good practice to use lowercase in all URLs.

CXO Configuration

To use Longview Tidemark Adapter you need a license key with Longview enabled.

  1. Initialize the Longview adapter. This needs to be one time for the initial setup and is performed by running a few commands which require few parameters as an input.

    For more information on the available commands and their parameters, run the CXO.Adapter.LongviewTidemark.Cli.exe help command for detailed descriptions.

  2. Open command line as Administrator, browse to the Longview Tidemark Adapter\Extraction folder and run the initialize command to create the configuration database.

    Avoid using spaces in the parameter values.

    Command Initialize
    Parameters

    • server-name: Name of the server on which the database should be created

    • database-name: Name of the database to be created

    • authentication-type: windows / proprietary

    • username: SQL user name (if authentication-type = proprietary)

    • password: SQL user password (if authentication-type = proprietary)

    • disable-encryption (optional): Set to yes to disable database encryption
    Example

    .\CXO.Adapter.LongviewTidemark.Cli.exe initialize server-name:cxo-dev-sql02 database-name:CXO.Adapter.LongviewTidemark.Configuration authentication-type:Proprietary username:cxo password:somePassword disable-encryption: yes

  3. Run the set-authentication-settings command to set up the identity provider values.

    Note: UserGroup specified in "idp-client-allowed-user-group" should be created in CXO. Only users from that group are allowed to open CXO Longview Adapter.

    Command set-authentication-settings
    Parameters

    • idp-authority: URL to IDP setup

    • idp-client-id: The client id set in IDP

    • idp-client-secret: The client secret from IDP

    • idp-client-allowed-user-group: The user group that is allowed to use the Longview Adapter
    Example

    .\CXO.Adapter.LongviewTidemark.Cli.exe set-authentication-settings idp-authority:https://cxoUrl/idp idp-client-id:LongviewClientUI idp-client-secret:secret idp-client-allowed-user-group:ADM

  4. Restart the Application Pool for Longview.

Creating a Longview Source

  1. Create a new source system in the SSM for the correct source type: Longview to create:

    • Fact database

    • SSAS cube

    • It’s recommended to use the same source name in the SSM as in the command below, otherwise scheduling extractions will not work

  2. Run the create-source-in-adapter command to create a new Longview source.

Important: At this point you can decide the type of Longview source as either Longview Close or Longview Tax. This selection cannot be changed after source creation!

Longview Plan and Longview Close work the same way. Similarly, Longview Tax and Transfer Pricing work the same way. But if you want to integrate with Longview Plan, you need to select Longview Close, and if you want to connect to Transfer Pricing, you will have to select Longview Tax.

Command create-source-in-adapter
Parameters

  • source-type: longview-close/longview-tax

  • source-name: Name of source to be created. This should be the same name as was used in the SSM

  • factdb-name: Name of the fact database that was created via SSM

  • factdb-server: SQL server on which the fact database is hosted

  • factdb-authentication-type: Integer value indicating how to authenticate with fact database: 0 = proprietary, 1 = windows.

  • factdb-username (optional): SQL username in case of proprietary authentication

  • factdb-password (optional): SQL password in case of proprietary authentication

  • ssas-server-name: SQL server on which the SSAS cube is hosted

  • ssas-database-name: name of the SSAS database

  • ssas-cube-name: name of the SSAS cube within the database, should be "CXO" for regular scenarios.

  • first-period (optional): the first period in case the customer works with a broken book year. Example: Apr.

    Note: Currently only works for Longview-Close sources.

  • disable-encryption (optional): Set to yes to disable database encryption
Example

.\CXO.Adapter.LongviewTidemark.Cli.exe create-source-in-adapter source-type:longview-close source-name:MyLongviewCloseSource factdb-name:cxo_fact_MyLongviewCloseSource factdb-server:cxo-dev-sql02 factdb-authentication-type:1 ssas-server-name:cxo-dev-as01 ssas-database-name:MyLongviewCloseSource ssas-cube-name:CXO first-period:Apr disable-encryption: yes

After running the above commands, the adapter is configured, and a first source is available. When multiple sources are required, run the create-source-in-adapter command for each source that is required.

Each source is created with a default configuration for dimensions, Longview symbol names, etc. These defaults need to be changed for the source to function properly. This is explained in Longview Adapter User Interface.

Was this article helpful?

We're sorry to hear that.