WebSphere V4.0 Administrative Tools - IBM Administrative Tools Admin Console ... "") Sample Client...

IBM WebSphere Application Server V4.0 IBM WebSphere Application Server V4.0

WebSphere V4.0 Administrative

Tools

10/02/01 © Copyright 2001 IBM Corporation WS40ST05.prz 23 of 401 Page 1 of 34

TopicsTopics

Command Line Administrative Tools:XMLConfig Tool

Configuration informationActions supported

WebSphere Control Program (WSCP)Objects supported

Graphical Administrative ToolsAdmin Console

WebSphere 4.0 AEInstall Enterprise ApplicationEnterprise Application PropertiesResources - JDBC, URL

Thin Client Admin ConsoleWebSphere 4.0 AEs/AEdBrowser based

10/02/01 © Copyright 2001 IBM Corporation WS40ST05.prz Page 124 of 401 of 34


Command Line Administrative Tools


Tools to modify WebSphere (WAS) RepositoryTools to modify WebSphere (WAS) Repository

WASRepository

XMLConfig

WSCP

WriteRead/Write

WebSphere 4.0 AE Admin Console

Read/WriteImport Export

WSCPCommand

file

XMLfile

Read

Interactive

Command Line Tool


XMLConfig and WSCP: Comparison from V3.5.XXMLConfig and WSCP: Comparison from V3.5.X

XMLConfig and WSCP read and write objects in WAS repository

Objects stored in WAS repository for V4.0 are different than V3.5

In V4.0, application data is stored in archive (EAR) files, not in WAS repository

Use AAT to edit Application data (EAR, EJB JAR, Web WAR, ...)

In V3.5, all data is stored in WAS repository

Tools operate on different set of objectsFor example:

In V3.5, could add servlets, EJBs to the appserverIn V4.0, this is all within the EJB JAR or WAR file.

Command syntax is similar in V3.5.X and V4.0


XMLConfig ToolXMLConfig Tool

Command line tool to modify extract configuration dataUsed by Administrator%WAS_HOME%\bin\xmlconfig.dtd file contains the XML specifications Command syntax (similar to V3.5.X)xmlconfig {[(-import <xml data file>)||

(-export <xml output file> [-partial <xml data file>])]-adminNodeName <primary node name> [-nameServiceHost <host name> [-nameServicePort <port number>]]

[-traceString <trace spec> [-traceFile <file name>]][-generatePluginCfg <true || false>]

[-substitute <"key1=value1[;key2=value2[...]]">]}

Samplesxmlconfig -export output.xml -adminNodeName node1xmlconfig -import input.xml -adminNodeName node1


XMLConfig Tag HierarchyXMLConfig Tag Hierarchy

<websphere-sa-config><virtual-host><jms-provider><url-provider><jdbc-driver>

<data-source><server-group><node>

<application-server><web-container><session-manager>

<enterprise-application><ejb-module><web-module>

<security-config>

Tags removed in V4.0:<model>

<ejb-container><ejb>

<servlet-engine><web-application>

<servlet><user-profile-manager>

<servlet-redirector><model><enterprise-application-security><ejb-security><uri-security><method-group><permission>


XMLConfig: Configuration Information ...XMLConfig: Configuration Information ...

ResourcesJDBC, URL, Java Mail, J2C, JMS

Enterprise ApplicationsUser/Role bindingRunAs MappingWeb Module

Name, Context Root, EJB and Resource BindingsModule Install info (App. Server where module is installed)

Entity moduleName, EJB and Resource BindingsModule Install info (App. Server where module is installed)


Other things that XMLConfig can modify - no significant change from WebSphere Application Server V3.5:

Virtual HostMime tableAlias list

Security ConfigurationSecurity defaultsAuthentication mechanism

Node InformationApplication ServersPropertiesServices - EJB Container, Web Container, Trace, ...

In a default install, xmlconfig.dtd is located in the<WAS_HOME>/bin directory.

WebSphere Control Program (WSCP)WebSphere Control Program (WSCP)

WSCP: Interactive command line administrative toolUsed to perform the following functions:

Define, configure, and manage administrative database objects from any node.Import or export configuration data.Perform diagnostic operations such as enabling a trace.

Based on a standard scripting language, TclInvoking WSCP

wscp.bat or wscp.shUsage: wscp [-h] [-c command] [-f Tcl_file_name] [-pproperties_file_name][-x extension_class][-- options ]

General format of all wscp actions is:<object-type> <action> [name] [options]Example syntax of name:

/Node:N1/ApplicationServer:Default Server/


WSCP: Objects Common to V3.5.2+ and V4.0WSCP: Objects Common to V3.5.2+ and V4.0

ApplicationServerContextDataSourceDrAdminGenericServerHelpJDBCDriverNodeRemoteVirtualHostXMLConfig


WSCP: Unique Objects in V3.5.2+ and V4.0WSCP: Unique Objects in V3.5.2+ and V4.0

WAS 3.5.2+ unique objectsEnterpriseApplicationEnterpriseBeanModelServletServletEngineServletRedirectorSessionManagerUserProfileWebApplicationWebResource

WAS 4.0 unique objectsDomainEnterpriseAppJ2CConnectionFactoryJ2CResourceAdapterJMSConnectionFactoryJMSDestinationJMSProviderMailSessionModulePmiServiceSecurityConfigSecurityRoleAssignmentServerGroupURLURLProvider


WSCP: All Objects in V3.5.2+ and V4.0WSCP: All Objects in V3.5.2+ and V4.0

WAS V3.5.2+ Supported Objects

ApplicationServerContextDataSourceDrAdminEJBContainerGenericServerHelpJDBCDriverNodeRemoteVirtualHostXMLConfig

Deleted ObjectsEnterpriseApplicationEnterpriseBeanModelServletServletEngineServletRedirectorSessionManagerUserProfileWebApplicationWebResource

WAS V4.0 Supported Objects

ApplicationServerContextDataSourceDrAdminGenericServerHelpJDBCDriverNodeRemoteVirtualHostXMLConfig

Added ObjectsDomainEnterpriseAppJ2CConnectionFactoryJ2CResourceAdapterJMSConnectionFactoryJMSDestinationJMSProviderMailSessionModulePmiServiceSecurityConfigSecurityRoleAssignmentServerGroupURLURLProvider



GraphicalAdministrative

Tools

10/02/01 © Copyright 2001 IBM Corporation WS40ST05.prz 5 of 401 Page 13 of 34

Administrative ConsoleAdministrative Console

Domain Resources

(installed on Nodes)

Enterprise Apps installed on this domain

Node and Application

Servers

Installed J2EE Components in

App Server

Used for Cloning (like V3.5 Model)


AE: Application Installation WizardAE: Application Installation Wizard

An EAR wrapper will be

created for stand-alone

modules

Specify EAR file (created

by AAT)


AE: Additional App Install StepsAE: Additional App Install Steps

Specify Role Mapping for Bean MethodsOnly for methods with no role mappings

Map Users to RolesMap EJB RunAs roles to users

Only allows to modify existing role mappings

Bind EJBs to JNDI namesFor all EJBs

Map EJB References to EJBsMap Resource References to Resources

Only for unmapped references

Secify the Default Datasource for EJB ModuleSpecify Datasource for individual CMP Beans

At the EJB module level or at the single EJB level


AE: Application Install Final StepsAE: Application Install Final Steps

Select Virtual Host for Web ModulesSelect Application Server for EJB and Web ModulesOptionally, generate deployed EJB code

Any changes made during install will be reflected ONLY in the Repository


If the JAR file has been deployed (stubs and skeleton classes generated), you will be prompted with "This application/module has already been deployed. Should it be redeployed?"

Don't confuse Deploy with Install. Deploying an EJB is code generation only.

Manipulating Enterprise ApplicationsManipulating Enterprise Applications

Admin Console allows limited manipulation of application configuration parameters

Browsing ability also more limited than in WAS V3.5Example: the URL of a servlet cannot be looked up using the console, since it resides in the WAR deployment descriptors

Changes made through the console won't be reflected in the original .ear file

in AEs/AEd, some changes can be reflected in the expanded representation of the .ear file in the installedApps directoryin AE, only the repository can be changed by the admin console

Use the AAT to look up and modify deployment descriptors

Changes imply reinstalling the application after modificationMust keep the EAR file available and up-to-date on every node where you expect to need it


Customizing Application ServersCustomizing Application Servers

Set "ping" frequency,

userid, process priority Standard

input, output, and error files

Transaction inactivity

parms

Command line args and heap

size

Tracing, OLT, Resource

Analyzer, etc.


New in V4.0: (General tab)Environment :

Specifies environment variables and their values to be used by the application server. The value of this property is a list of strings in the form, "name=value"

Node Startup State: The state you would like the application server to have each time the node starts. Values are: Stopped, Started, and Last State.

Module Visibility: Specifies the classloader isolation mode to use for the application server. Specify "SERVER" to use one classloader for the entire server.Specify "APPLICATION" to use one classloader per enterprise application. Specify "MODULE" to use one classloader per module. Specify "COMPATIBILITY" for compatibility for applications from WebSphere Application Server V3.5.x and V3.0.2.x.

EJB Modules PropertiesEJB Modules Properties

Edit Name of Modules (EJB and

WAR)

Specify unresolved

resource bindings

Specify unresolved

EJB ref bindings

Assign JDNI

names to beans


ResourcesResources

DataBase

JavaMailDiscussed as part of J2EE JavaMail

URL Providers

J2C Resource AdaptersDiscussed as part of J2EE J2C

JMS ProvidersDiscussed as part of J2EE JMS


JDBC Resource GUIJDBC Resource GUI


URL ConfigurationURL Configuration

URL resources have no runtime service providerUnlike other resources (like JDBC, JavaMail)Java itself could be thought of as the resource provider because it supplies the java.net.URL and java.net.URLConnection classesURL resources implemented the behavior of the resource provider by making use of the Java URL class

Property Description

URL Spec URL specification (e.g., "http://www.ibm.com")

Sample Client Codecontext = new InitialContext();url = (URL)context.lookup("java:comp/env/url/MyURL"); connection = (HttpURLConnection)url.openConnection();

ResourceRef(at Deployment)

Global JNDI name



Browser-BasedThin Client

Admin Console(WAS V4.0 AEs/AEd)


Thin Client AdministrationThin Client Administration

Type in:http://localhost:9090/admin

Loads server-cfg.xml by default

Can load other config files


Thin Client Admin OverviewThin Client Admin Overview

Only one domain can exist

Expand to administervirtual hosts

Expand to administerapplications and the application server

Turn security on and off

Administer "resource providers" (JDBC drivers, ...)


Nodes, Applications, App ServerNodes, Applications, App Server

Only one node can exist

Expand to administer applications

Expand to administerapplication servers

Expand to administer path map variables

Browse installed resource providers


Administering ApplicationsAdministering Applications

Installs an application from an EAR fileUninstalls an application

Exports an application to an EAR fileExports Table.ddl


For AEs, Uninstall does not delete the expanded .ear file from the installedApps directory. Only the configuration information in the repository is removed. If you exit the admin console without saving, you may find that your application is not as uninstalled as you thought.

Administering the App ServerAdministering the App Server

Only one server can exist

Set cmd line args, classpath, heap, log files, ...

Manage HTTP ports, persistent sessions, thread pool

Set cache size, passivation dir, ...

Set lsd port number

Set bootstrap port number

Start/stop traces

Define name server port number

Configure services to stop and start when the server does

set "Use Domain Qualified user"


Only one application server can exist. However, the name need not be "Default Server".

Resource ProvidersResource Providers

Define JavaMail provider (max 1 per server)

Define URL provider and factory (max 1 per server)

Define JDBC drivers and data sources

Define JMS providers (can define multiple, only MQ Series supported)


Saving Changes to the XML FileSaving Changes to the XML File

Step 1: Make changes

Step 4: Click OK

Step 2: Click Save

Step 3: Select Save or Save As + file name


Step 2 is navigational only - Nothing is actually saved until you press "OK"

Application Administration ConsiderationsApplication Administration Considerations

Browser-based Admin Console shows primarily information based on the XML repository.For applications, the console displays:

State (start/stop), application name, .ear, .jar, and .war file names

The console displays deployment descriptors by:Application

EJB Module

Web Module

Application Client Module

You can to edit EJB module bindings


SummarySummary

SummaryCommand Line Admin Tools (AE only)

XMLConfig

WSCP

Graphical Admin ToolsAdmin Console (AE only)

Thin Client (Browser-based) Admin Console (AEs and AEd only)

ResourcesInfoCenter


Lab Preview - Install an Enterprise ApplicationLab Preview - Install an Enterprise Application

Put on the "Deployer" hat

Create a Datasource

Explore the .EAR file, see where things go

Install in AEs

Switch to "System Administrator" hat

Create and Configure a Database in DB2

Start and test the application in AEs

View Deployment Descriptors


WebSphere V4.0 Administrative Tools - IBM Administrative Tools Admin Console ... "") Sample Client...

Documents

Transcript of WebSphere V4.0 Administrative Tools - IBM Administrative Tools Admin Console ... "") Sample Client...