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
$connection.Open()

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()
$sqlReader.Read()

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

$sqlReader.close()

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 licenses.id = $license_id"
$sqlCmd.CommandText = $query_lock
$sqlCmd.Transaction = $transaction
$result = $SqlCmd.ExecuteNonQuery()
Write-Host "Result UPDATE: " $result

Write-Host "End Transaction"
$transaction.Commit()
$connection.Close()

LogWrite("New hostname selected.")
LogWrite($newHostName)

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("http://169.254.169.254/latest/meta-data/instance-id")
$Tag = New-Object amazon.EC2.Model.Tag
$Tag.Key = "Name"
$Tag.Value = $license_hostname
New-EC2Tag -Resource $instanceId -Tag $Tag



Comments

Anonymous said…
Without a doubt, though, one of many consistently hottest playing video games of all time is actual roulette. It's a game the place a player can attain unbelievable highs and lows – it's one of the most risky playing video games thus far. Its reputation has spawned a number of} variants on the game's rules, including European, American, French, and lots of|and a 점보카지노 lot of} others.

Popular posts from this blog

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

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: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , 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

Event System to Create Mapped Structure Groups for Binary Publish

As a continuation of last week's Publish Binaries to Mapped Structure Group , this week's TBB is in fact the Event System part of that solution. Make sure you do check out the previous post first, which explains why and what this Event System does. To reiterate, the Event System intercepts a Multimedia Component save, take its Folder path and create a 1-to-1 mapping of Structure Groups. The original code was written, again, by my colleague Eric Huiza : [ TcmExtension ( "MyEvents" )] public class EventsManager  : TcmExtension {     private Configuration configuration;     private readonly Regex SAFE_DIRNAME_REGEX = new Regex ( @"[\W_]+" );     public EventsManager() {         ExeConfigurationFileMap fileMap = new ExeConfigurationFileMap ();         fileMap.ExeConfigFilename = Path .GetDirectoryName( Assembly .GetExecutingAssembly().Location) + "\\EventSystem.config" ;         configuration = ConfigurationManager