Skip to main content

License Management

Image
By
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



Labels:

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.
05 December, 2022 01:39
Post a Comment

Popular posts from this blog

Running sp_updatestats on AWS RDS database

By
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...
2 comments
Read more

REL Standard Tag Library

By
The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...
2 comments
Read more

Publish Binaries to Mapped Structure Groups

By Unknown
Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...
10 comments
Read more