|Table of Contents|
Long Term Support
Stable, tested ServerTemplate assets
Use the DB SQLS Create login operational script to create a new SQL Server user (login) and password for your application's use. Enter the following RightScript inputs before running this script.
Note: It's recommended that you set up credentials for password values and any other sensitive data as shown in the examples below.
|Input Name||Description||Example Values|
|DB_NAME||Default database to assign to the new SQL Server user.||Text:MyDatabase|
|DB_NEW_LOGIN_NAME||User name for the new SQL Server user.|| |
|DB_NEW_LOGIN_PASSWORD||Password for the new SQL Server user.||Cred:SQL_SERVER_PASSWORD|
|DB_REMOTE_SERVER_IP||IP address of the target SQL Server. The script assumes that the default SQL Server port, 1433, is used for server communications.||Text:220.127.116.11|
|DB_REMOTE_SQL_LOGIN||Login ID for a SQL Server user with administrative permissions, used to create the new application-specific user account.||Cred:SQL_APPLICATION_USER|
|DB_REMOTE_SQL_PASSWORD||Login password for a SQL Server user with administrative permissions.||Cred:SQL_APPLICATION_PASSWORD|
To run your IIS server in conjunction with an Amazon Elastic Load Balancer (ELB), you must follow the steps below:
Note: If your ELB will uses the HTTPS protocol, refer to the next section for information on generating the required server certificate and private key files in PEM format.
To use the HTTPS (HTTP with SSL/TLS) protocol, the ELB and HAProxy load balancers require a server certificate and private key in X.509/PEM format.
IIS server certificates are typically exported in .pfx (PKCS#12) format. However, you can generate a PEM-formatted certificate and private key files for the load balancers using the SYS Convert PFX operational script, in conjunction with a .pfx (PKCS#12 format) server certificate file, included as a script attachment, and the following inputs:
It's recommended that you create credentials to hide the sensitive values for these inputs for security reasons.
The SYS Convert PFX script saves your PEM-formatted certificate and key files as public.crt and private.pem, in the C:\Certificates directory on the IIS server.
In Amazon and Rackspace environments, the SYS Configure IIS logs rotation policy boot script sets up a Windows scheduled task on your IIS server, which runs daily and archives any log entries older than one day to an ROS container (e.g. Amazon S3 bucket or Rackspace Cloud Files container) based on the REMOTE_STORAGE_ACCOUNT_PROVIDER input.
The SYS upload IIS logs operational script lets you manually run an IIS log archive on demand. The same inputs that are used for the SYS Configure IIS logs rotation policy script are used.
By default, the IIS Download application code boot script places the application code into the following directory by default: C:\inetpub\wwwroot\release\<GMT-timestamp>
If the application code is located in a different directory, run the IIS Switch default website operational script and specify the correct path using the OPT_DEFAULT_SITE_ROOT_PATH input so that IIS knows the new location of the application code.
To learn more about the following topics that apply to all Windows-based ServerTemplates published by RightScale, please see Base ServerTemplate for Windows - Overview.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.