|
|
Copy the encrypted password to a notepad for easy copy/paste to replace the value of the .<Encrypted PAI Schema Password> property and servigistics.analytics.sf.dbpassword property.
|
|
|
If the Servigistics dbupgrader is not installed on the WebUI server, this step needs to be done on the server where the Servigistics dbupgrader resides.
|
|
Property Name
|
Value
|
Tip
|
|---|---|---|
|
servigistics.analytics.jarurl
|
Path to svg-snowflake-analytics-<version>.jar on the server in the format:
file:<jar path>
|
file:C:/SPO12.1.1.2/PAI/Jar/svg-snowflake-analytics.jar
|
|
servigistics.analytics.sf.dburl
|
URL of database containing the schema for the analytics data
|
jdbc:snowflake://<account>.<region>.snowflakecomputing.com
|
|
servigistics.analytics.sf.dbusername
|
Username for the analytics schema having read/write permission
|
The Snowflake username
|
|
servigistics.analytics.sf.dbpassword
|
Encrypted password
|
Enter the encrypted password generated in step 8
|
|
servigistics.analytics.sf.dbdriver
|
Snowflake JDBC Driver
|
net.snowflake.client.jdbc.SnowflakeDriver
|
|
servigistics.analytics.sf.dbtype
|
snowflake
|
|
|
servigistics.analytics.sf.warehouse
|
Snowflake warehouse for compute resources
|
Created in the Creating the Snowflake Resources step
|
|
servigistics.analytics.sf.database
|
Snowflake database where your schema resides
|
Created in the Creating the Snowflake Resources step
|
|
servigistics.analytics.sf.schema
|
Snowflake schema where your database tables reside
|
Created in the Creating the Snowflake Resources step
|
|
servigistics.analytics.sf.internalStageName
|
Snowflake stage where CSV files are stored
|
Destination on the Snowflake platform where CSV files are uploaded. Created in the Creating the Snowflake Resources step
|
|
servigistics.analytics.sf.csvpath
|
AutoPilot server accessible file path to write the exported CSV files
|
There must be enough available space to store all Servigistics exported data for one entire Analytics run. If there are multiple AutoPilot servers this parameter needs to specify a shared drive with read/write permissions.
|
|
servigistics.analytics.fillrate.horizonDays
|
30
|
Defines the number of days in the past to calculate fill rate
|
|
servigistics.analytics.pi.demandmiss.calc.horizonslices
|
Default is 12
|
Determines the horizon for past period for Unplanned Missed calculation.
|
|
servigistics.analytics.pi.demandmiss.retainslices
|
Default is 6
|
Determines the number of periods in months to retain to be used for Unplanned Missed calculation.
|
|
servigistics.analytics.sf.csvFileSplitRowCount
|
Not less than 10,000. The recommended value is 500,000
|
The value that specifies the maximum number of rows to be written to a CSV file when creating files containing data to load into Snowflake. Multiple CSV files are created if the number of rows exceeds the value specified. This improves performance in Snowflake when files are larger than 1 GB in size.
|
|
|
If the Servigistics dbupgrader is located on a different server than the WebUI server, the files in this step need to be copied to the server where dbupgrader resides.
|
|
|
Copy the encrypted password to a notepad for easy copy/paste to replace the value of the .<Encrypted PAI Schema Password> property and servigistics.analytics.dbpassword property.
|
|
|
If the Servigistics dbupgrader is not installed on the WebUI server, this step needs to be done on the server where the Servigistics dbupgrader resides.
|
|
Property Name
|
Value
|
Tip
|
|---|---|---|
|
servigistics.analytics.jarurl
|
Path to svg-snowflake-analytics-<version>.jar on the server in the format:
file:<jar path>
|
file:C:\SPO12.1.1.2\PAI\Jar\svg-snowflake-analytics.jar
|
|
servigistics.analytics.sf.dburl
|
URL of database containing the schema for the analytics data
|
jdbc:snowflake://<account>.<region>.snowflakecomputing.com
|
|
servigistics.analytics.sf.dbusername
|
Username for the analytics schema having read/write permission
|
The Snowflake user
|
|
servigistics.analytics.sf.dbpassword
|
Encrypted password
|
Enter the encrypted password generated in step 9
|
|
servigistics.analytics.sf.dbdriver
|
Snowflake JDBC Driver
|
net.snowflake.client.jdbc.SnowflakeDriver
|
|
servigistics.analytics.sf.dbtype
|
snowflake
|
|
|
servigistics.analytics.sf.warehouse
|
Snowflake warehouse for compute resources
|
Created in the Creating the Snowflake Resources step
|
|
servigistics.analytics.sf.database
|
Snowflake database where your schema resides
|
Created in the Creating the Snowflake Resources step
|
|
servigistics.analytics.sf.schema
|
Snowflake schema where your database tables reside
|
Created in the Creating the Snowflake Resources step
|
|
servigistics.analytics.sf.internalStageName
|
Snowflake stage where CSV files are stored
|
Destination on the Snowflake platform where CSV files are uploaded. Created in the Creating the Snowflake Resources step
|
|
servigistics.analytics.sf.csvpath
|
AutoPilot server accessible file path to write the exported CSV files
|
There must be enough available space to store all Servigistics exported data for one entire Analytics run. If there are multiple AutoPilot servers this parameter needs to specify a shared drive with read/write permissions.
|
|
servigistics.analytics.fillrate.horizonDays
|
30
|
Defines the number of days in the past to calculate fill rate
|
|
servigistics.analytics.pi.demandmiss.calc.horizonslices
|
Default is 12
|
Determines the horizon for past period for Unplanned Missed calculation.
|
|
servigistics.analytics.pi.demandmiss.retainslices
|
Default is 6
|
Determines the number of periods in months to retain to be used for Unplanned Missed calculation.
|
|
servigistics.analytics.sf.csvFileSplitRowCount
|
Not less than 10,000. The recommended value is 500,000
|
The value that specifies the maximum number of rows to be written to a CSV file when creating files containing data to load into Snowflake. Multiple CSV files are created if the number of rows exceeds the value specified. This improves performance in Snowflake when files are larger than 1 GB in size.
|
|
|
If the Servigistics dbupgrader is located on a different server than the WebUI server, the files in this step need to be copied to the server where dbupgrader resides.
|