Skip to main content

License Management

This post is part of a bigger topic Autoscaling Publishers in AWS.

Tridion Publishers need a license that matches the name of the host machine they run on. Each Publisher must have a different name. This means that when using autoscaling, we must know in advance which license to copy into the instance (at first start up time) and also we must rename that machine's hostname to match the license. This is needed because otherwise the instance machine name is always the one set in the AMI.

The script below executed by the Amazon Launch Configuration service when the publisher instance starts. It is backed by a database that contains the available licenses, each with a host name. The script takes the first license available and then changes the host name to match the name specified in the license.

Additionally, the script then downloads the correct license files from their s3 location and copies them in the right folder under the Tridion installation.

Finally the script instructs the server to join the Active Directory domain that is supposed to be part of. This logic is tricky, and sometimes it doesn't work within a single server restart. So two restarts might be needed: first to change the host name, then second to join the domain.

The license that is used is marked as 'unavailable', so the next instance of publisher that starts up cannot use the same license again. We will see in a later post that when a publisher is decommissioned, the license is marked as available again and the db table is updated accordingly.

$connectionString = "Server=$dataSource;uid=$user; pwd=$pwd;Database=$database;Integrated Security=False;"
$query = "SELECT * FROM licenses WHERE licenses.available = 'true' and licenses.type = 'publisher'"

$connection = New-Object System.Data.SqlClient.SqlConnection
$connection.ConnectionString = $connectionString

Write-Host "Begin SQL Transaction"
$transaction = $connection.BeginTransaction("LicenseTransaction")

$sqlCmd = New-Object System.Data.SqlClient.SqlCommand
$sqlCmd.CommandText = $query
$sqlCmd.Transaction = $transaction
$sqlCmd.Connection = $connection
$sqlReader = $sqlCmd.ExecuteReader()

$license_id = $sqlReader["id"]
$license_hostname = $sqlReader["hostname"]
$license_file = $sqlReader["license_file"]
$license_cd_file = $sqlReader["license_cd_file"]


Write-Host $license_id
Write-Host $license_hostname
Write-Host $license_file
Write-Host $license_cd_file

$query_lock = "UPDATE licenses SET licenses.available = 'false' WHERE = $license_id"
$sqlCmd.CommandText = $query_lock
$sqlCmd.Transaction = $transaction
$result = $SqlCmd.ExecuteNonQuery()
Write-Host "Result UPDATE: " $result

Write-Host "End Transaction"

LogWrite("New hostname selected.")

aws s3 cp $license_file "D:\SDL Web\bin\license.xml"
aws s3 cp $license_cd_file "D:\SDL Web\config\cd_licenses.xml"

echo "Selected hostname is: "$license_hostname
LogWrite("Creating Name tag...")
Set-DefaultAWSRegion $AWSRegion
$client = New-Object System.Net.WebClient
$instanceId = $client.DownloadString("")
$Tag = New-Object amazon.EC2.Model.Tag
$Tag.Key = "Name"
$Tag.Value = $license_hostname
New-EC2Tag -Resource $instanceId -Tag $Tag


Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: I stumbled upon the following post from 2008 (!!!), , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven