Jump to: navigation, search

Authoring Solution Definitions

A solution definition file (also called a solution package definition, or SPD) is an XML file that describes what is being deployed and how the deployment is to be executed, as well as any necessary pre- and post-installation procedures.

This page helps you to author your first SPD file to use with Genesys Administrator Extension.

Authoring an SPD File

Create a new SPD file.
Launch a text or XML editor, open a new document, and add the following header lines: [+] Click here to reveal code

The first line is the header information that is required for all XML documents. The second line indicates the schema version of the XML document, and will be used to compare against the running GAX instance. Any major version that contains a later version of the schema will be rejected by GAX.

Important
See the General Elements reference page for more information about the tags that are used in an SPD file.

Add information to personalize the SPD file.
Personalize the SPD file by using the following code as an example: [+] Click here to reveal code
Important
See the General Elements reference page for more information about the tags that are used in an SPD file.

Notes

  • The <deploymentkey> tag is the key string that is used to match different versions of the same solution.
  • The <name> tag is the name that is displayed when the XML file is imported into GAX. The name and the version uniquely identify an SPD file in GAX.
  • The <version> tag indicates the version number of the SPD file.
  • The <description> tag is the description text that is displayed in the user interface.
  • The <summary> tag contains a summary of which configurations this solution definition performs. The summary is displayed in the Summary tab of the GAX user interface.

Add the <profile> element.
Add the <profile> element by using the following code as an example:
Important
If profile name="install", the profile installs a solution. If profile name="update", the profile updates a solution from a previous version.
[+] Click here to reveal code
Important
See the General Elements reference page for more information about the tags that are used in an SPD file.

Add user input dialog boxes.
Add user input dialog boxes by using the following code as an example: [+] Click here to reveal code

Dialog tags are displayed on screen in the GUI Deployment Wizard. Dialog boxes allow the user to select the input values that are defined by the input tags. Multiple dialog boxes (Wizard windows) can be created/added. Multiple dialog boxes enable you to group different user-inputs based on their scope.

Important
See the Dialog Input Elements reference page for more information about the tags that are used in an SPD file.

Add the Execution Block.
The <execution> tag is the main tag in the SPD file. It specifies the execution sequence of various actions that are classified in the following groups:
  • <cfg:...> -- Configuration actions
  • <os:...> -- OS actions
  • <fileio...> -- File I/O actions
  • <http...> -- Web services actions

In addition to these actions, the <execution> tag supports additional child elements that enable the implementation of various functions:

Add the Execution Block by using the following code as an example:

[+] Click here to reveal code

Or, refer to the following sample for code using web services:

[+] Click here to reveal code

See the Executable Elements reference page or the Web Services Elements reference page for more information about the tags that are used in an SPD file.

Save the Solution Definition file that you created as <filename>.XML.

Launch Genesys Administrator Extension.

Navigate to the Solution Definitions panel.

In the Solution Definitions panel, click +.

In the New Solution Definition panel that is displayed to the right, click Browse.

Find the Solution Definition file that you created and select it.

Click Upload. The name of the Solution Definition file, as defined in the Solution Definition, is displayed in the list.

Verify the Solution Definition file is deployable.
To verify that the Solution Definition file can be deployed, perform the following steps:
    a. In the list of Solution Definition files, click the Solution Definition file that you imported in the previous steps.

    b. A related menu is displayed to the right of the Solution Definition list. Verify that the Solution Definition file can be deployed by selecting Check IP Availability.
    • The list of required IPs that are found in the IP Repository and those that are missing are displayed in the IP Availability area.
    c. Upload missing IPs to the IP repository before deploying this Solution Definition file.

If there are no missing IPs, click the Deployable check box.

Click Sav to save your changes or Cancel to leave the Solution Definition file unchanged.

Complete SPD samples

READ THIS FIRST: readme.txt

  • Tenantcreation.xml This SPD creates the Genesys Tenant and the Administrator (Person) that manages this tenant.
  • eservices.xml This SPD contains Install-, Enable-, and Disable-profiles. The Install-profile deploys the eServices Chat Server, Contact Server, Classification Server, E-mail Server, Training Server, Application Clusters, Stat Server, Genesys Desktop, third-party components, and 8.1.0 and 8.0.2 applications to the tenant. It also makes the necessary configurations on the segment-level applications that are required by eServices. The Enable-/Disable-profiles enable/disable this service by establishing/removing the component connections from the tenant level to the segment level.
  • gvphpe.xml This SPD deploys the Genesys Voice Platform Service for Genesys Hosted Provider Edition.
  • http.xml This SPD demonstrates the use of the <http:request> tag.
  • inboundvoice.xml This SPD contains Install-, Enable-, and Disable-profiles. The Install-profile deploys SIP Server, Genesys Desktop, and Stat Server applications to the tenant. It also makes the necessary configurations on the segment-level applications that are required by the inbound voice service. The Enable-/Disable-profiles will enable/disable this service by adding/removing the tenant entry from the network SIP Server's routing strategy list object.
  • outboundvoice.xml This SPD contains Install-, Enable-, and Disable-profiles. The Install-profile deploys SIP Server, Genesys Desktop, and Stat Server applications to the tenant. It also makes the necessary configurations on the segment-level applications that are required by the outbound voice service. The Enable-/Disable-profiles will enable/disable this service by establishing/removing the component connections from the tenant level to the segment level.
  • tserverAvayahpe.xml This SPD deploys the Genesys T-Server for Avaya CM for Genesys Hosted Provider Edition.
  • tserverCiscohpe.xml This SPD deploys the Genesys T-Server for Cisco UCM for Genesys Hosted Provider Edition.
  • webapihpe.xml This SPD deploys the Genesys Web API Server for Genesys Hosted Provider Edition.
  • wfm.xml This SPD contains Install-, Enable-, and Disable-profiles. The Install-profile makes the necessary configuration updates on the database and WFM system to deploy the WFM service. The Enable profile re-enables a previously disabled WFM service by enabling the Database Access Point Objects configured on the tenant level. The Disable-profile disables a previously deployed WFM service by disabling the tenant's user access to the WFM applications, as well as removes the users from the WFM system. Information.png Note: If a service type that contains SIP Server is deployed later, it is necessary to run the WFM re-enable service to properly configure the SIP Server connection for WFM.

References

The Automated Solution Deployment capability within GAX is guided by the XML markup in the solution definition XML file. The following wiki pages outline the elements, attributes, and behavior of the XML markup. The <solutionDefinition> element is the root element of a typical solution definition XML file.

This page was last modified on December 12, 2018, at 22:18.

Feedback

Comment on this article:

blog comments powered by Disqus