Use the PowerShell scripts at your disposal to define your complete delivery infrastructure and map it to your Content Manager instance(s). You can also performs the steps in this task in one go by running the PowerShell script %TRIDION_HOME%\bin\Configure-NewStyle-Publishing.ps1, but that script interactively prompts you for every parameter listed under every individual script below. This task is typically performed by the Business IT department of your organization.
Procedure
- On your Topology Manager server machine, open a PowerShell prompt.
- Define your Topology Type by running the following command:
Add-TtmCdTopologyType -Id TOPOLOGYTYPEID -Name TOPOLOGYTYPENAME -EnvironmentPurposes "PURPOSES"
where:
- TOPOLOGYTYPEID is a unique ID for this Topology Type, for example,
StagingAndLive.
- TOPOLOGYTYPENAME is the display name of this Topology Type, for example,
"Staging & Live".
- PURPOSES is a comma-separated list of the Purposes of this Topology Type, for example,
Staging, Live.
- Define your Content Delivery environments by running the following command on one line (once for each Content Delivery environment):
Add-TtmCdEnvironment -Id CDENVIRONMENTID -EnvironmentPurpose CDENVIRONMENTPURPOSE
-DiscoveryEndpointUrl DISCOVERYENDPOINTURL -AuthenticationType AUTHTYPE
where:
- CDENVIRONMENTID is a unique ID for this Content Delivery environment, for example,
CdServerFarm03.
- CDENVIRONMENTPURPOSE is one of the Purposes defined for the Topology Type, for example,
Live or Staging.
- DISCOVERYENDPOINTURL is the URL of the Discovery Endpoint URL for this Content Delivery environment, for example, http://discovery.example.com.
- AUTHTYPE is the type of authentication used to access the Discovery Endpoint URL: either
Anoynmous or OAuth. If you set the parameter to OAuth, a ClientId parameter and a ClientSecret parameter need to be supplied as well.
- Define your Topology (or Topologies) by running the following command (once for each Topology):
Add-TtmCdTopology -Id TOPOLOGYID -Name TOPOLOGYNAME -CdTopologyTypeId TOPOLOGYTYPEID -CdEnvironmentIds CDENVIRONMENTIDS
where:
- TOPOLOGYID is a unique ID for this Topology, for example,
CloudTopology.
- TOPOLOGYNAME is the display name of this Topology, for example,
"Cloud Topology".
- TOPOLOGYTYPEID is the unique ID of the Topology Type of this Topology, for example,
StagingAndLive.
- CDENVIRONMENTIDS is a comma-separated list of Content Delivery environments, for example,
CdServerFarm02, CdServerFarm04.
- Define the Web site associated with a Content Delivery environment by running the following command (once for each Web site):
Add-TtmWebsite -Id WEBSITEID -CdEnvironmentId CDENVIRONMENTID -BaseUrls "BASEURLS"
where:
- WEBSITEID is a unique ID for the Web site, for example,
StagingWebsite.
- CDENVIRONMENTID is the unique ID of one of the Content Delivery environments, for example,
CdServerFarm17.
- BASEURLS is a comma-separated list of base URLs (enclosed in double quotes) for this Web site, for example,
"http://myserver:8082/, http://16.7.2.33/".
The sites you define appear in the Sites slide-out navigation screen. Each site automatically contains a default Web application with an empty context URL (that is, a context URL of /). The ID of this Web application (which you will need when you map a Publication to a Web application) is the ID of the Web site, followed by the string _RootWebApp. So if WEBSITEID above was set to StagingWebsite, the ID of the default Web application would be StagingWebsite_RootWebApp.
- If you want to define other Web applications in addition to the default one for a Web site, define the additional Web application(s) associated with each Web site by running the following command (once for each additional Web application):
Add-TtmWebApplication -Id WEBAPPID -WebsiteId WEBSITEID -ContextUrl "CONTEXTPATH"
where:
- WEBAPPID is a unique ID for the Web application, for example,
StagingMicrosite01.
- WEBSITEID is the unique ID of the Web site in which this Web application runs, for example,
StagingWebsite.
- CONTEXTURL is the Web folder path to this Web application, relative to the Web site's base URL, for example,
"/microsite/". If your Publication that maps to this Web application publishes to the file system, the value of ContextUrl must match the Publication Path property of that Publication, as found in its General tab.
Results
Your delivery infrastructure is now configured in Topology Manager. You can see the environments and their properties in the
Topology Management slide-out navigation screen in Content Manager Explorer and Experience Manager. The next step is for Web content managers to use Business Process Types in their Publications, to enable publishing to one or more Purposes. Additionally, specific Publications need to be mapped to specific Web applications in the Content Delivery environments. Web content managers can do this themselves by using the Site Wizard, or they can ask Business IT to run the
Add-TtmMapping script.