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

Scaling Policies

By
This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the
Post a Comment
Read more

Toolkit - Dynamic Content Queries

By
This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio
Post a Comment
Read more

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
1 comment
Read more