Adding software to the Depot from web repository

To add a software to the Depot from web repository

1. Right-click a Depot folder and from the pop-up menu, select New > Software.
2. Select the type of software package to create. 
3. In the Select Installable Sources dialog box, select the installable file from the list of saved web repositories. Use the hierarchical tree to browse to the location where the installable file is saved and select the file. 
   You can also select one or more files.

4. If you want to deploy the software package directly to the agent, select Download during deployment. If you select this option, the Application Server uses the web repository URL to access the specified installable files and copies them to a staging directory on the agent during the staging phase of a Deploy Job.

   If you want to copy the installable file to the file server at the time of depot software creation, do not select Download during deployment option.

5. Click OK.
6. Click Browse to the right of the Save in field. Use the Select Folder dialog box to select the depot folder where you want to store software packages. Click OK.
7. (Applicable for custom software) From the Operating system list, select the operating system for the software you are packaging. 
8. (Applicable for custom software) From the Custom software type list, select the type of software you are packaging.
   If you are packaging software that does not appear in this list, select Custom Software and the window provides a generic install and uninstall command.
9. In the Installable source/ Source field, verify that the source file is correct for the selected package. If the source file is not correct, click Browse to specify the source file for the selected package.
10. If you do not want to copy source files to a directory where they can be used for rolling back this deployment, select Do NOT copy source to undo directory during deployment.
11. (Applicable for service pack and patch) If you are adding a service pack to the Depot, select Source is service pack. If you are adding a patch, do not select Source is service pack. 
12. Enter the name and description of the software to be added to the Depot. 
13. (Applicable for hotfix) If you are adding a patch to the Depot and you have manually specified the source file for the patch, do the following:
    
    1. 
       
       • In the Bulletin ID field, enter the bulletin number of the patch.
       • In the Patch Key field, enter the patch key. When the system automatically completes the Patch Name field, it provides a unique name.  
14. (Applicable for hotfix) If you have manually specified the source file for the patch or service pack, do the following:
    1. 
       
       • For Product, select the product for which you are adding a patch or service pack. For example, you might select Windows 2003 or SQL Server 2005.
       • For Service Pack, select the level of the service pack you are adding. If you are adding a patch, enter the level of the service pack to which the patch applies.
       • For Language, select the language for the patch or service pack.
15. The Software info list is used to match the software being deployed with software stored in the Depot or on the network. If the Software info list is not populated, do one of the following:
    • (UNIX) To identify the software being deployed, click Browse to the right of the Software info list. The Select Installable Location dialog box opens. Use it to navigate to an instance of the software you are packaging. Select the software and click OK. Using that software package, TrueSight Server Automation can automatically populate the Software Info list.
      If you do not use parameters when providing a network location and an agent is installed at the source location, the system can always automatically determine the software to deploy for UNIX packages. It accomplishes this by checking a list of applicable software packages and version numbers contained within the software package. However, if you have used parameters when specifying the location of a network-based URL, the system may not be able to access that list to determine the software to deploy. Similarly, TrueSight Server Automation cannot access the list if an agent is not installed on the host where the source files are located. 
    • (Windows) If you plan to add Windows software to the Depot, you must manually identify the files that must be deployed. To add an item to the list, click the + sign to the right of the Software info list. The Software Part Information dialog box opens. Enter a name and optionally a version and platform for the software. Then click OK. To delete an existing entry, select the entry in the Software Info list and click the - sign.
16. (Applicable for Windows MSI package) Open the Optional MSI Customization Properties dialog box by clicking Edit beside Optional Install MSI Customization Properties or Optional Uninstall MSI Customization Properties.
    Use the dialog boxes to create answers that replace the standard answers used in an MSI silent install or uninstall. To create custom properties, use Name and Value to enter a name/value pair and then click . Ensure that the names that you enter correspond to standard names used in an MSI file. Name/value pairs are used when you execute the MSI file. They do not change the MSI package. To delete an item from the list of name/value pairs, select the item and click .

17. In the Install command field, enter the command (including arguments) that invokes installation of the package type you are creating. This field automatically displays the default installation command for the type of software you are packaging. To apply the command to all software listed in the left pane, click Apply to All.  
    
    When executing the Install command, TrueSight Server Automation replaces a parameter bracketed with two question marks, such as ??SOURCE??, with its appropriate value. For example, the system replaces ??SOURCE?? with the directory in which software is stored in the package being deployed. The following table describes parameters in the default install and uninstall commands. If the command includes a parameter not shown in the following table, the parameter must reference a server property and associated target servers must have a value defined for the property. If a software package is encapsulated in a BLPackage, parameters can reference local properties for the BLPackage.

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
    This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
    

    An install command can reference a support file by including the string ??supportFile??, where supportFile can be the name of any support file, a name that must start with an underscore character. For example, you can reference a response file by entering a string such as ??_RESPONSEFILE??. References created this way appear in the Support Files table at the bottom of the window. To remove a file from the Support Files table, delete the string referencing the file in the install command.
    Square brackets within an install command enclose optional information, such as
    [-a "??_INSTALL_ADMINFILE??"].
    In the response file, you can add a parameter bracketed with two question marks. TrueSight Server Automation replaces the parameter, such as ??TARGET.NAME??, with its appropriate value during deployment. 
    To apply the command to all software listed in the left pane, click Apply to All. 
    If you enter a parameter that references a server property, you can type the parameter name, bracketed with two question marks, or click Select Property to choose a property from a list. If you click Select Property, you can view hierarchical properties by clicking the right arrow that appears next to some properties. A subordinate list of properties appears. To return to the parent list, click the left arrow next to the property at the top of the list.

    Note about adding AIX packages:

    When you create an AIX package or patch and the software parts being packaged cannot be parsed, the default install command is automatically altered to replace the word "all" for the ??SUBPACKAGES?? or ??SUBPATCHES?? parameter. However, if you modified the install command to exclude a ??SUBPACKAGES?? or ??SUBPATCHES?? parameter, this replacement does not occur. Automatic modifications of AIX packages and patches are not visible within the Add Software wizard. Modifications occur when the software package is created.

18.  For Uninstall command, enter the command, including arguments, that invokes the uninstall. This field automatically displays the default uninstall command for the type of software you plan to package. To apply the command to all installables listed in the left pane, click Apply to All.

    The uninstall command works like the install command. The system replaces parameters with an appropriate value. The uninstall command can reference other files by including the string ??_supportFile??. Square brackets within an install command enclose optional information.

    Note about adding AIX packages:

    For AIX packages, if the uninstall command includes the ??SUBPACKAGES?? parameter, the command is disabled. However, if you modify the uninstall command so it does not include a ??SUBPACKAGES??parameter, the command remains enabled. No uninstall command exists for AIX patches.

19. To provide a location for a support file, select an entry in the Support Files table and click the Edit Parameter Entry to display the Set File Parameters dialog box. Do the following: 

    1. Click Browse to display a dialog box from where you can select the deployment options for the support file. If necessary, enter a URL to identify a network location. You can use parameters in the file name, but parameters are not substituted if you enter a URL for a network location. 
    2. If you do not want the system to insert values for parameters that appear within the body of the file, check Skip parameter substitution for this file. (This is typically necessary if a support file is binary, such as an MSI package with a required CAB file.) 
    3. Click OK.

    Using agent mounting for specifying support files

    When specifying support files, do not use agent mounting if you are packaging software that generates a result file that is unique for each target server.

20. Click Next.

21. The Properties panel provides a list of properties automatically assigned to the job being created. In this list, you can modify the value of any properties that are defined as editable.

    For any property that has a check in the Editable column, select the property and click in the Value column.

    • To set a property value back to its default value, click Reset to Default Value .
      The value of the property is reset to the value it inherits from a built-in property class. The Value Source column shows the property class from which the value is inherited.
    • Depending on the type of property you are editing, you can take different actions to set a new value, such as entering an alphanumeric string, choosing from an enumerated list, or selecting a date.
      To insert a parameter into the value, enter the value, bracketed with double question mark delimiters (for example, ??MYPARAMETER??) or click Select Property .
22. Click Next.

23. Using the Permissions panel, you can add individual permissions to an object. You can also set permissions by adding ACL templates or ACL policies. The Permissions list is an access control list (ACL) granting roles access to any objects created in the system, such as depot objects. ACLs control access to all objects, including the sharing of objects between roles. For more information, see the following table:

    Task	Description
    Adding an authorization	An authorization grants permission to a role to perform a certain type of action on this object. To add authorization to this object, click Add Entry  in the Access Control List area. Then use the Add New Entry dialog box to specify the role and authorization you want to add.
    Adding an ACL template	An ACL template is a group of predefined authorizations granted to roles. Using an ACL template, you can add a group of authorizations to the object. To add an ACL template to the object, click Use ACL Template  in the Access Control List area. Then use the Select ACL Template dialog box to specify an ACL template that you want to add to this object. To set the contents of the selected ACL templates so that they replace all entries in the access control list, select Replace ACL with selected templates. If you do not select this option, the contents of the selected ACL templates are appended to existing entries in the access control list.
    Adding an ACL policy	An ACL policy is a group of authorizations that can be applied to this object but can be managed from one location. To add an ACL policy to this object, click Use ACL Policy  in the ACL Policies area. Then use the Select ACL Policy dialog box to specify an ACL policy that you want to add to the object. To set the contents of the selected ACL policies so they replace all entries in the access control list, select Replace ACL with selected policies. If you do not select this option, the contents of the selected ACL policies are appended to existing entries in the access control list.

24. Click Finish. A background process saves the software package to the Depot. Depending on how you have specified behavior for background processes, either a dialog box opens or the Show background operations icon appears in the lower right corner of the console. Both indicate an operation is running in the background.