Versions Compared

Key

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

...

  • CXO Version 21.3.3 (or higher)

  • .NET 56.0 or higher has to be installed

  • Longview version 21.2 or newer

...

Info

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)

Example

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

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

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

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

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

...

To update the connection fields, run the following command with the correct values and source name. When certain values do not need to be replaced, remove those parameters. Especially use this command when updating password. If password is updated by SQL update query it will not be encrypted, running this command updates and encrypts the password.

Command

set-lv-source-configuration

Parameters

  • source: Name of source for which longview connection is set

  • url (optional): Longview connection URL

  • username (optional): Longview connection username

  • password (optional): Longview connection password

  • listener-port (optional): Longview connection listener port

  • access (optional): Longview connection access

  • user-group (optional): Longview connection user group

  • instance-id (optional): Longview connection instance id

Example

.\CXO.Adapter.LongviewTidemark.Cli.exe set-lv-source-configuration source:MyLongviewTaxSource url:http://longview.tax.com username:daniel password:secret_password listener-port:8000 access:V3_COMPATIBLE_ACCESS user-group:Admin instance-id:LVTax

.\CXO.Adapter.LongviewTidemark.Cli.exe set-lv-source-configuration source:MyLongviewTaxSource password:secret_password

.\CXO.Adapter.LongviewTidemark.Cli.exe set-lv-source-configuration source:MyLongviewTaxSource

Other option to update the connection fields is by running the following query with the correct values and source name. When certain values do not need to be replaced, remove those lines from the query. This update query should not be used for updating the Password value since it will not be encrypted. Use the above command for updating password.

...

Update Symbol Names, Symbol Attributes and Dimension Description which are yet to be configured.

Remove a Dimension Mapping

To remove a dimension mapping from a Longview dimension to a CXO dimension, run the following query with correct values for LVSourceConfigurationId and CxoDimension (run QUERY 3).

QUERY 7For Longview plan and close, the time period dimension is by default mapped to the other three dimensions, Year, Period, and View. To add a 4th dimension (usually category) run the following query:

QUERY 7

Code Block
languagesql
update	DimensionMapping
set		LVDimensionName = 'TimePer'
where	LVSourceConfigurationId = @lv_source_configuration_id
and		CxoDimension = 'CAT'

Update Symbol Names, Symbol Attributes and Dimension Description which are yet to be configured.

Note: Depending on the Longview installation and configuration TimePer could be named under a different identifier. Other names could be ‘Timeper’, ‘TIMEPER’, ‘Timeperiods’. to check this name, run the following query:

Code Block
languagesql
select LVDimensionName
from DimensionMapping
where
LVSourceConfigurationId = @lv_source_configuration_id
and CxoDimension in ('YER', 'PER', 'VIW')
group by LVDimensionName

Remove a Dimension Mapping

To remove a dimension mapping from a Longview dimension to a CXO dimension, run the following query with correct values for LVSourceConfigurationId and CxoDimension (run QUERY 3).

QUERY 8

Code Block
languagesql
declare @lv_source_configuration_id uniqueidentifier = 'LV SOURCE CONFIGURATION ID HERE';
declare @cxo_dimension varchar(50) = 'CXO DIMENSION HERE';
declare @lv_dimension_name varchar(255) = (
    select LVDimensionName 
    from DimensionMapping 
    where LVSourceConfigurationId = @lv_source_configuration_id 
    and CxoDimension = @cxo_dimension
);

update  DimensionMapping
set     LVDimensionName = NULL
where   LVSourceConfigurationId = @lv_source_configuration_id
and     CxoDimension = @cxo_dimension

delete from LVDimensionsExtractionConfiguration
where   LVSourceConfigurationId = @lv_source_configuration_id 
and     DimensionName = @lv_dimension_name

...

To update symbol names, symbol attributes and dimension description for a LV dimension, run the following query with the correct LVSourceConfigurationId and DimensionName (run QUERY 4).

QUERY 89

Code Block
languagesql
update  LVDimensionsExtractionConfiguration
set     SymbolNames = '...',
		SymbolAttributes = '...',
		DimensionDescription = '...'
where   LVSourceConfigurationId = 'LV SOURCE CONFIGURATION ID HERE'
and     DimensionName = 'DIMENSION NAME HERE'

...

To create a new member attribute mapping for a specific dimension, run the following query with the correct DimensionMappingId (run QUERY 5).

QUERY 910

Code Block
insert into MemberAttributeMapping 
    (Id, DimensionMappingId, CxoMemberAttribute, SymbolAttribute)
values (
    newid(), 
    'DIMENSION MAPPING ID HERE', 
    'CXO MEMBER ATTRIBUTE HERE', 
    'SYMBOL ATTRIBUTE HERE')

...

To remove an existing member attribute mapping, run the following query with the correct DimensionMappingId and SymbolAttribute (run QUERY 5).

QUERY 1011

Code Block
languagesql
delete from MemberAttributeMapping
where DimensionMappingId = 'DIMENSION MAPPING ID HERE'
and   SymbolAttribute = 'SYMBOL ATTRIBUTE HERE'