IBM Certified WebSphere Application Server 8.5 Administrator - Administrative Tools Overview
Learn about the various administrative tools available for managing IBM Certified WebSphere Application Server 8.5. Explore ways to administer through admin consoles, command line utilities, scripting, and JMX programs. Understand the importance of admin consoles, different types available, and how to access and utilize them effectively. Discover tips on saving configurations, tracking activities, and managing resources efficiently within the admin console environment.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
IBM Certified WebSphere Application Server 8.5 Administrator A course to get certified in 7 days Karun Subramanian, ESIS Consulting LLC Part 2
Section 4 Administrative Tools
Ways to Administer Admin Consoles Command line utilities scripting using wsadmin JMX programs Admin Console is the widely used tool. Command line and scripting can be very powerful and can save time for repetitive tasks While JMX programs can be used to administer, it is very rare in practice
Admin Consoles Various types of consoles available Admin consoles are web based applications ISC (Integrated Solutions Console) is the primary way to administer a cell. It is installed in the DMGR Admin Console for Administrative agents manages Nodes that are registered to it Job Manager Admin Console manages the Job manager settings and submits jobs
Admin Consoles Cont... Generally accessed through URL https://<your server>/WC_adminhost_secure/ibm/console Your activity is tracked at <profile home>/wstemp so that it can be recovered in case of unexpected exit from the console Using Console preferences, the commands used by WAS during the Admin Console activity can be logged For most of the operations within Admin console, you can view the command used by WAS
Admin Consoles Cont... Resources can be created in various scopes o Application o Application Server o Node o Cluster o Cell Granular scope overrides if the same resource is defined in multiple scopes Admin console provides an option to view the available scopes either in a drop down list or using fields
Admin Consoles Cont... Whenever you make changes in Admin console, you are prompted for saving . It is a good idea to click on the review link to see what files are being modified You can also save the configuration using System Administration -> Save Changes to Master Repository
Admin Consoles Cont... Admin Console provides few Guided Activities such as Creating and configuring a cluster for workload management , Configuring database connectivity etc Admin console can show runtime events generated by Application Server classes Guided activities walks you through step by step while you perform the actual steps You cannot login to the same Admin console using the same user id using two different browser windows
Securing Admin Consoles Enable Administrative Security to secure Admin Console You must determine the user repository to use (Active directory, Local OS File based repository etc) Administrative security is NOT the same as Application security In order to access the Admin console, the user must authenticate against the chosen repository and also belong to a administrative role defined in the Admin console (screenshot)
Securing Admin Consoles Cont... Fine grained security possible. Resources can be grouped into Authorization groups and users can be assigned to required administrative role within the authorization group Cell wide authorization group is also available Users and Groups -> Manage Users (or) Manage Groups Users and Groups -> Administrative user roles (or) Administrative group roles
Various Administrative roles Administrator: Can do everything except map users to Administrative roles Admin Security Manager: Map users to Administrative roles and manage authorization groups Auditor: View and change Security Auditing Configurator: Change WAS Configuration Operator: Can start/stop services Monitor:Can view configuration and runtime Deployer: Can configure/deploy Applications ISCAdmin: Manage users and groups within the Admin console only
Job Manager Console Manages jobs submitted to targets that are registered to the Job Manager Loosely coupled administrative functionality You can manage jobs via ISC (Integrated solutions console) as well (which tree ?) You can start/stop Servers, start/stop/install Applications and liberty profile resources, create/delete Servers and clusters, install/update IIM (IBM installation manager) You can also run wsadmin scripts on target using Job Manager console
Command line Tools Several commands available Windows commands are .bat whereas Unix commands are .sh Commands are located in <WASHOME>/bin and <PROFILEHOME>/bin. Where you run the command from is significant Most commands accept -profileName parameter which ensures the profile against which the command is run When required, the command will prompt username/password
Sample commands startServer <server name> : Starts an Application Server stopManager : Stops Deployment Manager serverStatus -all : Shows status of all the Servers versioninfo : Shows versions of installed Websphere Application Server products addNode : Federates a node into a cell managesdk : defines the JDK version used by WAS manageprofile : Manages profiles
Administration using Scripting Very powerful way of Administering WAS If you can do it through Admin Console, you can do it through wsadmin Uses Bean Scripting framework. Jython is the preferred language. Jcal is being deprecated Can be run offline or online (attaches to a running process) Will require username/password when needed Can be run to remotely when connecting to a running process
wsadmin Introduction Launch wsadmin o <profilehome>/bin/wsadmin -lang jython o wsadmin.sh in Unix systems <profilehome>/properties/wsadmin.propertie s for setting certain parameters. You can, for example set com.ibm.ws.scripting.defaultLang to Jython A script profile can be used with -profile option to run a script before the main script (for example, you can define your own methods/functions in this file)
wsadmin Introduction Cont... You can use the interactive mode to run commands in wsadmin prompt o wsadmin -lang jython Using -c flag, you can invoke one command as part of invoking wsadmin o wsadmin -lang jython -c AdminControl.getCell() Using -f flag, you can run your own script and then exit from wsadmin o wsadmin -lang jython -f c:\createMyCluster.py To enable tracing of wsadmin, uncomment the following line in wsadmin.properties com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
wsadmin Introduction Cont... Five Management objects available o AdminControl o AdminConfig o AdminTask o AdminApp o Help print Help.AdminControl() : General help about the Administrative object print AdminControl.help( queryNames ) : More specific help about the particular method/command
wsadmin Management objects - AdminControl Controls Objects in running Websphere process, for example stop a node agent, or change log level of an application server Get the Object on which to run AdminControl and use AdminControl commands against it o myServer = AdminControl.completeObjectName( node=myNode, type=server,name=myAppServer ,* ) o print Help.attributes(myServer) o print Help.operations(myServer) o AdminControl.invoke(myServer, stop )
wsadmin Management objects - AdminControl Cont... To change an attribute of the running process myServerTrace = AdminControl.completeObjectName( type=Trac eService,process=myAppServer,*) AdminControl.setAttribute(myServerTrace, t raceSpeficiation , *=info:com.ibm.ws.rsada pter.jdbc.*=all ) The above commands enables sql tracing on myAppServer
wsadmin Management objects - AdminConfig Retrieves, updates, creates and removes Configuration objects in WAS repository Only available when connected to dmgrs Major steps in using AdminConfig Determine the the configuration object type print AdminConfig.types() Get the configuration object id print AdminConfig.list( Server ) Server=AdminConfig.getid( /Node:myNode/ Server:myServer/ )
wsadmin Management objects - AdminConfig Cont... View the attributes print AdminConfig.attributes( Server ) perform the operation (update,remove,create etc) jdbcpr = AdminConfig.getid( /JDBCProvider:UserDefi ned-mySQLServerJDBCProvider/ ) print AdminConfig.show(jdbcpr) AdminConfig.modify(jdbcpr, [[ description , Custom JDBC driver ]]) Save the configuration and sync the nodes AdminNodeManagement.syncActiveNodes()
wsadmin Management objects - AdminApp Installs,updates and removes Enterprise Application print AdminApp.list() AdminApp.edit( AppName ,options) AdminApp.editInteractive( AppName )
wsadmin Management objects - AdminTask Set of Administration commands (grouped based on the function) to simplify wsadmin scripts Generally more user friendly than standard wsadmin commands Interactive and batch mode. Interactive mode presents text based wizards print AdminTask.help( -commands ) print AdminTask.help( - commandGroups )
AdminTask - Property file based configuration Configuration of WAS can be extracted to a single text file,modified and then applied using wsadmin Helps avoid complex wsadmin commands AdminTask.extractConfigProperties( - configData Node=node1 - propertiesFileName=myProps.txt ) Other commands: validateConfigProperties applyConfigProperties deleteConfigProperties createPropertiesFileTemplates
Using Administration Scripting libraries Perform complex functions using just one command. Pre built Jython scripts for your use, categorized into various types Located in <WASHOME>/scriptLibraries. When you invoke wsadmin, these commands are loaded and available to you Review the jython scripts or invoke their help method to find out more print AdminJDBC.help() print AdminJDBC.listDataSources()
