Using CA AppLogic › Appliance Developer Guide › Appliance OS Installations › Windows Installations › Windows OS › Windows SQL and IIS › SQL12

SQL12

You can create a Windows Server Appliance for the Windows Server 2012 Base Server Class. SQL12 family of appliances are built on top of generic Windows 2012 Server or Windows 2008 R2 Server appliances.

Note: In the following instructions:

• For WIN12y, the y placeholder is for the Windows edition, such as Standard or DataCenter, that the appliance or application is based on.
• For SQL12y_12, the y placeholder is for the SQL edition, such as S for Standard, E for Enterprise, BI for Business Intelligence, that the appliance is based on. All the SQL editions used to create the SQL12y_12 appliances are based on the SQL Server 2012.

Install and Configure the Appliance

Follow these steps:

1. Create the Windows Server appliance WIN12y for the Windows Server 2012 Base Server Class.
2. Create a new singleton from the specified base class, such as WIn12S.
   1. Create a new application that includes an instance of the base class.
   2. Branch the class.
   3. Right click the class, then select Resources, then assign 1 to the CPU and 1GB of Memory.
3. Start the application
4. SSH into the singleton using the graphic console of the singleton.
   1. Select the singleton, then click the Login (graphic) icon.
   2. Set a new Administrator password (net user administrator password - select a password).
5. In the GUI, stop the application.
6. Right-click appliance and select Modify Boundary, then select the Volumes tab.
   1. Resize the singleton boot volume to 20 GB. This is an approximate size. The typical SQL install requires 4 to 5 GB of free disk space. After this install, there should be approximately 1 GB of free space on the singleton boot volume. Adjust the size according to the free space on your singleton.
   2. Add a new placeholder volume with the name data and mount on D:\. Mark it as mandatory.
7. Right-click the canvas and select Manage Volumes.
   1. Add an application volume to use temporarily as the placeholder volume with the filesystem: ntfs08 and size: 8GB.
8. Start the application.
9. Click the Login (graphic) icon and login to the graphic console of the singleton as Administrator.
10. Enable virtual memory for the appliance:
    1. Select Start, Control Panel, System (System and Security), Advanced systems settings, Advanced, Performance Settings, Advanced, Virtual memory, Change.
    2. Leave the C drive with no paging file and set the D drive to use a system managed page file size.
    3. Click Set.

    Do not close the graphic console.

11. In the GUI, restart the application.
12. Access the graphic console and complete the following steps.
13. Install the version of SQL Server 2012. A complete distribution source should be used: ISO-image or a full redistributable package.

    If you are downloading an extractable archive of SQL Server 2012, download and extract it on the D volume. When using an ISO-image, you can mount the image as a separate drive or extracted on D, then installed to C.

14. Extract the redistributable package as in the following example:

    en_sql_server_2012_express_edition_with_tools_with_sp1_x86.exe /Q /X:D:\ 
    

15. Use the SQL setup configuration file ConfigurationFile2012.ini and launch the installation as following:

    setup.exe /q /IAcceptSQLServerLicenseTerms /action=Install /configurationfile=D:\ConfigurationFile2012.ini /sapwd="manager" /ASSYSADMINACCOUNTS="%COMPUTERNAME%\Administrator" /SQLSYSADMINACCOUNTS="%COMPUTERNAME%\Administrator" "NT AUTHORITY\SYSTEM" /TCPENABLED=1
    

    Point MEDIASOURCE on the root of the SQL installation folder.

    Note: If SQL installation requires .NET framework enabled, then access server manager, features. Enable .NET framework 3.5.1 feature and run the above installation command again.

16. Install the SQL exe. This self-executing installer can be downloaded from the grid controller through the default interface of the singleton. This interface has already been properly configured through DHCP.
    1. To locate the internal IP address of the controller, open a command line shell and execute the following. Note the IP address of the DHCP server for the last enumerated interface. For example, Local Area Connection 5:

       ipconfig /all
       

    2. Point IE at http://IP-address:8080/download/ and download the current Windows SQL exe. For example, SQL_Windows-*.exe: Right-click the exe file and select Save Target As to download the file to the desktop.
    3. Double-click the exe file on the desktop to perform the installation.
    4. Delete the exe file and empty the Recycle Bin.
17. If there are junction points on the volume, delete junction points to prevent Windows volume resize failures.

    Search for junction points using the command prompt.

    dir/S /A:L
    

    The output reports the path for any junction points.

    The following are examples of junction points on a Windows boot volume. The names on your volumes can differ.

    • WINDOWS\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\
    • WINDOWS\assembly\GAC_MSIL\IEExecRemote\2.0.0.0__b03f5f7f11d50a3a\
18. Run services.msc and start MYSQL Server service, if not started.
19. Clean-up drive D by removing all SQL-related installation files, including the setup configuration file.
20. In a Cygwin bash shell
    1. Set a new complex password. Ffor example, net user administrator pq398hpaowht0293j^LWOIFH9htfw9jfe.
    2. Exit the SSH session.
21. SSH into the singleton using the graphic console of the singleton and execute the following command:

    rm -f ~/.bash_history /appliance/passwd.stamp. 14. 
    

22. Close the graphic console.
23. In the GUI, stop the application.
24. Right click the appliance and select Modify Boundary.
    1. In the General tab, edit the class as follows:
       • In the Name field, change the class name to SQL12y_12.This is the name that displays on the icon in the catalog.
       • Verify the Instance Name Template field is blank. The name of the instance is generated when you drag the icon on the canvas.
       • In the Category field, change class category to Database Appliances
       • Enter a class description in the Description field. The description should describe the class and, typically, include the version of the main appliance package, such as SQL Server Appliance - based on Windows Server 2012 Datacenter Edition and SQL Server 2012 Enterprise v1.0.0-1.
       • In the Documentation URL field, enter the following:

         http://doc.3tera.com/AppLogicxx/index.htm?toc.htm?CatDatabaseAppliancesSQL.html

         where xx indicates the correct version of AppLogic

       • In the Visual Attributes section, change the class icon color to Red in the Color field and adjust the icon size, as needed.
    2. Select the Interface tab.
       • Delete the net and out terminals.
       • Define the interfaces as follows.

1. Click OK to apply changes. The Interface Editor displays.

1. Right-click the singleton, then select Attributes.
   1. In the Name field, change the instance name to SQL12y_12.
   2. Select the Properties tab and add the following properties.

c. Select the Resources tab and set the following appliance resources:

d. Click OK to apply changes. The Interface Editor displays.

25. Select a catalog, such as system_ms, and drag the SQL12y_12 appliance to a catalog.

The SQL12y_12 appliance is now ready for use in your applications.