Deploying Avaya WebLM in a software-only environment using Solution Deployment Manager

Last Updated : Mar 19, 2024 |

About this task

Use this procedure to deploy Avaya WebLM ISO in a software-only environment using Solution Deployment Manager.

Before you begin

  • Install the Solution Deployment Manager client if System Manager is unavailable.

  • Add a location.

  • Add a platform.

Procedure

  1. To access Solution Deployment Manager, do one of the following:

    • On the System Manager web console, click Services > Solution Deployment Manager.

    • On the desktop, click the Solution Deployment Manager icon (Icon used to open the Solution Deployment Manager client dashboard).

  2. Click Application Management.
  3. In Application Management Tree, select a location.
  4. On the Applications tab, click New.

    The system displays the Application Deployment dialog box.

  5. In the Select Location and Platform section, do the following:
    1. In Select Location, select a location if not already selected.
    2. In Select Platform, select a platform to deploy the Software-Only ISO image.

      The system displays the IP Address and FQDN of the platform in the Platform IP and Platform FQDN fields.

  6. In the Provide admin and root Credentials section, do the following:
    1. In Admin User of OS, type the admin user name.
    2. In Admin Password of OS, type the admin user password.
    3. In Root User of OS, type the root user name.
    4. In Root Password of OS, type the root user password.
    5. Optional Click Test Connection.

      The system logs in to the platform by using the credentials to test the platform connectivity. If connectivity is established, the system displays the message: Test Connection Successful.

    6. Click OK.
  7. Click Next.
  8. To select the required application, on the ISO tab, click one of the following:

    • SW Library / Select from software library: Select the local library where the ISO image is available.

      If you are deploying the ISO image from the Solution Deployment Manager client, you can use the default software library that is set during the Solution Deployment Manager Client installation.

      Remote library is not supported for software-only deployment.

    • Browse: Select the ISO image from your local computer, and click Submit File.

    • URL: Click URL and provide the path to the ISO image.

    Select the required application, click Submit.

    If the application ISO image supports the patch deployment, the system enables the Service or Feature Pack tab.

  9. In Flexi Footprint, select the footprint size for the application.
  10. In Test Your Operating System Compatibility Against Element Software Package, click Test Environment Compatibility.

    The installer checks if the platform has all the dependent rpms, network, cpu, memory, and hard disk configuration as specified for the element. This process takes about 4-5 minutes. After the process starts, you cannot proceed further until the process is complete. If you get any error or warning, make the necessary changes before the next steps.

    Note:

    If the browser hangs, the system provides the option to end the script or wait. Always click Wait.

  11. Optional To view the installer compatibility results in a separate window, click View Output.

    The system displays the Environment Check Output window.

  12. Click Next.
  13. On the Configuration Parameters page, provide all the information required.

    For a Software-Only application deployment, the Network Parameters tab is disabled.

  14. Click Deploy.
  15. On the EULA Acceptance window, click Accept.

    After accepting EULA, the system displays Software only Installation Warning for software-only application deployment.

  16. To continue with the deployment, click Accept.

    The system displays the deployment status in the Current Action Status column and the deployed application on the Applications tab.

  17. To view details, click Status Details.

Next Steps

This is an important mandatory step: Configure the Java path as an environment variable and reboot the WebLM Server VM.