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 6 Next »

Installation Prerequisites

  • CXO Version 21.3.3 (or higher)

  • .NET 5.0 has to be installed

Installation

  • Install Longview Adapter

CXO configuration and Source Creation

Note: To be able to use the Longview Adapter you need a license key with Longview enabled.

  • Create a new source system in the SSM for the correct source type: Longview. This should create:

    • Fact database

    • SSAS cube

  • In the next steps you will run a few commands to initialize the Longview adapter and the source. These commands need a few parameters for input, please avoid using spaces in the parameter values.
    For more information on the available commands and their parameters, run the CXO.Adapter.LongviewTidemark.Cli.exe help command for detailed descriptions.

  • Open command line as Administrator, browse to the Longview adapter folder and run the initialize command to create the configuration database.

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)

Example

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

  • Then run the create-source-in-adapter command to create a new Longview source.

    IMPORTANT: Here you decide the type of Longview source: Longview Close or Longview Tax. This cannot be changed after source creation!

Command

create-source-in-adapter

Parameters

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

  • source-name: name of source to be created

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

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

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

  • 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. The next section explains how to configure the Longview sources.

Longview Source Configuration

A newly created Longview source needs additional configuration to function properly. Since the Longview adapter currently does not have a user interface, these configurations have to be done by running SQL scripts on the Longview configuration database.

Longview Connection

To show the currently configured connection information for the sources in the Longview adapter, run the following query on the configuration database:

select  s.Name, 
        Type = CASE 
             WHEN s.Type =  1 THEN 'Longview Close'
             WHEN s.Type =  2 THEN 'Longview Tax'
             ELSE 'Unknown'
        END,
        sc.Url,
        sc.UserName,
        sc.Password,
        sc.ListenerPort,
        sc.Access, 
        sc.UserGroup,
        sc.InstanceId
from    Source s
join    LVSourceConfiguration sc on sc.SourceId = s.Id

The results of this query shows per source the URL to the Longview instance, the username and password to authenticate with the Longview system and a few other Longview-specific fields. The values for these fields should be provided by people managing the Longview system to connect to.

To update the connection fields run the following query with the correct values and source name. When certain values do not need to be replaced, remove the particular lines from the query.

update  sc
set     sc.Url = '...',
        sc.UserName = '...',
        sc.Password = '...',
        sc.ListenerPort = 0,
        sc.Access = '...',
        sc.UserGroup = '...',
        sc.InstanceId = '...'
from    LVSourceConfiguration sc
join    Source s on sc.SourceId = s.Id
where   s.Name = 'SOURCE NAME HERE'

An example to replace just the URL and credentials for a source called MyLongviewSource:

update  sc
set     sc.Url = 'https://example-url-to-longview-source.com',
        sc.UserName = 'Administrator',
        sc.Password = 'secret_password'
from    LVSourceConfiguration sc
join    Source s on sc.SourceId = s.Id
where   s.Name = 'MyLongviewSource'

Dimension Configuration

To show the currently configured dimension mappings for a given source run the following query with the correct source name:

select  dm.LVSourceConfigurationId, 
        dm.CxoDimension, 
        dm.LVDimensionName 
from    Source s
join    LVSourceConfiguration sc on sc.SourceId = s.Id
join    DimensionMapping dm on dm.LVSourceConfigurationId = sc.Id
where   s.Name = 'SOURCE NAME HERE'

This shows which Longview dimension is mapped to which CXO dimension. If the LVDimensionName column has a NULL value, nothing is mapped to this CXO dimension.

To update a dimension mapping for a given source run the following query with correct values for LVSourceConfigurationId and CxoDimension (you get these from running the select query above) plus the name of the LV Dimension you want to map.

update  DimensionMapping
set     LVDimensionName = '...'
where   LVSourceConfigurationId = 'LV SOURCE CONFIGURATION ID HERE'
and     CxoDimension = 'CXO DIMENSION HERE'

  • No labels