Talos™

Your 30 Day Trial Installation Guide

Contents

3 Helping you get started with your trial Talos download

4 Prerequisites for installation

5 Installing Talos – Linux platforms

7 Installing Talos – Windows platforms

9 Validate your Talos licence

10 Using Talos

10 Discovering an existing WebSphere Application Server

13 ReadWebSphereApplicationServercellconfiguration

14 Creating templates

17 Add templates to other cells

18 Apply template to create a payload

19 Apply payloads to runtime

20 Compare mode

Helping you get started with your trial Talos download

This document provides you with an initial guide on how to install and use the Talos trial download. For additional information, please consult the documents provided in the Talos directory structure, under the document folders.

Prerequisites for installation

Talos Server Requirements

Hardware

Memory: 4 GB RAM recommended

Disk Space: 2 GB recommended (it depends on number of environments and data stored for each environment)

Network Requirements to connect to Talos targets: SSH connectivity or connectivity to Talos Agent using an HTTPS port (default 8082)

Note: An orchestration engine is recommended. If none is available, Talos provides a great integration with Jenkins, which is free to use and can be co-installed with Talos.

Software

Operating System: • Linux, AIX, Windows – Please see Install

instrucutions later in this document.• Java Runtime Environment v1.7

Requirements for Talos Targets: • Linux, AIX, Windows – Windows requires Talos

Agent installation• Java Runtime Environment v1.7• Minimum 150MB disk space

Talos requires the Java Runtime Environment version 7 or later. If Java is not on your path, you’ll needtodefineaJAVA_HOMEenvironmentvariablethat points to your Java installation directory. JAVA_HOME/bin/javashouldbeexecutable.Ifyouare in doubt, simply execute the following at a shell prompt: whichjava

Ifapathtojavaisreturnedafterrunningthiscommand,verifythejavaversionwiththefollowing at a shell prompt: java-version

If the resulting output reports that Java is V7 or higher,thentheJavaprerequisiteissatisfied.

A 30 day Talos licence can be requested by emailing the Talos support team: talos@techdata.com

Installing Talos – Linux platforms

1. DownloadtheTalostrialpackage(talos_installer_trial.zip)fromourwebsite(https://talos.techdata.eu/). In the download package, you will get the:

• Taloscoreserver(talos-server.zip)

• Talos toolkits:• Installation Manager• WebSphere Application Server• IBM Http Server• Data Power

• Talos Cloud plugins• AmazonAWS• SoftLayer

2.Copythetalos_installer_trial.ziptoyourserverintoatemporaryfolder.Ifyourserverhasgotinternetaccess, you can use the following command to download it directly to temporary folder TMP:1.

3.Extractthetalos_installer_trial.zipintoatempdirectory:

4. Run the install.sh

Where: ‘-location’ is the location where to install the TALOS server.

The folder and its structure will be created if not existing and must have the last folder be called talos (i.e/opt/techdata/talos)

Note:Pleasewaitbetween1to5minutestoallowTOMCATtoexpendtheTALOSwarfile.

cd/tmp

wgethttp://download.talos.cloud/ext-talos-release/Talos/latest/talos_installer_trial.zip

cd/tmp

unziptalos_installer_trial.zip–dtalos_installer_trial

cd/tmp/talos_installer_trial/install/lin

./install.sh-location<locationforinstall>

5. Talos should now be available in the following URL: http://<hostname>:8080/talos. OpenawebbrowserandtestthatTalosisavailable.Thedefaultadministratoruser/passwordis admin/admin.

Installing Talos – Windows platforms

1. DownloadtheTalostrialpackage(talos_installer_trial.zip)fromourwebsite(https://talos.techdata.eu/). In the download package, you will get the:

• Taloscoreserver(talos-server.zip)

• Talos toolkits:• Installation Manager• WebSphere Application Server• IBM Http Server• Data Power

• Talos Cloud plugins• AmazonAWS• SoftLayer

2.Copythetalos_installer_trial.ziptoyourserverintoatemporaryfolder.Ifyourserverhasgotinternetaccess, you can use the following command to download it directly to temporary folder TEMP:

Open a browser and go to:

Pleaseuse‘Saveas’toselectwhereyouwanttodownloadthezipfile

3.Extractthetalos_installer_trial.zipintoatempdirectory:

•Openafileexplorerintothepreviousfolderyoudecidedtodownloadthezip•Rightclickthefileandselectextractall• Please change the location to your preference – For the rest of this documentation we will assume

the location is C:\Temp.

http://download.talos.cloud/ext-talos-release/Talos/1.2/talos_installer_trial.zip

4. Run the install.bat

Where: ‘-location’ is the location where to install the TALOS server.

The folder and its structure will be created if not existing and must have the last folder be called talos (i.e C:\temp\techdata\talos)

Note:Pleasewaitbetween1to5minutestoallowTOMCATtoexpendtheTALOSwarfile.

5. Talos should now be available in the following URL: http://<hostname>:8080/talos. Open a web browser andtestthatTalosisavailable.Thedefaultadministratoruser/passwordisadmin/admin.

Talos requires the Java Runtime Environment version 7 or later. If Java is not on your path, you’ll needtodefineaJAVA_HOMEenvironmentvariablethatpointstoyourJavainstallationdirectory.JAVA_HOME/bin/javashouldbeexecutable.Ifyouareindoubt,simplyexecutethefollowingatashellprompt:

cdC:\Temp\talos_installer_trial\install\win

install.bat-location<locationforinstall>

Validate your Talos licence

1. Before using Talos, you have to validate your licence.

2. Open the following URL: http://<hostname>:8080/talosin a web browser.

3.Loginusingthedefaultadminuser:admin/admin

4. You should see the following message: ‘Unable to validate your Talos license: There is no local license’.

5. Click ‘Administration’ and then ‘Licensing’.

6.Fromthisscreenyouhavetwowaystoenableyourlicense:‘Online’or‘Offline’.

7. To activate your license online, your Talos server requires internet connection. Just enter your license details and click the ‘Activate License’ button.

8. After that you should see a success message and a screen with your license details.

9.IfyourTalosserverdoesnothaveinternetconnectivity,youhavetoactivateyourlicenseoffline.Forthat,clickthe‘ActivateLicenseOffline’andfollowtheinstructionsprovidedonthepage.

Using Talos

ThissectionprovidesyouwithsomedetailsonhowtouseTalos.Inthisspecificusecase,wewilldiscoveranexistingWebSphereApplicationServercell,readitsconfigurations,createatemplatewithasub-setofconfigurationsandapplythattemplatetootherWebSphereApplicationServercells.

Discovering an existing WebSphere Application Server

OneofthefirstthingsyoumaywanttodowhenusingTalosistodiscoveranexistingWebSphereApplication Server cell. In this section we will discover the cell using a SSH connection, however you do have other connection options, for instance, SOAP or using Talos agent (usually used to connect to Windows targets).

1. Click‘MiddlewareInstances’->‘Discover’.

2. Select ‘Import WebSphere Cell using SSH’.

3. Fill out the information for the cell that you want to manage according to the description in the table below.

Field Description

Environment Anynamethatyouchoosetoorganizedomainsintoenvironments. Generally this is the software development lifecycle (dev, qa, stage, prod, etc.), but could be the name of the device or line of business.

Middleware ThenameoftheWebSpherecellasdefinedinthecellconfiguration.

Select Connection Type You can select using Talos agent, SSH using password or SSH using Authorizedkeys.Inthisdocument,weassumethatyouwilluseSSHusing password.

Host Name The hostname of the remote system – WebSphere Application Server DMGR.

OS Username The SSH username to connect to the target machine.

OS Password The password for the SSH user.

WebSphere Security User The username to connect to WebSphere.

WebSphere Security Password

The password to use when connecting to WebSphere.

DeploymentManagerProfilePath

Thepathtothedeploymentmanagerprofileontheremotesystem.

SOAP Port The port to connect to the JMX API via SOAP. This connection will happen on the remote system.

4. When complete, click ‘Continue’.

5.Thesystemwillreadinthenodes,clustersandserversdefinedinthecell.Anyerrorswillbeprintedtothe screen allowing you to go back to correct any information that was supplied. When the import is complete, click ‘Done’.

If any errors occur and you need to modify any of the information in the form, you can simply click the ‘Back’buttonatthebottomoftheconsolejobsviewtoreturntotheform.Allofthepreviousanswerswillbefilledoutandyoucansimplychangewhatevervaluesyouneed.

Read WebSphere Application Server cell configuration

1. Tobeginmanagingconfiguration,readintheentireconfigurationfromthecell.

2.IntheMiddlewareInstancesview,clickthemiddlewareinstancewejustdiscovered,andclick‘ReadConfiguration’.

3.Thejobwillrunwithanyerrorsbeingprintedtothescreen.Oncecomplete,click“Done”.

Creating templates

NowthatyouhaveconfigurationinTalosfortheWebSpherecell,youcancreateatemplate.ThetemplateallowsyoutoselectasubsetofconfigurationthatyouwanttopromoteintoanotherWebSpherecell.Italsoallowsforameansofcreatingtokenstorepresentenvironmentspecificvariablesandvalues.

1. Tocreateatemplate,click‘New’->‘was’

2. Provide a name for the template. This is a name that is meaningful to you and allows you to know what configurationhasbeenmappedintowhichmiddlewareinstances.

3.Selecttheobjectsandfilesthatyouwanttoincludeinthetemplate.

4.Addvariablesforenvironmentspecificvalues.

5. Change variable names to something meaningful.

6. Create the template by clicking on ‘Save’.

Add templates to other cells

Now that you have templates, you can add them to other cells. When templates are added to cells, you canspecifytheenvironmentspecificvaluesforthosevariablesthatwerecreated.

You have two ways to add a template to other cells, in the template view or in the middleware instance view. In this document, we will use the middleware instance view.

1. Click the middleware instance that you want to add the template. In our case, this is a second WebSphere Application Server that we discovered using the method explained above.

2. In the ‘Templates’ section, click ‘Add’ and select the template name you want to add:

3.Click“ToggleVariables”todefinethetemplatevariablesvaluesforthismiddlewareinstance

4. Click ‘Save Variables’.

Apply template to create a payload

Payloadsaretemplateswithtokensreplacedbyenvironmentspecificvalues.Theyarespecifictoamiddleware instance. You can create payloads from templates in the web UI or from the command line via an activity.

To create and view payloads in the web interface, go to either the ‘Template View’ for the template or the ‘Middleware View’ for the middleware. This example shows the steps from the ‘Middleware View’.

1. Click the middleware name on the left menu.

2. For the template that you want to create a payload from, click the ‘Create Payload’ button.

3. To view the result, click ‘View’.

4. A dialog will open with a tree view into the payload.

To create a payload by running an activity, at the command line in Talos server, execute the runActivity.sh command:

Apply payloads to runtime

PayloadscanbeappliedtoWebSphereApplicationServerruntimeconfigurationviaanactivity.Talosprovides integration with several orchestration engines to orchestrate this and more complex use cases like, for instance, building a WebSphere Application Server. However, in this case we will run the required activity by calling it using the command line.

1. To apply a payload to the WebSphere Application Server runtime, execute the following command in Talos server:

/opt/techdata/talos/bin/runActivity.sh-environment<environment_name>-middleware

<middleware_name>-toolkitwas-activity

ApplyTemplate–argtemplate=<template_name>

/opt/techdata/talos/bin/runRemoteActivity.sh-environment<environment_name>-middleware

<middleware_name>-toolkitwas

-activityAppsAndConfiguration–payload<template_name>

Compare mode

Talos allows you to compare two middlewares in order to ascertain any differences – particularly useful fordeterminingwhichitemsshouldbeincludedinatemplate,oridentifyingconfigurationdriftbetweenenvironments.

Inordertocomparethedifferences,yousimplyneedtoselectthefirstmiddleware,click‘CompareWith’,and select from the drop down, the middleware you wish to compare against.

You will then be presented with a list of scopes to be compared. There will be a default association between certain scopes, but these can be edited or removed as necessary:

Select the scopes to be compared and then click OK. The comparison is then displayed. Items that are present in both environments but the values differ are highlighted in yellow:

Items that are present in only one environment are highlighted in red.

Contact

If you experience any issues with installing and running the trial

download then contact one of the Talos support team:

talos@techdata.com • www.techdata.com