Only global administrators and Solution Manager administrators can create new environments. More information is available in the Authorization section.
In Denodo Standard, you can only create one environment per license scenario. See also Restrictions of Denodo Standard.
The first step to populate the catalog of the Solution Manager with a model of your infrastructure is to create an environment. To do this, click the root node of the catalog tree and click on the emerging menu.
Provide the following information:
Name: Name of the environment. You cannot change the name of an environment after creating it.
Description: Description of the environment.
License scenario: From the available scenarios of the current license installed in the Solution Manager, which one is assigned to this environment. This parameter will affect the capacities of the servers that belong to the environment. More information is available in the License Management section.
Recommended update: Minimum update of the Denodo platform, expressed with the format
yyyymmdd(e.g. 20181231), that will be required to any Virtual DataPort Administration Tool that connects to a Virtual DataPort Server from this environment.
URL of the recommended update: URL where the recommended update is available to download. In case a Virtual DataPort Administration Tool does not fulfill the minimum update required by the field Recommended update, a message will suggest this URL so the user can download it.
Recommended update is mandatory in the Administration Tool: When this field is checked, any Virtual DataPort Administration Tool that does not have the recommended update installed will not be able to connect to the server. Otherwise, it will only be notified.
Access Key ID: The access key ID used to create all the resource. This is an optional field that overrides the global AWS authentication.
Secret access key: The secret access key used to create all the resource. This is an optional field that overrides the global AWS authentication.
AWS Region: The AWS region where all the resources will be created. Please check AWS regions for further details.
When the Solution Manager is running in an EC2 instance, only the regions it belongs to are listed.
VPC: Virtual Private Cloud to use for this environment, this is the virtual network that will be used for the resources. You can always choose an existing VPC. Additionally, when the Solution Manager is running in an EC2 instance, you can create a new VPC specifying the CIDR block and the name. Please check AWS VPCs for further details.
When you create a new VPC or select an existing VPC different from the VPC where the Solution Manager instance is running, Solution Manager will automatically configure a VPC peering connection to ensure connectivity between the new VPC and the Solution Manager VPC. Please check VPC peering for further details.
If you want to use another option to connect the Solution Manager VPC and the servers VPC when they are in different VPCs, you can disable the automatic VPC peering connection creation and configuration. In order to do this, add the following property to the Solution Manager server configuration file (located in SM_HOME/conf/solution-manager/SMConfigurationParameters.properties) and restart the Solution Manager server: com.denodo.solutionmanager.cloud.aws.vpcPeeringConnectionEnabled=false