Use the Application Services library to create software service versions. The Application Services library also contains predefined services.

About this task

Sometimes, rather than creating a new service, you might prefer to edit the scripts and variables in the predefined service. As a best practice, create a copy of the predefined service before you make changes. See Maintain Service Versions.

You can share a service publicly or privately in a group. Sharing is supported at the component level and not at the individual version level.

Prerequisites

  • Log in to Application Services as an application cloud administrator and an application publisher and deployer.

  • Verify whether you must add items to the operating systems and descriptive tag lists. See Add Operating Systems to the Library and Add Tags to the Library.

  • If you plan to add an operating system with SELinux enabled, verify that the permissive mode is enabled or specific exceptions are in place for the applications being installed to avoid any installation failures.

  • If a service is used in a blueprint or included as a preinstalled service in a logical template, the service cannot be deleted. Before you delete a service, delete the referenced blueprint or logical template with the preinstalled service.

  • To view examples about how to name or describe a service, select Library > Services to view the predefined services.

Procedure

  1. On the Application Services title bar, click the drop-down menu and select Library > Services.
  2. Click New.
  3. Set the name of the service, add a description, and click Save.

    Use a name that corresponds to the software component to which the action scripts relate and append qualifiers for tracking purposes. For example, if you use the service on a particular operating system, you can set the service name as ServiceName_Windows or ServiceName_Linux.

  4. Click Create Service Version to create a service version.

    You can create multiple versions for a service.

    A page for creating a service version opens.

  5. Complete the service version information.

    The service version name stays the same.

    1. Specify major, minor, or micro release versions, with or without qualifiers.

      For example, you might use version numbers such as 1.0, 1.5, or 1.0.1-Linux.

    2. (Optional) : In the Description section, if you are creating a service version for a specific operating system, describe the operating system version used and any applicable required configuration.
  6. Set the tags to organize the list of services you see when you create a deployment blueprint for an application
    Note:

    Only tags designated as Server Type appear in the drop-down menu.

    You can add multiple tags.

  7. To create a tag that is not in the list, click Cancel, and select Library > Tags.
  8. (Optional) : In the Supported OSes section, if the scripts used in this service can run only on particular operating systems, select those operating systems here.

    In the blueprint editor, Application Services prevents the service from being added to a template unless the template contains one of these operating systems. Leave this field blank if the service can be used in any operating system.

  9. To use an operating system name that is not in the list, click Cancel, and select Library > Operating Systems to create an operating system name.
  10. (Optional) : In the Supported Components section, if only certain types of application component can run in this service, specify those components here.

    For example, only WAR and JAR components can run in a vFabric tc Server instance. Only SQL scripts can run in a database server. The components that you select restrict what application components can be added to this service in an application blueprint. Leave this field blank if you can add components to the service.

  11. Select the Pre-install in a Template check box to list the service in the Services Included section while you create or edit a logical template.

    Selecting the checkbox Indicates that the service is already installed in a template.

    If you did not select this check box, the service appears in the list of services that you can include when you create a deployment blueprint for an application.

    Logical templates with preinstalled services also appear in the OS Templates section of the application blueprint and are available as part of the template.

What to do next

Configure the service version properties. See Define Service Version Properties.