Websphere or Weblogic.........

How to Add a Remote QManager In MQExplorer

2010-07-13T05:44:00.000-07:00

Right click on the Queue Manager  Show/Hide Queue Managers…

Click on the Add… Button

Provide the Qmanager Name and click on the Next Button

Provide the Host Name or the IP Address in the place provided
And also provide the port number

Click on the Finish button.

Wily PMI Settings

2010-06-01T03:31:00.000-07:00

To enablePMI metrics in Wily make the following changes:

In the file IntroscopeAgent.profile:
1)Change the line from introscope.agent.pmi.enable=false to
introscope.agent.pmi.enable=true

2)Change introscope.agent.pmi.enable.* to true to capture the various PMI metrics.
The corresponding setting needs to be set in the Application Console.

For the Application via WebSphere console:

1) Select the server: Servers->Application Servers->

2) Select Custom Services and add/set the following:
a. Classname = com.wily.introscope.api.websphere.IntroscopeCustomService
b. Display Name = Introscope Custom Services
c. Classpath = /WebAppSupport.jar
d. Startup = Checked (true)

3) Performance Monitoring Service and set
a. Startup (true)
b. Select specification level

Note that steps 1, 2, 3 under WebSphere are already part of the model in perf and production.

Make an Undeleteable Folder in windows

2010-04-15T07:47:00.000-07:00

It often happens that some of your folders contain very important data and you delete those folders by mistake. So why not make such folders UNDELETEABLE & avoid such mistakes..! [Works with Windows XP|Vista|Seven]
1]- Open CMD ( Type in Run option, the command 'cmd' or navigate to All Programs->Accessories-> Command Prompt)

2]- Change the directory to where you want to create the folder.Type 'cd..' to exit the current directory. As an example i will be creating the folder in C:, so i will use the 'cd..' command twice to navigate to C:

3]- Type md\lpt1\\ and press enter, the folder now will be in your C:

4]- If you try to delete it, it wont delete. This works on all version of windows.

5]- If you want to delete it just go to 'CMD', navigate to the directory and type
rd\lpt1\\ and press Enter.

Lock a folder in windows XP without any software

2010-04-15T07:41:00.000-07:00

To Lock a folder in windows XP without any software. Follow the steps Below.

1. Make a Folder in C drive rename it as "abc" without quotes.
2. Now open Command Prompt from Start Menu.
3. Type "attrib +s +h C:\abc" without quotes and press enter.
4. This command will Make your folder invisble and it can not be seen even in hidden files and folders
5. To make it visible again type "attrib -s -h C:\abc"
6. You can lock any other folder also by changing the location C:\abc to address of your folder.

How to Install MQ on Redhat Linux

2010-03-19T00:35:00.000-07:00

1.1 User creation

Login as root to install mq

Create following user with group name of “mqm” which will be used to run MQ
groupadd mqm # add group mqm (purpose of gropuadd is to create
a new group account)
useradd -g mqm mqm # add user mqm to group mqm
(gpn)(usrn)
# gpn – groupname
# usrn -- username
(useradd or usermod command is used to add a user to a
group.useradd command creates a new user or update
default new user information.usermod command modifies a
user account i.e. it is useful to add user to existing
group.User account related info is stored in /etc/passwd,
/etc/shadow and /etc/group.)

1.2 Create mount points to install MQ

create mqm folder under /opt and /var where the Websphere MQ gets installed.
create /opt/mqm

root@li-dev01/> cd /opt/
root@li-dev01/opt> mkdir mqm # make it RW to mqm group and 600MB in space capacity
create /var/mqm as above # make it RW to mqm group and 300MB in space capacity
root@li-dev01/var> mkdir mqm

1.3 Kernel configuration parameters

make following kernel changes (/etc/sysctl.conf ): # mq prerequisites
vi /etc/sysctl.conf
#add these propeties if they are not available
kernel.msgmni = 1024
kernel.shmmni = 4096
kernel.shmall = 2097152

edit /etc/sysctl.conf
#add
kernel.sem 250 32000 32 1024

If you wish to load these sysctl values immediately, enter the command sysctl -p.
Note: If you do not issue the sysctl -p command, the new values are loaded when the system is rebooted.

1.4 Max open files

If the system is heavily loaded, you might need to increase the maximum possible number of open files. If your distribution supports the proc filesystem you can query the current limit by issuing the following command: cat /proc/sys/fs/file-max

If you are using a pluggable security module such as PAM (Pluggable Authentication Module), ensure that this does not unduly restrict the number of open files for the ’mqm’ user. For a standard WebSphere MQ queue manager, set the ’nofile’ value to 10240 or more for the ’mqm’ user. We suggest you add this command to a startup script in /etc/rc.d/…

1.5 Max process

A running WebSphere MQ queue manager consists of a number of thread programs, and each connected application will increase the number of threads running in the queue manager processes. You should ensure that the maximum number of processes which the mqm user is allowed to run is not unduly restricted by one of the pluggable security modules such as PAM. Set nproc for the mqm user to 4090 or more.

1.6 Root access privilege
this is needed when doing the MQ installation.

1.7 64bit consideration
Implications of a 64-bit queue manager Note: A 64-bit queue manager is available on the POWER, x86-64 and zSeries (s390x) platforms. When using the 64-bit queue manager, the use of the LIBPATH and LD_LIBRARY_PATH environment variable is not advised.

The recommended way of using WebSphere MQ commands and your applications is as follows:
• Unset LIBPATH and LD_LIBRARY_PATH and build your applications with a built in path to the appropriate WebSphere MQ libraries, this is detailed in the appropriate WebSphere MQ book for your type of WebSphere MQ application.
• If you need to set LIBPATH or LD_LIBRARY_PATH, consider not including /usr/lib in the path you specify in the variable. If you need to include /usr/lib in your LIBPATH or LD_LIBRARY_PATH then in order to avoid errors running 64-bit WebSphere MQ applications or WebSphere MQ commands, consider removing the symbolic links from /usr/lib to the 32-bit WebSphere MQ libraries using the dltmqlnk command. The symbolic links can be restored with the crtmqlnk command. You also need to build your applications with a built in path to the appropriate WebSphere MQ libraries.
Note that both the dltmqlnk command and the crtmqlnk command are scripts, and take no parameters.
• If you cannot use either of the first two options, run your applications in a different environment to the one which issues any WebSphere MQ commands.
Note: WebSphere MQ libraries are in the following locations: /opt/mqm/lib (32-bit libraries) and /opt/mqm/lib64 (64-bit libraries).

2. Installation of Websphere MQ on Linux:

2.1 Install rpm

2.1.1 Log in as root.

extract Websphere MQ files to the current directory(/home/test/Desktop/MQ)
tar -xzvf Websphere MQ for x86 6.0.tar.gz

And make sure all RPMs are in your current directory(/home/test/Desktop/MQ)

2.1.2 Run the mqlicense.sh script.

If you want to view a text-only version of the license, which can be read by a screen-reader, type:
root@li-dev01/MQ>./mqlicense.sh -text_only
The license is displayed.If want to accept the license without it being displayed, you can run the mqlicense.sh script with the -accept option.

# run this command from the current directory where Websphere MQ files are extracted.
root@li-dev01/MQ>./mqlicense.sh -accept
You must accept the license agreement before you can proceed with the installation.

2.1.3 Install components
Use the rpm -ivh command to install each component that you require.
The minimum components you must install are:
• MQSeriesRuntime
• MQSeriesJRE
• MQSeriesServer
• MQSeriesJava
This example shows a minimum installation:

rpm -ivh MQSeriesRuntime-6.0.0-0.i386.rpm MQSeriesSDK-6.0.0-0.i386.rpm MQSeriesServer-6.0.0-0.i386.rpm MQSeriesJava-6.0.0-0.i386.rpm
(At a strech u can install all the rpms or u can install one by one
(1.) rpm -ivh MQSeriesRuntime-6.0.0-0.i386.rpm
(2.) rpm -ivh MQSeriesSDK-6.0.0-0.i386.rpm
(3.) rpm -ivh MQSeriesServer-6.0.0-0.i386.rpm
(4.) rpm -ivh MQSeriesJava-6.0.0-0.i386.rpm)

for 64bit:
rpm -ivh MQSeriesRuntime-7.0.0-0.x86_64.rpm
rpm -ivh MQSeriesJava-7.0.0-0.x86_64.rpm MQSeriesJRE-7.0.0-0.x86_64.rpm MQSeriesServer-7.0.0-0.x86_64.rpm

You can reinstall the /bin/sh shell using RPM, or specify the RPM option –nodeps to disable dependency checking during installation of WebSphere MQ.

Install rest of the components:
rpm -ivh MQSeriesSDK-7.0.0-0.x86_64.rpm
rpm -ivh MQSeriesSamples-7.0.0-0.x86_64.rpm
rpm -ivh MQSeriesClient-7.0.0-0.x86_64.rpm
rpm -ivh gsk7bas-7.0-4.14.i386.rpm
rpm -ivh gsk7bas64-7.0-4.14.x86_64.rpm
rpm -ivh MQSeriesKeyMan-7.0.0-0.x86_64.rpm
rpm -ivh MQSeriesMan-7.0.0-0.x86_64.rpm
rpm -ivh MQSeriesTXClient-7.0.0-0.x86_64.rpm
rpm -ivh MQSeriesEclipseSDK33-7.0.0-0.x86_64.rpm
rpm -ivh MQSeriesConfig-7.0.0-0.x86_64.rpm

when you are installing MQSeriesIES33-7.0.0-0.x86_64.rpm, if you get any error saying that libstdc++.so is needed then go to the link

http://rpmfind.net/linux/rpm2html/search.php?query=libstdc%2B%2B.so.5&submit=Search+...
And search for libstdc++5.0-3.3.3-62745cl.i386.html GNU c++ library and download and Install that rpm.
(or)

use rpm -ivh -nodeps MQSeriesIES33-7.0.0-0.x86_64.rpm

2.1.4 client install:

Install minimum components:
• MQSeriesRuntime
• MQSeriesJRE
• MQSeriesServer
• MQSeriesJava

for 64bit:
rpm -ivh MQSeriesRuntime-7.0.0-0.x86_64.rpm
rpm -ivh MQSeriesJava-7.0.0-0.x86_64.rpm MQSeriesJRE-7.0.0-0.x86_64.rpm MQSeriesServer-7.0.0-0.x86_64.rpm

Then:
rpm -ivh MQSeriesClient-7.0.0-0.x86_64.rpm

================
2.2 Install verification
================

2.2.1 Create a sample Queue

login as MQM user
su - mqm

mqm@li-dev01>crtmqm -q QM_test.queue.manager #-q indicates default queue manager
There are 90 days left in the trial period for this copy of WebSphere MQ.
WebSphere MQ queue manager created.
Creating or replacing default objects for QM_test.queue.manager.
Default objects statistics : 58 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.

# if queue manager is not created and gives AMQ8081 error with 863 code
download fixpack from
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24015717

tar -xvf 6.0.2-WS-MQ-LinuxIA32-FP0005.tar
Make sure that Fix pack is extracted in the directory(/home/test/Desktop/Patch)

rpm -ivh all the below rpms

• MQSeriesRuntime
• MQSeriesJRE
• MQSeriesServer
• MQSeriesJava

# if queue manager is not created and gives AMQ8108 error with 893 code then install IBMJava2-142-ia32-SDK-1.4.2-6.0.i386.rpm from the fix pack,

when you are installing this rpm if you get any error saying that libXp.so, then go to the link and download that and install this rpm
ftp://ftp.pbone.net/mirror/ftp.centos.org/5.4/os/x86_64/CentOS/libXp-1.0.0-8.1.el5.i386.rpm

mqm@li-dev01>strmqm
There are 90 days left in the trial period for this copy of WebSphere MQ.
WebSphere MQ queue manager ‘QM_test.queue.manager’ starting.
5 log records accessed on queue manager ‘QM_test.queue.manager’ during the log replay phase.
Log replay for queue manager ‘QM_test.queue.manager’ complete.
Transaction manager state recovered for queue manager ‘QM_test.queue.manager’.
WebSphere MQ queue manager ‘QM_test.queue.manager’ started.

mqm@li-dev01>runmqsc
5724-H72 (C) Copyright IBM Corp. 1994, 2008. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM_test.queue.manager.

define qlocal (test_QL.queue)
1 : define qlocal (test_QL.queue)
AMQ8006: WebSphere MQ queue created.
end
2 : end
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
mqm@li-dev01>

2.2.2 Test the sample queue
mqm@li-dev01>cd /opt/mqm/samp/bin
mqm@li-dev01>./amqsput test_QL.QUEUE
Sample AMQSPUT0 start
target queue is test_QL.QUEUE
Sample AMQSPUT0 end

# if /opt/mqm/samp/bin is not found install rpm MQSeriesSamples.

Sample AMQSPUT0 end
mqm@li-dev01>./amqsget test_QL.QUEUE
Sample AMQSGET0 start
message
no more messages
Sample AMQSGET0 end

3. Uninstalling Websphere MQ in Linux:

Remove install RPMs

login as root

root@websphere mwinstall]# rpm -ivh IBMJava2-SDK-1.4.2-0.0.i386.rpm to install, so I queried to find out what the software name of the rpm was as you cannot use the rpm filename that you used to install the rpm.

root@websphere mq]# rpm -qa | grep IBM
IBMJava2-SDK-1.4.2-0.0

rpm -e IBMJava2-SDK-1.4.2-0.0

This worked however for the other rpm;s I had to remove the fix-packs first

Remove fix pack rpm's

Use this command to see which Websphere MQSeries base rpms and fixpacks are installed
root@websphere mq]# rpm -qa | grep MQSeries

I used rpm -ivh IBMJava2-142-ia32-SDK-1.4.2-6.0.i386.rpm to apply fix pack
So I used rpm -e IBMJava2-142-ia32-SDK-1.4.2-6.0

install: rpm -ivh MQSeriesRuntime-U809950-6.0.2-2.i386.rpm
remove: rpm -e MQSeriesRuntime-U809950-6.0.2-2

install: rpm -ivh MQSeriesServer-U809950-6.0.2-2.i386.rpm
remove: rpm -e MQSeriesServer-U809950-6.0.2-2

install: rpm -ivh MQSeriesJava-U809950-6.0.2-2.i386.rpm
remove: rpm -e MQSeriesJava-U809950-6.0.2-2

Remove base rpm's

I had to do in this order

rpm -e MQSeriesJava-6.0.0-0

rpm -e MQSeriesServer-6.0.0-0

rpm -e MQSeriesRuntime-6.0.0-0

Query to make sure they have all been removed

rpm -qa | grep MQSeries

Remove MQ directories

/opt/mqm # cd /opt , rm -rf mqm
/var/mqm # cd /var , rm -rf mqm

Switching Users: su in Linux

2010-03-17T02:52:00.000-07:00

Switching Users: su

To switch to another user, we use su command

Running su without any parameter will automatically try to login you to root user.

You’ll be prompted for the root password and, if you enter it correctly, will drop down to a root shell.

Example:

[tirumal@myhostname ~]$ su

It will prompt for the password, if you give the correct password you will be logged into the root shell.

If you are already in the root user(shell) and want to switch to another ID, you don’t need to enter the password when you issue this command.

If u want to login to with a particular user, then

[tirumal@myhostname ~]$ su raj
(Or)
[tirumal@myhostname ~]$ su - raj

The difference is,if we are using optional hyphen (-), this is tells us to switch identities and run the login scripts for that user (use the user specific environmental variables).
If there is no hyphen, the shell will take the globally set environment variables.

What is the difference between a Portal server and an Application server?

2010-03-02T23:42:00.001-08:00

What is the difference between a Portal server and an Application server?

Before understanding portal server, we will have to understand portal. As we know, portal in nothing but a web application. In simple words, a portal server is an application having a portal and its management capabilities. In traditional web application, we have a separate management section for managing the web application. Portal server provides the application as well as that management section. In other words, a portal server is an application deployed inside application server.

Whereas, an application server is a system that provides the execution environment that is at the core of network computing or web-based architectures, providing a full set of services.

Resources for MQ(Link)

2009-12-29T21:41:00.000-08:00

WebSphere MQ Documentation Index

The following are the topics that we get from the link

WebSphere MQ Introduction Documentation
WebSphere MQ Cluster Documentation
WebSphere MQ .NET Documentation
WebSphere MQ JMS Documentation
WebSphere MQ Pub/Sub Documentation
WebSphere MQ Security Documentation
WebSphere MQ SSL Documentation
Troubleshooting Documentation
General Documentation

http://www.capitalware.biz/library_wmq.html

What are metrics that are collected by Wily

2009-12-03T22:33:00.000-08:00

The following is the data that is collected by Wily

1.) CORBA method timers
2.) Remote Method Invocation (RMI) method timers
3.) Thread Counters
4.) Network bandwidth
5.) JDBC update and query timers
6.) Servlet timers
7.) Java Server Pages(JSP) timers
8.) System logs
9.) File system input and output bandwith meters
10.)Available and used memory
11.) EJB (Enterprise JavaBean) timers

Tools for trouble shooting WAS

2009-11-23T23:01:00.000-08:00

Contains informative links for trouble shooting issues with WAS.

Some helpful tools for trouble shooting WAS issues:

ThreadAnalyzer: IBM Thread and Monitor Dump (javacore) Analyzer for Java Technology
HeapAnalyzer: views heapdumps(out of memory or memory leak conditions)
VerboseGC Viewer: IBM Pattern Modeling and Analysis Tool for Java Garbage Collector

From this link you can download the latest versions of each tool: http://www.alphaworks.ibm.com/tech/jca

The WAS InfoCenter for WAS 5.1 ND is here:
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1/index.jsp

In case ThreadAnalyzer is no longer available, IBM has a new set of tools called IBM Support Assistant (http://www.ibm.com/software/support/isa), into which you can add ThreadAnalyzer.
Info on the new ThreadAnalyzer is available here -> http://www.ibm.com/support/docview.wss?uid=swg21259758

Also, the other tools mentioned below are available as follows (use the Tabs on top to see the OverView):

HeapAnalyzer: -> http://www.alphaworks.ibm.com/tech/heapanalyzer/download

VerboseGC Viewer: IBM Pattern Modeling and Analysis Tool for Java Garbage Collector: http://www.alphaworks.ibm.com/tech/pmat/download

Install JBoss Application Server

2009-11-23T03:25:00.000-08:00

Install JBoss Application Server

1. Copy jboss-4.2.2.GA.zip from google.com to local desktop
2. Unzip zip into c:\ (when you unzip files will be copied under c:\jboss-4.2.2.GA)
3. Open command prompt and execute:
C:\jboss-4.2.2.GA\bin\run.bat --configuration=default -b localhost

4. Verify you are able to view webpage for http://127.0.0.1:8080

How to apply fix pack for websphere 6.1(demo_video)

2009-11-16T06:09:00.000-08:00

How to apply fix pack for websphere 6.1(demo_video)

http://download.boulder.ibm.com/ibmdl/pub/software/dw/lotus/IEA/Viewlets/Install_WAS_6.1_FP/install_was_61_fp_viewlet_swf.html

Run Websphere on other user than root

2009-11-10T03:02:00.000-08:00

For his installation Websphere need to use root account. The installation's script don't propose the creation or utilisation of an other user account. This is disturbing because all the objets created by Webphere belong to root.
But it's easy to correct this problem.

Modifications to do
-------------------
I take in account that you have created the user and the group that you wanted. After that you just have to connect yourself to the Websphere's administration console to change some parametres in this page : Execution process parameters.
You can go to this page thanks to the menu Servers > Applications server > name_of_your_server and (in the options of this page) Server Infrastructure > Gestion des processus and Java > Processus Execution.

So you can change the user and group wich is going to run the principal process of Websphere ( java ). With that, all objects created by websphere (images, files, ...) are accessible even to other user than root.

Warning : after this you must change the owner of all files and directorys read by Websphere ( $WAS_HOME/ and your WebApp and all other required files)

ref: http://www.berthou.com/us/category/websphere/

.nifregistry and vpd.properties files

2009-11-03T23:47:00.000-08:00

.nifregistry and vpd.properties files

The installer program for WebSphere Process Server uses the InstallShield MultiPlatform (ISMP) program to install code. The .nifregistry and vpd.properties files list program components that are currently installed. The file helps ISMP and the installer programs of WebSphere Process Server recognize previous installations of WebSphere Process Server and control options for new installations.
Location of the .nifregistry file
The location of the .nifregistry file varies per operating platform:

* Icon indicating AIX platforms On AIX® platforms: The root directory /usr/.ibm/.nif/.nifregistry or the non-root directory /.ibm/.nif/.nifregistry
* Icon indicating HP-UX platforms On HP-UX platforms: The root directory /opt/.ibm/.nif/.nifregistry or the non-root directory /.ibm/.nif/.nifregistry
* Icon indicating i5/OS platform only On i5/OS® platforms: The root directory /QIBM/WAS/.ibm/.nif/.nifregistry
* Icon indicating Linux platforms On Linux® platforms: The root directory /opt/.ibm/.nif/.nifregistry
* Icon indicating Solaris platforms On Solaris platforms: The root directory /opt/.ibm/.nif/.nifregistry or the non-root directory /.ibm/.nif/.nifregistry
* Icon indicating Windows platforms On Windows® platforms: The root directory C:\Windows\.nifregistry

For example:

NON-ROOT user: fvttest
NON-ROOT-HOME: /home/fvttest .nifregistry dir: /home/fvttest/.ibm/.nif/.nifregistry

Examples of the .nifregistry file

For a particular product the .nifregistry file contains one entry (line) each for every PAK that gets installed and one entry (line) for the product offering (e.g. WebSphere® Business Integration, Enterprise Service Bus, and so on).
The following line shows an example of a PAK entry in the .nifregistry file:

paklocationuri="zip:///C:/IBM/WebSphere/ProcServer/properties/version/nif/backup/
wbi.primary.pak" productid="WBI"/
productid=""/>

The following line shows an example of a product offering entry in the .nifregistry file:

lastvisited="2007-10-29 00:07:43-0500" productid="WBI" version="6.1.0.0"/>
productid="" version="6.1.0.0"/>

Cleaning up the .nifregistry file after a failed uninstallation
For these steps to clean the .nifregistry file after a failed uninstallation:

1. Backup the .nifregistry file.
2. Open the .nifregistry file in a text editor (ensure that line wrapping is turned off).
3. Search and delete all lines that have the and in them where is the install location where you have a failed uninstallation and is the product offering ID of the product that you are trying to uninstall.
4. Save the .nifregistry file and close the text editor.

Icon indicating HP-UX platforms Icon indicating Solaris platforms Operating system exceptions for using the vpd.properties file

* ISMP uses the vpd.properties file to track WebSphere products that it installs on all platforms but Solaris and HP-UX.
* ISMP uses native operating system registration on these platforms when installing as root, and does not create a vpd.properties file.

When installing as a non-root installer, the installer programs create a vpd.properties file on all platforms, including Solaris and HP-UX.

Situations that require you to edit the vpd.properties file

Certain situations require you to edit the vpd.properties file before reinstalling WebSphere Process Server. The uninstaller programs for WebSphere Process Server edit the vpd.properties while uninstalling a product, to remove entries for the product and any of its features that might have entries in the file.
Some situations that occur require you to manually remove product entries from the vpd.properties file before you can reinstall a product. These situations include:

* Bypassing the uninstaller program to uninstall a product manually
* Uninstalling a product manually when the uninstaller program is not present or is not working

If the vpd.properties file has entries for a product that you uninstalled, you must edit the file and remove the entries. If you do not edit the vpd.properties file to remove entries for a product or features of a product, you cannot reinstall the product into the same directory structure. If product entries in the vpd.properties file are present, the installer program reads the vpd.properties file, determines that the product is already installed, and displays the panel that prompts you to install additional features into the existing product or to install the binaries a second time. Unfortunately, the existing binaries might not be valid at that point. The installer program does not verify the products that it finds listed in the vpd.properties file.
Location of the vpd.properties file
The location of the vpd.properties file varies per operating platform:

* Icon indicating AIX platforms On AIX platforms: The root directory or the usr/lib/objrepos directory
* Icon indicating i5/OS platform only On i5/OS platforms: /InstallShield/VitalProductData/vpd.properties
* Icon indicating Linux platforms On Linux platforms: The root directory
* Icon indicating Windows platforms On Windows platforms: Installation directory of the operating system, such as the C:\WINNT directory or the C:\windows directory

Example of the vpd.properties file

The following example shows the entry for the vpd.properties file for Version 6.1.0.0 of the WebSphere product on a Windows platform. The example shows entire lines but wraps each line for formatting purposes.

WSEAA61|6|1|0|0|6.1.0.0|1=IBM WebSphere Process Server|IBM WebSphere Process Server|
IBM WebSphere Process Server V6.1.0.0|IBM|http://www.ibm.com|6.1.0.0|C:\Program Files\
IBM\WebSphere\ESB1|0|0|1|WSEAA61|6|1|0|0|6.1.0.0|1|0|false|"_uninst" "uninstall.jar" "
uninstall.dat" ""|true|3|WSEAA61|6|1|0|0|6.1.0.0|1

Identifying entries in the vpd.properties file

Use the following table to help identify product entries.
Table 1. Identifer in the vpd.properties file for WebSphere productsIdentifier Product
WSE...61 All version 6.1 products use this identifier to identify the core product files:

* WebSphere Process Server, Version 6.1
* WebSphere Enterprise Service Bus, Version 6.1

href:http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r1mx/index.jsp?topic=/com.ibm.websphere.wps.610.doc/doc/rins_vpd.html

configuration archive file(CAR File)

2009-11-03T23:41:00.000-08:00

A configuration archive (CAR) file captures the configuration of a standalone application server profile for later restoration on another application server node. The CAR can help clone the original profile to another machine or system.

A configuration archive file is an exported configuration file from an existing standalone application server profile and contains all application server configuration data including security settings, resources, defined ports, and so on. The advantage of using a CAR is that all of this configuration, including any enterprise archive (EAR) files, can be reliably restored to many application server nodes. Importing a configuration archive also offers some performance advantages over creating a standalone application server in the normal way.

The WebSphere Configuration Archive is new features in WebSphere Application Server v6.0.
This feature allows a set of complete or subset of WebSphere configuration archive. WebSphere
Application Server V6 provides a mechanism that allows you to export certain profiles, or server
objects from a profile, to an archive. The archive can be distributed and imported to other
installations. An exported archive is a zip file of the config directory with host-specific information
removed. The recommended extension of the zip file is .car. The exported archive can be the
complete configuration or a subset. Importing the archive creates the configurations defined in the
archive. The target configuration of an archive export / import can be a specific server or an entire
profile.
To use an archive you would:
1. Export a WebSphere configuration. This creates a zip file with the configuration.
2. Unzip the files for browsing or update for use on other systems. For example, you might need
to update resource references.
3. Send the configuration to the new system. An import can work with the zip file or with the
expanded format.
4. Import the archive. The import process requires that you identify the object in the configuration
you want to import and the target object in the existing configuration. The target can be the
same object type as the archive or its parent:
– If you import a server archive to a server configuration the configurations are merged.
– If you import a server archive to a node, the server is added to the node.
A tutorial on creating and using archives can be found in the Information Center. See
ftp://ftp.software.ibm.com/software/eod/was/6.0/SystemManagement/WASv6_SM_Configuration_
Archives/playershell.swf
Prof ile archives
The following command can be used to create an archive of a profile:
$AdminTask expor tWasprof ile {-archive }
You can only create an archive of an unfederated profile (standalone application server).
$AdminTask impor tWasprof ile {-archive }
exportWasprofile:
Use the exportWasprofile command to export the entire cell configuration to a configuration
archive. (myArchive.car)
• Using Jacl:
22 5/15/2006
$AdminTask exportWasprofile {-archive c:\myCell.ear}
• Using Jython string:
AdminTask.exportWasprofile('[-archive c:\myCell.ear]')
Interactive mode example usage:
• Using Jacl:
$AdminTask exportWasprofile {-interactive}
• Using Jython string:
AdminTask.exportWasprofile ('[-interactive]')
importWasprofile:
Use the importWasprofile command to import a cell configuration in the configuration archive to
the system. Only a base single server configuration is supported for this command.
• Using Jacl:
$AdminTask importWasprofile {-archive c:\myCell.ear}
• Using Jython string:
AdminTask.importWasprofile('[-archive c:\myCell.ear]')
Interactive mode example usage:
• Using Jacl:
$AdminTask importWasprofile {-interactive}
• Using Jython string:
AdminTask.importWasprofile ('[-interactive]')

ref: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/cins_if_config_archive.html

WebSphere Password Decoder

2009-11-03T05:30:00.000-08:00

WebSphere Password Decoder

This utility can decode WebSphere encoded passwords.
If you have lost your password(s), use this utility to recover them.

url: http://www.sysman.nl/wasdecoder/

Plug point for custom password encryption in websphere

2009-10-26T02:05:00.000-07:00

Plug point for custom password encryption

Problem(Abstract) A plug point for custom password encryption must be created to encrypt and decrypt all passwords in WebSphere Application Server that are currently encoded or decoded using Base64-encoding. The implementation class of this plug point has the responsibility for managing keys, determining the encryption algorithm to use, and for protecting the master secret.

Cause A custom provider of this plug point must implement an interface designed to encrypt and decrypt passwords. The interface is called by the WebSphere Application Server run time whenever the custom plug point is enabled. The custom algorithm becomes one of the supported algorithms when the plug point is enabled. Resolving the problem How to create, enable or disable a plug point for custom password encryption:
Plug point for custom password encryption
A plug point for custom password encryption can be created to encrypt and decrypt all passwords in WebSphere Application Server that are currently encoded or decoded using Base64-encoding. The implementation class of this plug point has the responsibility for managing keys, determining the encryption algorithm to use, and for protecting the master secret. The WebSphere Application Server run time stores the encrypted passwords in their existing locations preceded with {custom:alias} tags instead of {xor} tags. The “custom” part of the tag indicates that it is a custom algorithm. The “alias” part of the tag is specified by the custom implementation, which helps to indicate how the password was encrypted. The implementation can include the key alias, encryption algorithm, encryption mode, or encryption padding.
A custom provider of this plug point must implement an interface designed to encrypt and decrypt passwords. The interface is called by the WebSphere Application Server run time whenever the custom plug point is enabled. The custom algorithm becomes one of the supported algorithms when the plug point is enabled. Other supported algorithms include {xor} (standard base64 encoding) and {os400} (used on the iSeries platform).
The interface example shown below is com.ibm.wsspi.security.crypto.CustomPasswordEncryption:
package com.ibm.wsspi.security.crypto;
public interface CustomPasswordEncryption
{

/**
* The encrypt operation takes a UTF-8 encoded String in the form of a byte[].
* The byte[] is generated from String.getBytes("UTF-8").
* An encrypted byte[] is returned from the implementation in the EncryptedInfo
* object. Additionally, a logically key alias is returned in EncryptedInfo so
* which is passed back into the decrypt method to determine which key was used
* to encrypt this password. The WebSphere Application Server runtime has no
* knowledge of the algorithm or key used to encrypt the data.
*
* @param byte[]
* @return com.ibm.wsspi.security.crypto.EncryptedInfo
* @throws com.ibm.wsspi.security.crypto.PasswordEncryptException
**/
public EncryptedInfo encrypt (byte[] decrypted_bytes) throws PasswordEncryptException;

/**
* The decrypt operation takes the EncryptedInfo object containing a byte[]
* and the logical key alias and converts it to the decrypted byte[]. The
* WebSphere Application Server runtime will convert the byte[] to a String
* using new String (byte[], "UTF-8");
*
* @param com.ibm.wsspi.security.crypto.EncryptedInfo
* @return byte[]
* @throws com.ibm.wsspi.security.crypto.PasswordDecryptException
**/
public byte[] decrypt (EncryptedInfo info) throws PasswordDecryptException;

/**
* This is reserved for future use and is currently not called by the
* WebSphere Application Server runtime.
*
* @param java.util.HashMap
**/
public void initialize (java.util.HashMap initialization_data);
}
The com.ibm.wsspi.security.crypto.EncryptedInfo class contains the encrypted bytes along with the user-defined alias associated with the encrypted bytes. This information is passed back into the encryption method to help to determine how the password was originally encrypted.
package com.ibm.wsspi.security.crypto;
public class EncryptedInfo
{
private byte[] bytes;
private String alias;

/**
* This constructor takes the encrypted bytes and a keyAlias as parameters.
* This is used to pass to or from the WebSphere Application Server runtime to
* enable the runtime to associate the bytes with a specific key used to encrypt
* the bytes.
*/

public EncryptedInfo (byte[] encryptedBytes, String keyAlias)
{
bytes = encryptedBytes;
alias = keyAlias;
}

/**
* This returns the encrypted bytes.
*
* @return byte[]
*/
public byte[] getEncryptedBytes()
{
return bytes;
}

/**
* This returns the key alias. The key alias is a logical string associated
* with the encrypted password in the model. The format is
* {custom:keyAlias}encrypted_password. Typically, just the key alias is placed
* here, but algorithm information can also be returned.
*
* @return String
*/
public String getKeyAlias()
{
return alias;
}

}
The encryption method is called for password processing whenever the custom class is configured and custom encryption is enabled. The decryption method is called whenever the custom class is configured and the password contains the {custom:alias} tag . The custom:alias tag is stripped prior to decryption.
To enable custom password encryption, two properties must first be configured:
property com.ibm.wsspi.security.crypto.customPasswordEncryptionClass
Defines the custom class that implements the password encryption interface (com.ibm.wsspi.security.crypto.CustomPasswordEncryption).
com.ibm.wsspi.security.crypto.customPasswordEncryptionEnabled
Defines when the custom class is used for default password processing. When passwordEncryptionEnabled is not specified or set to false, and the passwordEncryptionClass is specified, the decryption method is called whenever a {custom:alias} tag still exists in the configuration repository.
If the custom implementation class defaults to com.ibm.wsspi.security.crypto.CustomPasswordEncryptionImpl, and this class is present in the classpath, then encryption is enabled by default. This simplifies the enablement process for all nodes. It is not necessary to define any other properties except for those the custom implementation requires. To disable encryption, but still use this class for decryption, specify the class com.ibm.wsspi.security.crypto.customPasswordEncryptionEnabled=false.
To configure custom password encryption, configure both of these properties in security.xml. The custom encryption class (com.acme.myPasswordEncryptionClass) must be placed in a JAR file in the ${WAS_INSTALL_ROOT}/classes directory in all WebSphere Application Server processes. Every configuration document that contains a password (security.xml and any application bindings that contain RunAs passwords), must be saved before all of the passwords become encrypted with the custom encryption class.
For client side property files such as sas.client.props, soap.client.props, use the PropFilePasswordEncoder.bat (Windows) or PropFilePasswordEncoder.sh (UNIX) script to enable custom processing. This script must have the two properties configured as system properties on the Java™ command line of the script. The same tools used for encoding and decoding can be used for encryption and decryption when custom password encryption is enabled.
Additional information
Whenever a custom encryption class encryption operation is called, and it throws a runtime exception or a defined PasswordEncryptException, the WebSphere Application Server run time uses the (xor} algorithm to encode the password. This prevents the password from being stored in plain text. Once the problem with the custom class has been resolved, it automatically encrypts the password the next time the configuration document is saved.
When a RunAs role is assigned a user ID and password, it currently is encoded using the WebSphere Application Server encoding function. Therefore, once the custom plug point is configured to encrypt the passwords, it encrypts the passwords for the RunAs bindings as well. If the deployed application is moved to a cell that does not have the same encryption keys, or the custom encryption is not yet enabled, it causes a login failure since the password is not readable.
One of the responsibilities of the custom password encryption implementation is to manage the encryption keys. This class must decrypt any password that it encrypted. Any failure to decrypt a password causes that password to be unusable, and the password must be changed in the configuration. All encryption keys must be made available for decryption until there are no passwords left using those keys. The master secret must be maintained by the custom password encryption class to protect the encryption keys.
You can manage the master secret by using a stash file for the keystore, or by using a password locator that enables the custom encryption class to locate the password so that it can be locked down.

Enabling custom password encryption
Complete the following steps to enable custom password encryption:
1. Add the following system properties for every server and client process. For server processes, update the server.xml for each process. Add these properties as a genericJvmArgument preceded by a -D prefix.

com.ibm.wsspi.security.crypto.customPasswordEncryptionClass=com.
acme.myPasswordEncryptionClass
com.ibm.wsspi.security.crypto.customPasswordEncryptionEnabled=true

Note: If the custom encryption class name is com.ibm.wsspi.security.crypto.CustomPasswordEncryptionImpl, it is automatically enabled when this class is present in the classpath. Do not define the system properties listed above when the custom implementation has this package and class name. To disable encryption for this class, you must specify com.ibm.wsspi.security.crypto.customPasswordEncryptionEnabled=false as a system property.

2. Add the JAR file containing the implementation class to the ${WAS_INSTALL_ROOT}/classes directory so that it can be loaded by the WebSphere Application Server runtime.
3. Restart all server processes.
4. Edit each configuration document that contains a password and save the configuration. All password fields are then run through the WSEncoderDecoder utility, which calls the plug point when it is enabled. Tags {custom:alias} appear in the configuration documents. The passwords, even though they are encrypted, are still Base64-encoded. They appear similar to encoded passwords except for the tags difference.
5. Any passwords that are in client-side property files must be encrypted using the PropsFilePasswordEncoder.bat (Windows) or PropsFilePasswordEncoder.sh (UNIX) utility. This utility requires that the properties listed above are defined as system properties in the script to encrypt new passwords instead of encoding them.
6. To decrypt passwords from client JVMs, the properties listed above must be added as system properties for each client utility.
7. For Network Deployment (ND) environments, the order in which enablement occurs is important. Ensure that all nodes have the custom encryption classes in their classpaths prior to enabling this function. When adding a new node to a cell that contains password encryption, the new node must contain the custom encryption classes prior to using addNode. Consider the following ND enablement scenarios:
a. StandAloneProfile is encrypting passwords with a different key prior to federation to a deployment manager cell. For this scenario, you must uninstall custom password encryption to ensure that the configuration has {xor} tags preceding the passwords prior to running addNode. The same implementation of the plug point must be in the /classes directory prior to running addNode, and the proper configuration properties are set so that the new node can recognize the encrypted password format of the security.xml after federation has completed.
b. StandAloneProfile does not have password encryption configured prior to federation to a deployment manager cell. The same implementation of the plug point must be in the /classes directory prior to running addNode, and the proper configuration properties are set so that the new node can recognize the encrypted password format of the security.xml after federation has completed.
c. If enabling custom password encryption in a cell with multiple nodes present, update the correct configuration properties and have the custom password encryption implementation class located on all nodes. Stop all processes in the cell, and then start the deployment manager. Use the administrative console to edit the security configuration and then save it. Ensure that the passwords are encrypted by looking at security.xml to see if the passwords are preceded by {custom:alias} tags.
d. Run syncNode on each node, and start them up one at a time. If any nodes fail to start, make sure that they have custom password encryption enabled properly in each security.xml and the implementation class is in the /classes directory appropriate for the platform.

Disabling custom password encryption
Complete the following steps to disable custom password encryption:
1. Change the com.ibm.wsspi.security.crypto.customPasswordEncryptionEnabled property to be false in security.xml, but leave the com.ibm.wsspi.security.crypto.customPasswordEncryptionClass property configured. Any passwords in the model which still have the tag {custom:alias} are decrypted by using the customer password encryption class.
2. If an encryption key is lost, any passwords encrypted with that key can not be retrieved. To recover a password, retype the password in the password field in plaintext and save the document. The new password must be written out using encoding with the {xor} tag. This can be performed by using scripting or from the administrative console. com.ibm.wsspi.security.crypto.customPasswordEncryptionClass=com.
acme.myPasswordEncryptionClass
com.ibm.wsspi.security.crypto.customPasswordEncryptionEnabled=false
3. Restart all processes to make the changes effective.
4. Edit each configuration document that contains an encrypted password and save the configuration. All password fields are then run through the WSEncoderDecoder utility, which calls the plug point due to the presence of the {custom:alias} tag. The {xor} tags reappear in the configuration documents after they are saved.
5. Any passwords that are in client-side property files must be decrypted and then encoded using the PropsFilePasswordEncoder.bat (Windows) and PropsFilePasswordEncoder.sh (UNIX) utility. If the encryption class is specified, but custom encryption is disabled, running this utility converts the encryption to encoding and causes the {xor} tags to reappear.

6. Disable custom password encryption from the client Java virtual machines (JVMs) by adding the system properties listed above to all client scripts. This enables the code to decrypt passwords, but it is not used to encrypt them again. The {xor} algorithm becomes the default for encoding. Leave the custom password encryption class defined for a period of time in the event that any encrypted passwords still exist in the configuration.

ref:http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21210244

Keywords that are used in websphere(interview questions)

2009-10-23T01:42:00.000-07:00

* abstract schema
Part of the deployment descriptor for an entity bean that is used to define the bean relationships, persistent fields, or query statements.
* * access bean *
An enterprise bean wrapper that is typically used by client programs, such as JavaServer Pages (JSP) files and servlets. Access beans hide the complexity of using enterprise beans and improve the performance of reading and writing multiple enterprise bean properties.
* * access control *
In computer security, the process of ensuring that only authorized users can access the resources of a computer system in authorized ways.
* access control list (ACL)
In computer security, a list that is associated with an object that identifies all the subjects that can access the object and their specific access rights.
* * access ID *
The unique identification of a user that is used during authorization to determine if access is permitted to the resource.
* * access intent *
Metadata that optimizes the runtime behavior of an entity bean with respect to concurrency control, resource management, and database access strategies.
* * access intent policy *
A grouping of access intents that governs a type of data access pattern for enterprise bean persistence.
* * access point group *
A collection of core groups that defines the set of core groups in the same cell or in different cells that communicates with each other.
* accessibility
An attribute of a software or hardware product that is usable by individuals who have disabilities.
* * ACL *
See access control list.
* activation
In EJB, the process of transferring an enterprise bean from secondary storage to memory. (Sun)
* * adapter *
A mechanism for connecting two unlike parts or machines, or for electrically or physically connecting a device to a computer or to another device.
* * add rule*
A conditional expression that states the conditions necessary for a given action to occur.
* * administrative agent *
A program that provides administrative support without requiring a direct connection to a database.
* * agent *
A function that represents a requester to a server.
* alarm listener
A type of asynchronous bean that is called when a high-speed transient alarm expires.
* * algorithm *
A set of well-defined rules for the solution of a problem in a finite number of steps. For example, a full statement of an arithmetic procedure for evaluating "sin x" to a stated precision.
* * algorithm mapping *
A process by which service providers can define the mapping of Uniform Resource Identifier (URI) algorithms to cryptographic algorithms that are used for Extensible Markup Language (XML) digital signature and XML encryption.
* * Apache *
An open-source Web server. IBM offers a Web server, called the IBM HTTP Server, which is based on Apache.
* * API *
See application programming interface.
* * applet *
A small application program that performs a specific task and is usually portable between operating systems. Often written in Java, applets can be downloaded from the Internet and run in a Web browser.
* application
One or more computer programs or software components that provide functionality in direct support of a specific business process or processes.
* * application assembly *
The process of creating an enterprise archive (EAR) file containing all the files related to an application as well as an Extensible Markup Language (XML) deployment descriptor for the application.
* * applet client *
A client that runs within a browser-based Java runtime environment, and is capable of interacting with enterprise beans directly instead of indirectly through a servlet.
* application client
In J2EE, a first-tier client component that executes in its own Java virtual machine. Application clients have access to some J2EE platform APIs, for example JNDI, JDBC, RMI-IIOP, and JMS. (Sun)
* * application client module *
A Java archive (JAR) file that contains a client that accesses a Java application. The Java application runs inside a client container and can connect to remote or client-side Java 2 Platform, Enterprise Edition (J2EE) resources.
* * application programming interface (API) *
An interface that allows an application program that is written in a high-level language to use specific data or functions of the operating system or another program.
* * Application Response Measurement (ARM) *
An application programming interface that is developed by a group of leading technology vendors that can be used to monitor the availability and performance of business transactions within and across diverse applications and systems.
* * Application Response Measurement (ARM) agent*
The implementation of the ARM standard by an implementation provider.
* * application server *
A server program in a distributed network that provides the startup environment for an application program.
* application server root
The top directory for a WebSphere Application Server node.
* ARM
See Application Response Measurement.
* artifact
A physical piece of information that is used or produced by a software development process. Examples of artifacts include models, source files, scripts, and binary executable files.
* * association *
1. For Extensible Markup Language (XML) documents, the linkage of the document itself to the rules that govern its structure, which can be defined by a document type definition (DTD) or an XML schema. 2. In enterprise beans, a relationship that exists between two container-managed persistence (CMP) entity beans. Two types of associations exist: one-to-one and one-to-many.
* asymmetric algorithm
See public-key algorithm.
* * asymmetric cryptography *
In computer security, pertaining to the use of different keys for encryption and decryption; a synonym for public key cryptography.
* * asynchronous bean *
A Java object or an enterprise bean that a Java 2 Platform, Enterprise Edition (J2EE) application can run asynchronously.
* * asynchronous messaging *
A method of communication between programs in which a program places a message on a message queue, then proceeds with its own processing without waiting for a reply to its message. See also synchronous messaging.
* atomic
Pertaining to transaction changes to the state of resources: either all occur or none occur. The atomic characteristic maintains data integrity by making sure that some updates are not made while others fail.
* * authentication *
In computer security, a process that ensures that the identities of both the sender and the receiver of a network transaction are true.
* authenticity
The validation of client and server identities during a Secure Sockets Layer (SSL) connection by both communicating parties using public key cryptography and asymmetric cryptography.
* * authorization *
The process of granting a user either complete or restricted access to an object, resource, or function.
* * authorization table *
A table that contains the role to user or group mapping information that identifies the permitted access of a client to a particular resource.
* * automatic restart management *
The facilities that detect failures and manage server restarts.
* * AXIS *
An implementation of the Simple Object Access Protocol (SOAP) on which Java Web services can be implemented.
* base edition
A deployed application that has no associated or specific edition information.
* * basic authentication*
An authentication method that uses a user name and a password.
* * bean *
A definition or instance of a JavaBeans component. See also JavaBeans.
* * Bean Scripting Framework *
An architecture for incorporating scripting language functions to Java applications.
* * bean-managed messaging *
A function of asynchronous messaging that gives an enterprise bean complete control over the messaging infrastructure.
* * bean-managed persistence (BMP) *
Pertaining to an entity bean that manages its own persistence. See also container-managed persistence.
* * bean-managed transaction (BMT) *
The capability of the session bean, servlet, or application client component to manage its own transactions directly, instead of through a container.
* * bind *
To establish a connection between software components on a network using an agreed-to protocol. In Web services, the bind operation occurs when the service requestor invokes or initiates an interaction with the service at run time using the binding details in the service description to locate, contact, and invoke the service.
* binding
A temporary association between a client and both an object and a server that exports an interface to the object. A binding is meaningful only to the program that sets it and is represented by a bound handle.
* block decryption
Symmetric algorithms that decrypt a block of data at one time.
* block encryption
Symmetric algorithms that encrypt a block of data at one time.
* BMP
See bean-managed persistence.
* BMT
See bean-managed transaction.
* BOM
See byte order mark.
* bootstrap server
An application server that runs the SIB service.
* * bootstrapping *
The process by which an initial reference of the naming service is obtained. The bootstrap setting and the host name form the initial context for Java Naming and Directory Interface (JNDI) references.
* * bottleneck *
A place in the system where contention for a resource is affecting performance.
* * bridge interface *
A node and a server that run a core group bridge service.
* broker archive
A file that is the unit of deployment to the broker that can contain any number of compiled message flow and message set files and a single deployment descriptor. You need a separate broker archive file for each configuration that you want to deploy.
* brute force collision
A programming style that relies on computing power to try all the possibilities with a known hash until the solution is found.
* * bucket *
One or more fields that accumulate the result of an operation.
* * bulk decryption *
See block decryption.
* * bulk encryption *
See block encryption.
* * bus *
Interconnecting messaging engines that manage bus resources
* * bus member *
The application servers within which the messaging engines run to support the bus.
* business activity
A collection of tasks that are linked so that they have an agreed outcome.
* business activity scope
An attribute of an existing core unit of work that provides the compensation ability in the event of an error in a business activity, when that activity cannot be atomically rolled back.
* * business logic tier *
The set of components that reside between the presentation and database tiers. This logic tier hosts the enterprise bean containers, which run the business logic.
* * business process container *
A process engine that contains process modules.
* byte order mark (BOM)
A character code at the beginning of a data stream that can be used as a signature that defines the byte order and encoding form.
* * CA *
See certificate authority.
* * cache instance resource *
A location where any Java 2 Platform, Enterprise Edition (J2EE) application can store, distribute, and share data.
* * cache replication *
The sharing of cache IDs, cache entries, and cache invalidations with other servers in the same replication domain.
* * callback handler *
A mechanism that uses a Java Authentication and Authorization Service (JAAS) interface to pass a security token to the Web service security runtime for propagation in the Web service security header.
* * capability list *
A list of associated resources and their corresponding privileges per user.
* * CBR *
See content based routing.
* * cell *
1. One or more processes that each host runtime components. Each cell has one or more named core groups. 2. An arbitrary grouping of one or more nodes in a WebSphere Application Server distributed network.
* * cell-scoped binding *
A binding scope where the binding is not specific to, and not associated with any node or server. This type of name binding is created under the persistent root context of a cell.
* * certificate authority (CA) *
An organization that issues certificates. The CA authenticates the certificate owner's identity and the services that the owner is authorized to use, issues new certificates, renews existing certificates, and revokes certificates.
* * certificate revocation list (CRL)*
A list of certificates issued by a certificate authority (CA). The certificates on this list might not be expired, but are no longer trusted by the CA.
* * chain *
The name of a channel framework connection that contains an endpoint definition.
* * channel *
An entry point to the Web services gateway that carries requests and responses between Web services and the gateway.
* * channel framework *
A common model for connection management, thread usage, channel management, and message access within WebSphere Application Server.
* * Channel Information Control System (CICS) *
An IBM licensed program that provides online transaction-processing services and management for business applications.
* * cheat sheet *
An interface that guides users through the wizards and steps required to perform a complex task, and that links to relevant sections of the online help.
* CICS
See Channel Information Control System.
* * cipher *
A cryptographic algorithm used to encrypt data that is unreadable until converted into plain data with a predefined key.
* * cipher suite *
A set of ciphers.
* * class *
In object-oriented design or programming, a model or template that can be used to create objects with a common definition and common properties, operations, and behavior. An object is an instance of a class.
* * class file *
A compiled Java source file.
* * class hierarchy *
The relationships between classes that share a single inheritance. In Java programming, all classes inherit from the Object class.
* * class loader *
Part of the Java virtual machine code that is responsible for finding and loading class files. A class loader affects the packaging of applications and the run-time behavior of packaged applications deployed on application servers.
* * class path *
A list of directories and JAR files that contain resource files or Java classes that a program can load dynamically at run time. See also CLASSPATH.
* * client proxy *
An object on the client side of a network connection that provides a remote procedure call interface to a service on the server side.
* * client type detection *
A process in which a servlet determines the markup language type required by a client and calls the appropriate JavaServer Pages file.
* * client/server *
Pertaining to the model of interaction in distributed data processing in which a program on one computer sends a request to a program on another computer and awaits a response. The requesting program is called a client; the answering program is called a server. See also distributed application.
* * Cloudscape *
An embeddable, all Java, object-relational database management system (ORDBMS).
* * cluster *
A group of application servers that collaborates for the purposes of workload balancing and failover.
* * CMP *
See container-managed persistence.
* * coexistence *
The ability of multiple installations of the WebSphere Application Server to run in the same machine at the same time.
* * collection certificate store *
A collection of intermediate certificates or certificate revocation lists (CRL) that are used by a certificate path to build up a certificate chain for validation.
* * Collector Tool *
A tool that gathers information about a WebSphere Application Server installation and packages this data in a Java archive (JAR) file to assist in problem determination and analysis. This information includes logs, property files, configuration files, operating system data, Java data, and prerequisite software presence and levels.
* Common Criteria
The title of a set of documents that describe a particular set of IT security evaluation criteria.
* * Common Object Request Broker Architecture (CORBA) *
An architecture and a specification for distributed object-oriented computing that separates client and server programs with a formal interface definition. See also Internet Inter-ORB Protocol.
* * Common Secure Interoperability Version 2 (CSIv2)*
An authentication protocol developed by the Object Management Group (OMG) that supports interoperability, authentication delegation, and privileges.
* * compilation unit *
A portion of a computer program sufficiently complete to be compiled correctly.
* * complex type *
In Extensible Markup Language (XML), a type that supports elements in its content and may carry attributes. See also simple type.
* * concurrency control *
The management of contention for data resources.
* * configuration repository *
A storage area of configuration data that is typically located in a subdirectory of the product installation root directory.
* configuration root
The mount point for the configuration file system.
* * configured name binding *
Persistent storage of an object in the name space that is created using either the administrative console or the wsadmin program.
* * connection factory *
A set of configuration values that produces connections that enable a J2EE component to access a resource. Connection factories provide on-demand connections from an application to an enterprise information system (EIS).
* * connection handle *
A representation of a physical connection.
* * connection pooling *
A technique used for establishing a pool of resource connections that applications can share on an application server.
* * connector *
In J2EE, a standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs). A connector consists of a resource adapter and application development tools (Sun). See also container.
* constructor
In object-oriented programming, a special method used to initialize an object.
* consumer
1. An application that attaches to a bus destination and receives messages from the service integration bus. 2. In java Message Service (JMS), an object that is used for receiving messages from a destination.
* * container *
In J2EE, an entity that provides life-cycle management, security, deployment, and run-time services to components. (Sun) Each type of container (EJB, Web, JSP, servlet, applet, and application client) also provides component-specific services. See also resource adapter, connector.
* * container transaction *
See container-managed transaction.
* * container-managed persistence (CMP) *
In Java 2 Platform, Enterprise Edition (J2EE) technology, data transfer between the variables of an entity bean and a resource manager administered by the entity bean container. See also bean-managed persistence.
* * container-managed transaction *
A transaction whose boundaries are defined by an EJB container. An entity bean must use container-managed transactions. (Sun)
* * content based routing (CBR) *
An optional feature of the caching proxy that provides intelligent routing to back-end application servers. This routing is based on HTTP session affinity and a weighted round-robin algorithm.
* * context parameter *
A definition of the server view of the Web application within which the servlet is running and supports servlet access to available resources.
* * control region *
A virtual storage area that provides the control, scheduling, and work management mechanisms necessary to coordinate shared resources.
* controller
A regulating mechanism that controls the scheduling and work management coordination for shared resources.
* * CORBA *
See Common Object Request Broker Architecture.
* * core group *
A group of processes that is directly accessible to each other and is connected using a local area network (LAN).
* * core group access point *
A definition of a set of servers that provides access to the core group.
* * core group bridge *
The means by which core groups communicate.
* * core group member *
A server included in the cluster of a core group.
* * create method *
In enterprise beans, a method defined in the home interface and invoked by a client to create an enterprise bean. (Sun)
* * credential *
In the Java Authentication and Authorization Service (JAAS) framework, a subject class that owns security-related attributes. These attributes can contain information used to authenticate the subject to new services.
* CRL
See certificate revocation list.
* * cryptographic token *
A logical view of a hardware device that performs cryptographic functions and stores cryptographic keys, certificates, and user data.
* CSIv2
See Common Secure Interoperability Version 2.
* * custom service *
A configurable service that plugs in to a WebSphere Application Server and defines a hook point that runs when the server starts and shuts down when the server stops.
* * custom user registry *
A customer-implemented user registry that implements the UserRegistry Java interface. This registry type can support virtually any kind of accounts repository from a relational database and can provide flexibility in adapting product security to various environments.
* * daemon *
A program that runs unattended to perform continuous or periodic functions, such as network control.
* * data access bean *
A class library that provides a rich set of features and functions, while hiding the complexity associated with accessing relational databases.
* * data definition language (DDL) *
A language for describing data and its relationships in a database. See also data manipulation language.
* data graph
A collection of tree-structured or graph-structured data objects.
* data replication service (DRS)
A service that transfers data, objects, or events among application servers.
* * data source *
1. In Java Database Connectivity (JDBC), an interface that provides a logical representation of a pool of connections to a physical data source. Data source objects provide application portability by making it unnecessary to supply information specific to a particular database driver. 2. A repository of data to which a federated server can connect and then retrieve data by using wrappers. A data source can contain relational databases, Extensible Markup Language (XML) files, search algorithms, table-structured files, or other objects. In a federated system, data sources display as a single collective database.
* data store
1. A place (such as a database system, file, or directory) where data is stored. 2. In Java Message Service (JMS), an administered object that encapsulates the identity of a message destination. See bus destination.
* * datagram *
A form of asynchronous messaging in which an application sends a message, but does not require a response.
* * DB2 *
A family of IBM licensed programs for relational database management.
* * DDL *
See data definition language.
* * debugger *
A tool used to detect and trace errors in computer programs.
* * declarative security *
The security configuration of an application during assembly stage that is defined in the deployment descriptors and enforced by the security run time.
* * delegation *
The process of propagating a security identity from a caller to a called object. According to the Java 2 Platform, Enterprise Edition (J2EE) specification, a servlet and an enterprise bean can propagate either the client identity when invoking enterprise beans, or can use another specified identity as indicated in the corresponding deployment descriptor.
* demarshal
The conversion of a data stream into an object.
* * demilitarized zone (DMZ) *
A configuration including multiple firewalls to add layers of protection between a corporate intranet and a public network, like the Internet.
* * deploy *
To place files or install software into an operational environment. In J2EE, this involves creating a deployment descriptor suitable to the type of application that is being deployed.
* deployer
A person who installs modules and Java 2 Platform, Enterprise Edition (J2EE) applications into an operational environment.
* * deployment descriptor *
An XML file that describes how to deploy a module or application by specifying configuration and container options. For example, an EJB deployment descriptor passes information to an EJB container about how to manage and control an enterprise bean.
* * deployment manager *
A special type of server that manages operations for a cell.
* * deprecated *
Pertaining to an entity, such as a programming element or feature, that is supported but no longer recommended, and that might become obsolete.
* deserializer
A method for converting a serialized variable into object data.
* destination
In Java Message Service, an administered object that encapsulates the identity of a message destination. See bus destination.
* destination routing path
A sequence of intermediary bus destinations that messages must pass through to reach a target bus destination.
* * digest code *
A number that is the result of a message digest function or a secure hash algorithm distilling a document.
* * digital certificate *
An electronic document used to identify an individual, server, company, or some other entity, and to associate a public key with the entity. A digital certificate is issued by a certification authority and is digitally signed by that authority.
* digital signature
The encrypted digest code that is appended to a document. In an authentication system that uses public-key encryption, digital signatures are used to sign certificates.
* * directive *
A first-failure data capture (FFDC) construct that may be contained in a WebSphere Application Server symptom database in order to provide information and suggested actions to assist a diagnostic module in customizing the data that is logged.
* * discover *
In UDDI, to browse the business registry to locate existing Web services for integration.
* discovery protocol
Pertaining to the protocol that is followed to retrieve information from a network.
* * distinguished name (DN)*
A set of name-value pairs (such as CN=person's name and C=country or region) that uniquely identify an entity in a digital certificate.
* * distributed application *
An application made up of distinct components that are physically located on different computer systems, connected by a network. See also client/server.
* * DMZ *
See demilitarized zone.
* * Document Object Model (DOM) *
A system in which a structured document, for example an Extensible Markup Language (XML) file, is viewed as a tree of objects that can be programmatically accessed and updated.
* document type definition (DTD)
The rules that specify the structure for a particular class of Standard Generalized Markup Language (SGML) or Extensible Markup Language (XML) documents.
* * DOM *
See Document Object Model.
* * domain *
An object, icon, or container that contains other objects representing the resources of a domain. The domain object can be used to manage those resources.
* * drop-down *
Pertaining to a list or menu that opens when clicked and stays open until the user selects a menu or list item or clicks elsewhere in the user interface.
* DRS
See data replication service.
* DTD
See document type definition.
* durable subscription
A subscription that can accumulate messages, even when no consumers are attached.
* * dynamic cache *
A consolidation of several caching activities, including servlets, Web services, and WebSphere commands into one service where these activities work together to improve performance and share configuration parameters.
* * dynamic cluster *
A server cluster that uses weights to balance the workloads of its cluster members dynamically, based on performance information collected from cluster members.
* dynamic operations
Operations that monitor the server environment and make recommendations that are based on data observation.
* * dynamic policy *
A template of permissions for a particular type of resource.
* * dynamic reloading *
The ability to change an existing component without restarting the server for the changes to become effective.
* * EAR *
See enterprise archive.
* ECSA
See extended common system area.
* Edge Side Include (ESI)
A technology supporting cacheable and noncacheable Web page components that can be gathered and assembled at the edge of a network.
* edition
A successive deployment generation of a particular set of versioned artifacts.
* * EIS *
See enterprise information system.
* EJB
See Enterprise JavaBeans.
* EJB container
A container that implements the EJB component contract of the J2EE architecture. This contract specifies a run-time environment for enterprise beans that includes security, concurrency, life-cycle management, transactions, deployment, and other services. An EJB container is provided by an EJB or J2EE server. (Sun)
* EJB context
In enterprise beans, an object that allows an enterprise bean to invoke services provided by the container and to obtain information about the caller of a client-invoked method. (Sun)
* EJB inheritance
A form of inheritance in which an enterprise bean inherits properties, methods, and method-level control descriptor attributes from another enterprise bean that resides in the same group.
* EJB module
A software unit that consists of one or more enterprise beans and an EJB deployment descriptor. (Sun)
* EJB object
In enterprise beans, an object whose class implements the enterprise bean remote interface (Sun).
* EJB query
A string that contains an optional SELECT clause that specifies the Enterprise JavaBeans (EJB) objects to return, a FROM clause that names the bean collections, an optional WHERE clause that contains search predicates over the collections, an optional ORDER BY clause that specifies the ordering of the result collection; and input parameters that correspond to the argument of the finder method.
* EJB reference
A logical name that is used by an application to locate the home interface of an enterprise bean in the target operational environment.
* EJB server
Software that provides services to an EJB container. An EJB server may host one or more EJB containers (Sun).
* * element *
In markup languages such as Standard Generalized Markup Language (SGML), Extensible Markup Language (XML), and Hypertext Markup Language (HTML), a basic unit consisting of a start tag, end tag, associated attributes and their values, and any text that is contained between the two.
* enclave
A construct that represents a business transaction or unit of work on the OS/390 workload manager.
* endian
A data type that is longer than a byte and that is stored in computer memory with the most significant byte first or last.
* * endpoint *
The system that is the origin or destination of a session.
* * endpoint listener *
The point or address at which incoming messages for a Web service are received by a service integration bus.
* endpoint reference
The combination of the address of a Web service that implements the manageability interface for a managed resource type and the properties that allow that Web service to identify the managed resource.
* * enterprise application *
An application that conforms to the Java 2 Platform Enterprise Edition specification.
* * enterprise archive (EAR) *
A specialized type of Java archive (JAR) file, defined by the Java 2 Platform, Enterprise Edition (J2EE) standard, used to deploy J2EE applications to J2EE application servers. An EAR file contains enterprise bean components, a deployment descriptor, and Web archive (WAR) files for individual Web applications. See also Web archive.
* * enterprise bean *
A component that implements a business task or business entity and resides in an EJB container. Entity beans, session beans, and message-driven beans are all enterprise beans. (Sun)
* * enterprise information system (EIS) *
The applications that comprise the existing system of an enterprise for handling company-wide information. Examples of enterprise information systems include: an enterprise resource planning (ERP) system, a mainframe transaction processing system, and a legacy database system. (Sun) See also resource adapter.
* Enterprise JavaBeans (EJB)
A component architecture defined by Sun Microsystems for the development and deployment of object-oriented, distributed, enterprise-level applications.
* enterprise workload manager
Part of the dynamic operations environment that manages subgoals and resources for the larger enterprise environment.
* * entity *
In markup languages such as Extensible Markup Language (XML), a collection of characters that can be referenced as a unit, for example to incorporate often repeated text or special characters within a document.
* * entity bean *
In EJB programming, an enterprise bean that represents persistent data maintained in a database. Each entity bean carries its own identity. (Sun) There are two types of entity beans: container-managed persistence (CMP) entity beans and bean-managed persistence (BMP) entity beans. See also session bean.
* * environment variable *
A variable that specifies how an operating system or another program runs, or the devices that the operating system recognizes.
* * error *
A discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition.
* * error log stream *
A continuous flow of error information that is transmitted using a predefined format.
* * ESI *
See Edge Side Include.
* * ESI processor *
A feature in the WebSphere Web server plug-in that supports fragment caching and fragment assembly into full pages.
* * event *
The encapsulated data that is sent as a result of an occurrence, or situation in the system.
* event factory
An object that returns new instances of either the CommonBaseEvent element or of the specialized classes representing complex property data types.
* * event listener *
A type of asynchronous bean that serves as a notification mechanism and through which Java 2 Platform, Enterprise Edition (J2EE) components within a single application can notify each other about various asynchronous events.
* * event source *
An object that supports an asynchronous notification server within a single Java virtual machine. Using an event source, the event listener object can be registered and used to implement any interface.
* exception
An event during program execution that prevents the program from continuing normally.
* * exception handler *
A block of code that reacts to a specific type of exception.
* express nonpersistent
A delivery option that specifies that messages are discarded when a messaging engine stops or fails. Messages can also be discarded if a connection that is used to send them becomes unavailable. See also best effort nonpersistent, reliable nonpersistent, reliable persistent, and assured persistent.
* expression
An SQL operand or a collection of operators and operands that yields a single value.
* *extended common system area (ECSA) *
A major element of MVS/ESA virtual storage above the 16 MB line. This area contains pageable system data areas that are addressable by all active virtual storage address spaces. It duplicates the common system area (CSA), which exists below the 16 MB line.
* extended manageability
Offers simpler and improved management of complex system operations with real-time advanced, meaningful visualization tools and gradual, controlled implementation of autonomic capabilities, helping reduce the cost of managing IT resources.
* * extended messaging *
A function of asynchronous messaging where the application server manages the messaging infrastructure and extra standard types of messaging beans are provided to add functionality to that provided by message-driven beans.
* Extensible Markup Language (XML)
A standard metalanguage for defining markup languages that is based on Standard Generalized Markup Language (SGML).
* * extension *
A class of objects designated by a specific term or concept; denotation.
* *factory *
In object-oriented programming, a class that is used to create instances of another class. A factory is used to isolate the creation of objects of a particular class into one place so that new functions can be provided without widespread code changes.
* * failover *
A cluster event where the primary database server or application server switches over to a backup system due to the failure of the primary server.
* FAP
See Formats and Protocols.
* * fast response cache accelerator (FRCA) *
A cache that resides in the kernel on AIX and Windows platforms that provides support for caching on multiple Web servers and on servers with multiple IP addresses.
* * fault message *
An object that contains status information and details about a problem with a message.
* Federal Information Processing Standard (FIPS)
A standard produced by the National Institute of Standards and Technology when national and international standards are nonexistent or inadequate to satisfy the U.S. government requirements.
* * federation *
The process of combining naming systems so that the aggregate system can process composite names that span the naming systems.
* FFDC
See first-failure data capture.
* * file serving *
A function that supports the serving of static files by Web applications.
* file store
A type of message store that directly uses files in a file system through the operating system.
* * filter *
A device or program that separates data, signals, or material in accordance with specified criteria.
* finder method
In enterprise beans, a method defined in the home interface and invoked by a client to locate an entity bean. (Sun)
* * fingerprint *
See digest code.
* FIPS
See Federal Information Processing Standard.
* * firewall *
A network configuration, usually both hardware and software, that prevents unauthorized traffic into and out of a secure network.
* first-failure data capture
A problem diagnosis aid that identifies errors, gathers and logs information about these errors, and returns control to the affected run-time software.
* * fix pack *
A cumulative collection of fixes that does not contain new functions. A fix pack can contain fixes that have not been shipped previously. Full regression testing is performed on fix packs. See also program temporary fix, test fix, interim fix, refresh pack.
* * folder *
A container used to organize objects.
* foreign bus
One of the other service integration buses with which a particular service integration bus can exchange messages.
* foreign destination
A destination that identifies a destination on a foreign bus.
* Formats and Protocols (FAP)
In message queuing, a definition of how queue managers communicate with each other, and of how clients communicate with server queue managers.
* * form logout *
A mechanism to log out without having to close all Web browser sessions.
* * form-based login *
An authentication process where a user ID and a password are retrieved using an Hypertext Markup Language (HTML) form, and sent to the server over the Hypertext Transfer Protocol (HTTP) or hypertext Transfer Protocol Secure (HTTPS) protocol.
* forward routing path
A set of bus destinations to which a message is routed and held as a stack property within the message. When a message is created, the forward routing path is added to the message. When the message reaches a destination, that destination is removed from the forward routing path in the message.
* * forwardable credentials *
A mechanism-specific security credential ( that is issued to access a resource, which is used to obtain another credential for access to a different resource.
* * FRCA *
See fast response cache accelerator.
* * garbage collection *
A routine that searches memory to reclaim space from program segments or inactive data.
* * gateway *
A middleware component that bridges Internet and intranet environments during Web service invocations.
* gateway destination
A type of service destination that receives messages for gateway services. Gateway destinations are divided into those that are used for request processing and those that are used for reply processing.
* gateway queue manager
The queue manager to which the connection is made in a WebSphere MQ link.
* gateway service
A Web service that is made available through the Web services gateway.
* General Inter-ORB Protocol (GIOP)
A protocol that Common Object Request Broker Architecture (CORBA) uses to define the format of messages.
* * generic server *
A server that is managed in, but not supplied by WebSphere Application Server. Any server or process that is necessary to support the Application Server environment, including a Java server, a C or C++ server or process, a CORBA server, or a Remote Method Invocation (RMI) server.
* * generic server cluster *
A group of remote servers that need routing by the proxy server.
* * getter method *
A method whose purpose is to get the value of an instance or class variable. This allows another object to find out the value of one of its variables. See also setter method.
* * GIOP *
See General Inter-ORB Protocol.
* * global security *
Pertains to all applications running in the environment and determines whether security is used, the type of registry used for authentication, and other values, many of which act as defaults.
* * grammar *
A document type definition (DTD) or schema providing a structured format used for successful processing by the trace service.
* grid job
A set of managed background activities.
* * group *
A collection of users who can share access authorities for protected resources.
* HA
See high availability.
* * HA group *
A collection of one or more members. A common group name relates the members together
* * HA policy *
A set of rules that is defined for a high availability (HA) group that dictate whether zero (0), or more members are activated. The policy is associated with a specific HA group by matching the policy match criteria with the group name.
* * handle *
In the J2EE specification, an object that identifies an enterprise bean. A client may serialize the handle, and then later deserialize it to obtain a reference to the enterprise bean. (Sun)
* * handler *
In Web services, a mechanism for processing service content and extending the function of a Java API for XML-based RPC (JAX-RPC) run-time system.
* * handshake *
The exchange of messages at the start of a Secure Sockets Layer session that allows the client to authenticate the server using public key techniques (and, optionally, for the server to authenticate the client), then allows the client and server to cooperate in creating symmetric keys for encryption, decryption, and detection of tampering.
* * hash *
In computer security, a number generated from a string of text that is used to ensure that transmitted messages arrived intact.
* hash map
A data structure that associates keys with values.
* * hierarchical *
Pertaining to data that is organized on computer systems using a hierarchy of containers, often called folders (directories) and files. In this scheme, folders can contain other folders and files. The successive containment of folders within folders creates the levels of organization, which is the hierarchy.
* * high availability *
Pertaining to a clustered system that is reconfigured when node or daemon failures occur, so that workloads can be redistributed to the remaining nodes in the cluster.
* * high availability file system *
A cluster file system that can be used for component redundancy to provide continued operations during failures.
* * high availability manager *
A framework within which core group membership is determined and status is communicated between core group members.
* high performance computing
The ability to support quality of service initiatives for business-critical applications to provide near-linear scalability of high-end transaction processing.
* * HMAC *
See Keyed-Hashing Message Authentication Code.
* * home interface *
In enterprise beans, an interface that defines zero or more create and remove methods for a session bean or zero or more create, finder, and remove methods for an entity bean. See also remote interface.
* * home method *
A method in the home interface that is used by a client to create, locate, and remove instances of enterprise beans.
* * horizontal scaling *
A topology in which more than one application server running on multiple computing nodes is used to run a single application.
* * host *
1. A computer that is connected to a network and provides an access point to that network. The host can be a client, a server, or both a client and server simultaneously. 2. In performance profiling, a machine or a machine starting partition on which an application under test resides. The host owns the processes that are profiled.
* * host name *
The network name for a network adaptor on a physical machine in which the node is installed.
* * hot deployment *
The process of adding new components to a running server without stopping and restarting the application server or application.
* * hot servant region *
A servant region that had a request dispatched to it previously and now has available threads.
* * hover help *
A form of online help that can be viewed by moving a mouse or other pointing device over a GUI item such as an icon or field.
* * HTTP *
See Hypertext Transfer Protocol.
* * HTTP channel *
A type of channel within a transport chain that provides client applications with persistent HTTP connections to remote hosts that are either blocked by firewalls or require an HTTP proxy server. An HTTP channel is used to exchange application data in the body of an HTTP request and an HTTP response that are sent to and received from a remote server.
* * HTTPS *
See Hypertext Transfer Protocol Secure.
* * Hypertext Transfer Protocol (HTTP) *
In the Internet suite of protocols, the protocol that is used to transfer and display hypertext and Extensible Markup Language (XML) documents on the Web.
* * Hypertext Transfer Protocol Secure (HTTPS) *
An Internet protocol that is used by Web servers and Web browsers to transfer and display hypermedia documents securely across the Internet.
* * IDE *
See integrated development environment.
* * identifier *
The name of an item in a program written in the Java language.
* * identity *
The data that represents a person and that is stored in one or more repositories.
* * identity assertion *
The invocation credential that is asserted to the downstream server. This credential can be set as the originating client identity, the server identity, or another specified identity, depending on the RunAs mode for the enterprise bean.
* * identity token *
A token that contains the invocation credential identity, which with the client authentication token are required by the receiving server to accept the asserted identity.
* * IDL *
See Interface Definition Language.
* IETF
See Internet Engineering Task Force.
* * IIOP *
See Internet Inter-ORB Protocol.
* * inbound authentication *
The configuration that determines the type of accepted authentication for inbound requests.
* * inbound port *
A type of port that takes a message that is received at an endpoint listener and passes it to the service integration bus for forwarding to the appropriate inbound service.
* * inbound service *
The external interface for a service that is provided by your own organization and hosted in a location that is directly available through the service destination.
* * inbound transport *
Network ports in which a server listens for incoming requests.
* indirect link
A link from a service integration bus to a foreign bus that is made through one or more intermediate foreign buses. The intermediate foreign buses can be service integration buses or WebSphere MQ systems.
* information center
A collection of information that provides support for users of one or more products, can be launched separately from the product, and includes a list of topics for navigation and a search engine.
* * inheritance *
An object-oriented programming technique that allows the use of existing classes as a basis for creating other classes.
* * initial context *
Starting point in a namespace.
* * initial reference *
A well-known reference that is associated with an identifier.
* * INS *
See Interoperable Naming Service.
* instance
In object-oriented programming, an object of a particular class.
* * integrated development environment (IDE) *
A set of software development tools such as source editors, compilers, and debuggers, that are accessible from a single user interface. In Eclipse, the IDE is called the workbench.
* Interactive System Productivity Facility (ISPF)
An IBM licensed program that serves as a full-screen editor and dialog manager. Used for writing application programs, it provides a means of generating standard screen panels and interactive dialogs between the application programmer and terminal user.
* Interface Definition Language (IDL)
In Common Object Request Broker Architecture (CORBA), a declarative language that is used to describe object interfaces, without regard to object implementation.
* internationalized
An application that is coded such that it can present information to users in different locales or languages, and accept input data from users in multiple locales.
* Internet Engineering Task Force (IETF)
The task force of the Internet Architecture Board (IAB) that is responsible for solving the short-term engineering needs of the Internet. The IETF consists of numerous working groups, each focused on a particular problem. Internet standards are typically developed or reviewed by individual working groups before they can become standards.
* Internet Inter-ORB Protocol (IIOP)
A protocol used for communication between Common Object Request Broker Architecture (CORBA) Object Request Brokers.
* * interoperability *
The capability to communicate, run programs, or transfer data among various functional units in a way that requires the user to have little or no knowledge of the unique characteristics of those units.
* * Interoperable Naming Service (INS) *
A program that supports the configuration of the Object Request Broker (ORB) administratively to return object references.
* * interoperable object reference (IOR) *
An object reference with which an application can make a remote method call on a CORBA object. This reference contains all the information needed to route a message directly to the appropriate server.
* * invocation *
The activation of a program or procedure.
* * invocation credential *
An identity with which to invoke a downstream method. The receiving server requires this identity with the sending server identity to accept the asserted identity.
* * invoker attribute *
An assembly property for a Web module that is used by the servlet that implements the invocation behavior.
* * IOR *
See interoperable object reference.
* IP sprayer
A device that is located between inbound requests from the users and the application server nodes that reroutes requests across nodes.
* * ISPF *
See Interactive System Productivity Facility.
* * J2EE *
See Java 2 Platform, Enterprise Edition.
* * J2EE application *
Any deployable unit of J2EE functionality. This unit can be a single module or a group of modules packaged into an enterprise archive (EAR) file with a J2EE application deployment descriptor. (Sun)
* * J2EE Connector architecture (JCA) *
A standard architecture for connecting the Java 2 Platform, Enterprise Edition (J2EE) platform to heterogeneous enterprise information systems (EIS).
* * J2EE server *
A run-time environment that provides EJB or Web containers.
* * JAAS *
See Java Authentication and Authorization Service.
* * Jacl *
See Java Command Language.
* * JAF *
See JavaBeans Activation Framework.
* * Java *
An object-oriented programming language for portable interpretive code that supports interaction among remote objects. Java was developed and specified by Sun Microsystems, Incorporated.
* * Java 2 Connector security *
An architecture designed to extend the end-to-end security model for J2EE-based applications to include enterprise information systems (EIS)
* * Java 2 Platform, Enterprise Edition (J2EE) *
An environment for developing and deploying enterprise applications, defined by Sun Microsystems Inc. The J2EE platform consists of a set of services, application programming interfaces (APIs), and protocols that provide the functionality for developing multitiered, Web-based applications. (Sun) See also Java 2 Platform Standard Edition.
* * Java API for XML (JAX) *
A set of Java-based APIs for handling various operations involving data defined through Extensible Markup Language (XML).
* * Java API for XML-based RPC (JAX-RPC) *
A specification that describes application programming interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and Extensible Markup Language (XML). JAX-RPC is also known as JSR 101.
* * Java Authentication and Authorization Service (JAAS) *
In Java 2 Platform, Enterprise Edition (J2EE) technology, a standard API for performing security-based operations. Through JAAS, services can authenticate and authorize users while enabling the applications to remain independent from underlying technologies.
* * Java Command Language (Jacl) *
A scripting language for the Java 2 environment that is used to create Web content and to control Java applications.
* * Java Database Connectivity (JDBC) *
An industry standard for database-independent connectivity between the Java platform and a wide range of databases. The JDBC interface provides a call-level API for SQL-based database access.
* Java Generic Security Services (JGSS)
A specification that provides Java programs access to the services that include the signing and sealing of messages and a generic authentication mechanism.
* * Java Management Extensions (JMX) *
A means of doing management of and through Java technology. JMX was developed through the Java Community ProcessSM program, by Sun Microsystems, Inc. and some leading companies in the management field. JMX is a universal, open extension of the Java programming language for management that can be deployed across all industries, wherever management is needed.
* * Java Message Service (JMS) *
An application programming interface (API) that provides Java language functions for handling messages. See also Application Messaging Interface, Message Queue Interface.
* * Java Naming and Directory Interface (JNDI) *
An extension to the Java platform that provides a standard interface for heterogeneous naming and directory services.
* * Java platform *
A collective term for the Java language for writing programs; a set of APIs, class libraries, and other programs used in developing, compiling, and error-checking programs; and a Java virtual machine which loads and executes the class files. (Sun)
* * Java Runtime Environment (JRE) *
A subset of the Sun Microsystems Java Development Kit (JDK) that contains the core executable programs and files that constitute the standard Java platform. The JRE includes the Java virtual machine (JVM), core classes, and supporting files.
* * Java Secure Socket Extension (JSSE) *
A Java package that enables secure Internet communications. It implements a Java version of the Secure Sockets Layer (SSL) and Transport Layer Security (TSL) protocols and supports data encryption, server authentication, message integrity, and optionally client authentication.
* * Java virtual machine (JVM) *
A software implementation of a central processing unit that runs compiled Java code (applets and applications).
* * Java Virtual Machine Profiler Interface (JVMPI) *
A profiling tool that supports the collection of information, such as data about garbage collection and the Java virtual machine (JVM) application programming interface (API) that runs the application server.
* Java Widget Library (JWL)
An extended widget set that is usable by portal and portlet programmers that adds JavaScript client-side processing to JavaServer Faces.
* * JavaBeans *
As defined for Java by Sun Microsystems, a portable, platform-independent, reusable component model. See also bean.
* * JavaBeans Activation Framework (JAF) *
A standard extension to the Java platform that determines arbitrary data types and available operations and can instantiate a bean to run pertinent services.
* * JavaMail API *
A platform and protocol-independent framework for building Java-based mail client applications.
* JavaServer Faces (JCF)
A Java framework that is used for developing Web applications.
* * JavaServer Pages (JSP) *
A server-side scripting technology that enables Java code to be dynamically embedded within Web pages (HTML files) and executed when the page is served, in order to return dynamic content to a client. See also JSP file, JSP page.
* JavaServer Pages (JSP) file
Application building blocks coded to the Sun Microsystems JavaServer Pages (JSP) specification. JSP files enable the separation of the Hypertext Markup Language (HTML) code from the business logic in Web pages so that HTML programmers and Java programmers can collaborate when creating and maintaining pages.
* * JAX *
See Java API for XML.
* * JAX-RPC *
See Java API for XML-based RPC.
* * JAX-RPC handler *
A Java class that performs a range of handling tasks, including logging messages, transforming message content, or terminating an incoming request.
* * JCA *
See J2EE Connector architecture.
* JCF
See JavaServer Faces.
* * JDBC *
See Java Database Connectivity.
* JGSS
See Java Generic Security Services.
* * JMS *
See Java Message Service.
* JMS provider
The software that implements the Java Message Service (JMS) specification for a messaging product.
* JMS Topic
In Java Message Service (JMS), a JMS-managed object that manages the message flow from publishers to subscribers.
* * JMX *
See Java Management Extensions.
* * JNDI *
See Java Naming and Directory Interface.
* * JRas *
A toolkit that consists of a set of Java packages that enable developers to incorporate message logging and trace facilities into Java applications.
* job class
A type of class that establishes a policy for resource consumption by a set of compute grid jobs. Each job is assigned to a job class.
* job log
A record of requests submitted to the system by a job, the messages related to the requests, and the actions performed by the system on the job. The job log is maintained by the system program.
* job management console
A stand-alone Web interface that can be used to perform job operations. Through the console, jobs can be submitted, monitored, viewed, and managed.
* job scheduler
A Compute Grid component that provides all job management functions. It maintains a history of all jobs, and maintains usage data for jobs that have run. The job scheduler is hosted in a WebSphere Application Server (or cluster) in a WebSphere Network Deployment environment.
* * JRE *
See Java Runtime Environment.
* * JSP *
See JavaServer Pages.
* * JSP file *
A scripted HTML file that has a .jsp extension and allows for the inclusion of dynamic content in Web pages. A JSP file can be directly requested as a URL, called by a servlet, or called from within an HTML page. See also JavaServer Pages, JSP page.
* * JSP page *
A text-based document using fixed template data and JSP elements that describes how to process a request to create a response. (Sun) See also JavaServer Pages, JSP file.
* * JSSE *
See Java Secure Socket Extension.
* * junction *
A logical connection created to establish a path from one server to another.
* * JVM *
See Java virtual machine.
* JVMPI
See Java Virtual Machine Profiler Interface.
* JWL
See Java Widget Library.
* kernel
The part of an operating system that performs basic functions such as allocating hardware resources.
* key
A cryptographic mathematical value that is used to digitally sign, verify, encrypt, or decrypt a message.
* key database file
A synonym for a key ring.
* key file
A synonym for key ring. The file that stores the keys used during the authentication of a message.
* key locator
A mechanism that retrieves the key for Extensible Markup Language (XML) signing, XML digital signature verification, XML encryption, and XML decryption.
* * key ring *
In computer security, a file that contains public keys, private keys, trusted roots, and certificates.
* Keyed-Hashing Message Authentication Code (HMAC)
A mechanism for message authentication that uses cryptographic hash functions.
* * keystore file *
A key database file that contains both public keys stored as signer certificates and private keys stored in personal certificates.
* * keystring *
Additional specification of the entry within a naming service.
* * launchpad *
A graphical interface for launching the product installation.
* * lazy authentication *
The process whereby the security run time obtains the required authentication data when the Java client accesses a protected enterprise bean for the first time.
* * LDAP *
See Lightweight Directory Access Protocol.
* Lightweight Directory Access Protocol (LDAP)
An open protocol that uses TCP/IP to provide access to information directories that support an X.500 model and that does not incur the resource requirements of the more complex X.500 Directory Access Protocol (DAP). For example, LDAP can be used to locate people, organizations, and other resources in an Internet or intranet directory.
* * Lightweight Third Party Authentication (LTPA) *
A protocol that uses cryptography to support security in a distributed environment.
* * link name *
A name defined in the deployment descriptor of the encompassing application.
* * link pack area (LPA) *
A major element of MVS/ESA virtual storage below the 16MB line. The storage areas that make up the LPA contain all the common reentrant modules shared by the system. The LPA provides economy of real storage by sharing one copy of the modules, protection because LPA code cannot be overwritten even by key 0 programs, and reduced pathlength because the modules can be branched to. See the CICS Transaction Server Performance Guide for more information.
* * listener *
A program that detects incoming requests and starts the associated channel.
* * listener port *
An object that defines the association between a connection factory, a destination, and a deployed message-driven bean. Listener ports simplify the administration of the associations between these resources.
* * load balancing *
The monitoring of application servers and management of the workload on servers. If one server exceeds its workload, requests are forwarded to another server with more capacity.
* * local *
Pertaining to a device, file, or system that is accessed directly from a user's system, without the use of a communication line. See also remote.
* * local transaction containment (LTC) *
A bounded scope that is managed by the container to define the application server behavior in an unspecified transaction context.
* * location service daemon *
A component of the Remote Method Invocation and Internet Inter-ORB Protocol (RMI/IIOP) communication function that works with workload management to distribute RMI requests among application servers in a cell.
* * log handler *
A class that uses loggers, levels, and filters to direct whether events are processed or suppressed.
* * logger *
A named and stateful object with which the user code interacts and that logs messages for a specific system or application component.
* * logging *
The recording of data about specific events on the system, such as errors.
* * logging level *
A value that controls which events are processed by Java logging.
* * login binding *
A definition of the implementation to provide login information per authentication methods.
* * login mapping *
A Java Authentication and Authorization Service (JAAS) login configuration that is used to authenticate a security token in a Web service security header.
* * long name *
The property that specifies the logical name for the server on the z/OS platform in WebSphere Application Server.
* LPA
See link pack area.
* LTC
See local transaction containment.
* LTPA
See Lightweight Third Party Authentication.
* * mail session *
A resource collection of protocol providers that authenticate users and control user access to messaging systems.
* Managed Bean (MBean)
In the Java Management Extensions (JMX) specification, the Java objects that implement resources and their instrumentation. MBeans must follow the design patterns and interfaces defined in the instrumentation level of the JMX specification. This ensures that all MBeans provide the instrumentation of managed resources in a standardized way. MBeans are manageable by any JMX agent, but they can also be managed by non-compliant agents that support the MBean concept.
* * managed node *
A node with an application server and a node agent that belongs to a cell.
* * managed resource *
An entity that exists in the run-time environment of an IT system and that can be managed.
* marooned message
A message that cannot be delivered due to the unavailability of a component that is necessary to its processing.
* marshal
To convert an object into a data stream for transmission over a network.
* MBean
See Managed Bean.
* MBean provider
A library containing an implementation of a Java Management Extensions (JMX) MBean and its MBean Extensible Markup Language (XML) descriptor file.
* * MD5 *
A type of message algorithm that converts a message of arbitrary length into a 128-bit message digest. This algorithm is used for digital signature applications where a large message must be compressed in a secure manner.
* mediation
1. The handling of inflight messages between the production of a message by one application, and the consumption of a message by another application. Mediation processing includes:
o Message transformation from one representation to another.
o Message routing to one or more targets that were not specified by the sending application.
o Message augmentation by adding data from a data source. 2. Administered object that defines the information that is needed by a messaging engine to mediate associated destinations.
* mediation handler
A unit of mediation function that performs specific message processing at run time. You can deploy a mediation handler as a simple Java bean or as a stateless session enterprise bean.
* mediation point
A location in a messaging engine at which messages are mediated.
* memory leak
The effect of a program that maintains references to objects that are no longer required and therefore need to be reclaimed.
* memory-to-memory replication
The session replication of one instance of WebSphere Application Server to another.
* message consumer
See consumer.
* * message digest *
A hash value or a string of bits resulting from the conversion of processing data to a number.
* message point
A location in a messaging engine at which messages are held before being processed. See queue point, publication point, and mediation point.
* message producer
See producer.
* message reliability
See reliability attribute.
* message selector
See selector.
* * message-driven bean *
An enterprise bean that provides asynchronous message support and clearly separates message and business processing.
* messaging bus
The role of a service integration bus when providing the messaging system for Java Message Service (JMS) applications using the default messaging provider.
* messaging engine
A component of a service integration bus that provides messaging function and a connection point to which applications connect to the bus. A messaging engine runs within a server and uses an instance of a Java Database Connectivity (JDBC) data source to interact with the database that contains the data store for that messaging engine.
* * metadata *
Data that describes the characteristics of stored data; descriptive data. For example, the metadata for a database table might include the name of the table, the name of the database that contains the table, the names of the columns in the table, and the column descriptions, either in technical terms or business terms. Database catalogs and information catalogs contain metadata.
* * method *
In object-oriented design or programming, the software that implements the behavior specified by an operation.
* * method extension *
An IBM extension to the standard deployment descriptors for enterprise beans that define transaction isolation methods and control the delegation of credentials.
* method permission
A mapping between one or more security roles and one or more methods that a member of a role can call.
* MIME
See Multipurpose Internet Mail Extensions.
* module
In J2EE, a software unit that consists of one or more components of the same container type and one deployment descriptor of that type. Examples include EJB, Web, and application client modules. Modules can be deployed as stand-alone units or assembled into an application. (Sun).
* * monitor *
In performance profiling, to collect data about an application from the running agents that are associated with that application.
* mount point
A logical drive through which volumes are accessed in a sequential access device class. For removable media device types, such as cartridges, a mount point is a logical drive associated with a physical drive. For the file device type, a mount point is a logical drive associated with an I/O stream.
* * MPMT *
See multiprocess multithread.
* multicast
Transmission of the same data to a selected group of destinations.
* * multiple configuration instance *
More than one instance of a product running in the same machine at the same time.
* * multiprocess multithread (MPMT) *
A process architecture of the IBM HTTP Server that supports multiple processes as well as multiple threads per process.
* Multipurpose Internet Mail Extensions (MIME)
An Internet standard that allows different forms of data including video, audio, or binary data to be attached to e-mail without requiring translation into ASCII text.
* * namespace *
A space that is reserved by a file system to contain the names of its objects.
* * naming *
An operation that is used by clients of WebSphere Application Server applications to obtain references to objects related to those applications.
* * naming context *
A logical namespace that contains name and object bindings.
* * naming federation *
The process of binding naming systems so that the aggregate system can process composite names that span the naming systems.
* * naming service *
An implementation of the Java Naming and Directory Interface (JNDI) standard.
* * NAT *
See network address translation.
* * native *
Pertaining to the relationship between a transport user and a transport provider that are both based on the same transport protocol.
* native execution endpoint
A server platform on which native execution jobs can run as part of a grid job.
* native execution job
A program that can be run as a background command on UNIX-type or Windows systems. Native execution jobs are unconstrained by programming and component models. Native applications can be implemented in Java, native-compiled languages, such as C++ and COBOL, and scripts.
* native start endpoint
A server platform on which native start jobs can run as part of a grid job. See also native start job and grid job.
* native start job
A program that can run as a background command on UNIX or Windows systems. Native start jobs can run across multiple programming and component models. Native applications can be implemented in Java, native-compiled languages, such as C++ and COBOL, and scripts.
* * network address translation (NAT) *
The conversion of a network address that is assigned to a logical unit in one network into an address in an adjacent network. See also static network address translation.
* network file system (NFS)
A base element of z/OS that allows remote access to z/OS host-processor data from workstations, personal computers, or any other system on a Transmission Control Protocol/Internet Protocol (TCP/IP) network that is using client software for the Network File System (NFS) protocol.
* * network protocol stack *
A set of network protocol layers and software that work together to process the protocols.
* NFS
See network file system.
* * node *
A logical grouping of managed servers.
* * node agent *
An administrative agent that manages all application servers on a node and represents the node in the managed cell.
* * node federation *
The process of combining the managed resources of one node into a distributed network such that the central manager application can access and administer the resources on the node.
* * node group *
Grouping of nodes based on a common characteristic or property to create a pool of common resources.
* * node name *
The machine name or host name; an arbitrary WebSphere Application Server-specific name that must be unique.
* * nonce *
A unique cryptographic number that is embedded in a message to help detect a replay attack.
* nondurable subscription
A subscription that only exists for the lifetime of a consumer connection to a service integration bus.
* * nonrepudiation *
In business-to-business communication the ability of the recipient to prove who sent a message based on the contents of the message. This can derive from the use of a digital signature on the message, which links the sender to the message.
* * notification *
A message that contains the event descriptions that are sent to managed resources, autonomic managers, and other resources.
* * object *
In object-oriented design or programming, a concrete realization (instance) of a class that consists of data and the operations associated with that data. An object contains the instance data that is defined by the class, but the class owns the operations that are associated with the data. In object-oriented design or programming, an instance of a class that consists of data and the operations associated with that data.
* * object adapter *
A Common Object Request Broker Architecture (CORBA) term that denotes the primary interface that a server implementation uses to access Object Request Broker (ORB) functions.
* * Object Request Broker (ORB) *
In object-oriented programming, software that serves as an intermediary by transparently enabling objects to exchange requests and responses.
* ODC
See on demand configuration
* ODR
See on demand router
* * one-way hash *
An algorithm that converts processing data into a string of bits; known as a hash value or a message digest.
* * Open Servlet Engine (OSE) *
A lightweight communications protocol that was developed by IBM for interprocess communication.
* * ORB *
See Object Request Broker.
* * OSE *
See Open Servlet Engine.
* * outbound authentication *
The configuration that determines the type of accepted authentication for outbound requests.
* * outbound port *
The mechanism through which an outbound service communicates with the externally-hosted Web service. Messages pass between the outbound service and the external service through the appropriate port.
* * outbound service *
The service that provides access through one or more outbound ports to a Web service that is hosted externally.
* PAA
See portal application archive.
* * package *
1. In Java programming, a group of types. Packages are declared with the package keyword. (Sun) 2. In Java 2 Platform, Enterprise Edition (J2EE) technology, to assemble components into modules and modules into enterprise applications.
* * page list *
An assembly property that specifies the location to forward a request, but automatically tailors that location, depending on the Multipurpose Internet Mail Extensions (MIME) type of the servlet.
* * parallel garbage collection *
A type of garbage collection that uses several threads simultaneously.
* * part reference *
An object that is used by a configuration to reference other related configuration objects.
* partitioned destination
A bus destination that is assigned to a cluster bus member. Each messaging engine in the server cluster has a separate queue point for the destination. Messages that are sent to a partitioned destination are routed to one of the queue points based on workload management (WLM) algorithms.
* passivation
In enterprise beans, the process of transferring an enterprise bean from memory to secondary storage. (Sun)
* PassTicket
In Resource Access Control Facility (RACF) secured signon, a dynamically generated, random, one-time-use, password substitute that a workstation or other client can use to sign on to the host rather than sending a RACF password across the network.
* * payload *
The body of the message that holds the content.
* * peer access point *
A means by which core groups can communicate with other cells.
* Performance Monitoring Infrastructure (PMI)
A set of packages and libraries that are assigned to gather, deliver, process, and display performance data.
* permanent destination
A bus destination for which a runtime instance is created automatically when the messaging engine starts. Permanent destinations remain until they are explicitly deleted by an administrative action. See temporary destination.
* * permission *
Authorization to perform activities, such as reading and writing local files, creating network connections, and loading native code.
* * persist *
To be maintained across session boundaries, usually in nonvolatile storage such as a database system or a directory.
* * persistence *
1. A characteristic of data that is maintained across session boundaries. An object that continues to exist after the start of the program or process that created it, usually in nonvolatile storage such as a database system. 2. In J2EE, the protocol for transferring the state of an entity bean between its instance variables and an underlying database. (Sun)
* perspective
A group of views that show various aspects of the resources in the workbench. The workbench user can switch perspectives, depending on the task, and customize the layout of views and editors within the perspective.
* plain old Java object (POJO)
Another name for a simple or regular java object and not an enterprise bean.
* * plug-in *
A software module that is often written by a third party, that adds function to an existing program or application such as a Web browser.
* * PME *
See programming model extension.
* * PMI *
See Performance Monitoring Infrastructure.
* * point-to-point *
A style of messaging application in which the sending application knows the destination of the message.
* poisoned message
A message that is badly formatted and which, when it arrives on a queue, causes the receiving application to back out the receipt of the message.
* POJO
See plain old Java object.
* * policy *
A set of considerations that influence the behavior of a managed resource or a user.
* * port *
As defined in a WSDL document, a single endpoint defined as a combination of a binding and a network address.
* * port destination *
The specialization of a bus destination that is used to pass messages to an external Web service. You can configure one or more port destinations for each type of message protocol and transport mechanism (for example, SOAP over Hypertext Transfer Protocol (HTTP) or Simple Object Access Protocol (SOAP) over Java Message Service (JMS)) through which service requests and responses can pass to the external service.
* * port number *
In the Internet suite of protocols, the identifier for a logical connector between an application entity and the transport service.
* portal
A single, secure point of access to diverse information, applications, and people that you can customize and personalize.
* portal application archive (PAA)
A portlet application that is packaged as a Web or enterprise archive with two additional Extensible Markup Language (XML) descriptors that define access control, page layout, and navigation as well as any other resources in the package (for example, themes, wires, or Java 2 Platform, Enterprise Edition (J2EE) artifacts).
* portlet
A reusable Web module that runs on a portal server. Portlets have predefined roles, such as retrieving news headlines, searching a database, or displaying a calendar.
* * presumed trust *
A type of identity assertion where trust is presumed and additional trust validation is not performed. Use this mode only in an environment where trust is established with some other mechanism.
* * primary key *
1. An object that uniquely identifies an entity bean within a home. (Sun) 2. In Java programming, a category of data type that describes a variable that contains a single value of the appropriate size and format for its type: a number, a character, or a Boolean value. Examples of primitive types include byte, short, int, long, float, double, char, boolean.
* primitive key
In Java programming, a type of data that describes a variable containing a single value of the appropriate size and format for its type: a number, a character, or a Boolean value. Examples of primitive types include byte, short, int, long, float, double, char, boolean.
* * principal *
An entity that can communicate securely with another entity. In Kerberos, principals are represented as entries in the Kerberos registry database and include users, servers, computers, and others.
* * private key *
In secure communication, an algorithmic pattern used to encrypt messages that only the corresponding public key can decrypt. The private key is also used to decrypt messages that were encrypted by the corresponding public key. The private key is kept on the user's system and is protected by a password. See also key, public key.
* * process definition *
A specification of the runtime characteristics for an application server process.
* * process module *
A program unit that contains a set of process templates that support administrative tasks.
* producer
1. An application that attaches to a destination and produces messages that are put onto the service integration bus. 2. In Java Message Service (JMS), an object that is used for sending messages to a destination.
* * profile *
Data that describes the characteristics of a user, group, program, device, or remote location.
* profile root
The home directory for a particular instantiated profile.
* programmatic login
A type of form login that supports application presentation site-specific login forms for the purpose of authentication.
* * programmatic security *
A collection of methods that are used by applications when declarative security is not sufficient to express the security model of the application.
* * programming model extension (PME) *
The programming model capabilities that ship with WebSphere Application Server Enterprise Edition. These capabilities are also known as enterprise services.
* * property *
A characteristic or attribute that describes a unit of information.
* * proxy cluster *
A group of proxy servers that distributes HTTP requests across the cluster.
* * proxy peer access point *
A means of identifying the communication settings for a peer access point that cannot be accessed directly.
* * proxy server *
A server that acts as an intermediary for HTTP Web requests that are hosted by an application or a Web server. A proxy server acts as a surrogate for the content servers in the enterprise.
* public
In the Java programming language, pertains to a method or variable that can be accessed by elements residing in other classes. (Sun)
* public key
In secure communication, an algorithmic pattern that is used to decrypt messages that were encrypted by the corresponding private key. You can use a public key to encrypt messages that are decrypted by the corresponding private key only. Users broadcast their public keys to everyone with whom they must exchange encrypted messages.
* public-key algorithm
An algorithm that is designed so that the key used for encryption is different from the key that is used for decryption. The decryption key cannot be derived, at least not in any reasonable amount of time, from the encryption key.
* publication point
A message point that is associated with a topic space destination. When you define a topic space, a publication point is created in each messaging engine within the bus. Messages are held at the publication point until they are consumed by all of the local subscribers.
* * publish *
1. To make a Web site public, for example by putting files in a path known to the HTTP server. 2. In Universal Description, Discovery, and Integration (UDDI), to advertise a Web service so that other businesses can find it and bind with it. Service providers publish the availability of their services through a registry.
* publish/subscribe
A style of messaging application in which the providers of information or publishers, are decoupled from the consumers of that information, subscribers, using a broker.
* publish/subscribe bridge
The component of a WebSphere MQ link that enables publish/subscribe messaging between the service integration bus and WebSphere MQ.
* QoS
See quality of service.
* quality of service (QoS)
A set of communication characteristics that is required by an application. QoS defines a specific transmission priority, level of route reliability, and security level.
* * queue *
A WebSphere MQ object to which message queuing applications can put messages, and from which they can get messages. Local queues can contain a list of messages that are waiting to be processed. Queues of other types cannot contain messages: they point to other queues, or can be used as models for dynamic queues.
* queue destination
A bus destination that is used for point-to-point messaging.
* queue point
A messaging point at which messages are held in a queue until they are consumed. When you define a queue destination and assign it to a bus member, a queue point is created for each messaging engine in the assigned bus member.
* * queuing network *
A group of interconnected components.
* * RACF *
See Resource Access Control Facility.
* rapid deployment tools
Tools to rapidly develop and deploy Java 2 Platform, Enterprise Edition (J2EE) artifacts on the server and package the J2EE artifacts into the deployed enterprise archive (EAR) file.
* * RAR *
See resource adapter archive.
* RDBMS
See relational database management system.
* * realm *
A collection of resource managers that honor a common set of user credentials and authorizations.
* * realm name *
The machine name of a user registry.
* * reentrance *
A situation where a thread of control attempts to enter a bean instance again.
* * reference *
A logical name that is defined in the application deployment descriptor and used to locate external resources for enterprise applications. At deployment, the references are bound to the physical location of the resource in the target operational environment.
* * referential integrity *
In Extensible Markup Language (XML) tools, the condition that exists when all of the references to items in the XML schema editor or DTD editor are automatically cleaned up when the schema is detected or renamed.
* referral
In the Lightweight Directory Access Protocol (LDAP), a pointer from one LDAP directory server to another.
* refresh pack
A fix pack, which is a cumulative collection of fixes, that also contains new functions. Full regression testing is performed on refresh packs.
* * region *
A contiguous area of virtual storage that have common characteristics and that can be shared between processes.
* * registry *
A repository that contains access and configuration information for users, systems, and software.
* relational database management system (RDBMS)
A collection of hardware and software that organizes and provides access to a relational database.
* reliability attribute
A quality of service attribute for messages that specifies the reliability of message delivery options.
* reliable nonpersistent
A delivery option that specifies that messages are discarded when a messaging engine stops or fails.
* reliable persistent
A delivery option that specifies that messages can be discarded when a messaging engine fails.
* remote
Pertaining to a system, program, or device that is accessed through a communications line.
* * remote home interface *
In enterprise beans, an interface that specifies the methods that are used by remote clients for locating, creating, and removing instances of enterprise bean classes. See also local home interface.
* remote interface
In enterprise beans, an interface that defines the business methods that can be called by a client.
* remote mediation point
The representation of a remote proxy for a mediation point that exists at a remote messaging engine. The remote mediation poinht manages an outbound message stream to the mediation point at the remote messaging engine.
* remote message point
A message point that a messaging engine creates dynamically for the purpose of sending and receiving messages to and from a message point on another messaging engine in the service.
* remote method
A business method in the remote interface that is callable by a client.
* Remote Method Invocation (RMI)
A protocol that is used to communicate method invocations over a network. Java Remote Method Invocation is a distributed object model in which the methods of remote objects that are written in the Java programming language can be invoked from other Java virtual machines, possibly on different hosts.
* Remote Method Invocation over Internet Inter-ORB Protocol (RMI/IIOP)
Part of the Java 2 Platform, Standard Edition (J2SE) model that developers can use to program in the Java language to work with RMI interfaces, but use IIOP as the underlying transport.
* Remote OSE
The use of the Open Servlet Engine (OSE) protocol as a transport mechanism to communicate between two separate machines in the WebSphere Application Server environment.
* * remote *
Pertaining to a system, program, or device that is accessed through a communications line.
* remote procedure call (RPC)
A protocol that allows a program on a client computer to run a program on a server.
* remote publication point
A representation of a remote proxy for a publication point that exists at a remote messaging engine. The remote publication point manages an outbound message stream to the publication point at the remote messaging engine.
* remote queue point
The representation of a remote proxy for a queue point that exists on a remote messaging engine. The remote queue point manages an outbound message stream to the queue point on the remote messaging engine, and an inbound message retrieval request stream for messages received from the queue point.
* * remove method *
In enterprise beans, a method defined in the home interface and invoked by a client to destroy an enterprise bean.
* * repertoire *
Configuration information that contains the necessary details for building a Secure Sockets Layer (SSL) connection.
* * replication *
The process of copying objects from one node in a cluster to one or more other nodes in the cluster, which makes the objects on all the systems identical.
* * replication entry *
A run-time component that handles the transfer of internal WebSphere Application Server data.
* * repository *
A persistent storage area for source code and other application resources. In a team programming environment, a shared repository enables multi-user access to application resources.
* * request consumer binding *
A definition of the security requests for the request message that is received by a Web service.
* * request generator binding *
A definition of the security requests for the request message that is sent to a Web service.
* * request metrics *
A mechanism to monitor and troubleshoot performance bottlenecks in the system at an individual request level.
* * request receiver binding *
A definition of the security requirements for the request message that is received from a request to a Web service.
* * request sender binding *
A definition of the security requirements for the request message that is sent to a Web service.
* * Resource Access Control Facility (RACF) *
An IBM licensed program that provides access control by identifying users to the system; verifying users of the system; authorizing access to protected resources; logging detected, unauthorized attempts to enter the system; and logging detected accesses to protected resources.
* * resource adapter *
A system-level software driver that is used by an EJB container or an application client to connect to an enterprise information system (EIS). A resource adapter plugs in to a container; the application components deployed on the container then use the client API (exposed by adapter) or tool-generated, high-level abstractions to access the underlying EIS. (Sun) See also container, enterprise information system.
* resource adapter archive (RAR)
A Java archive (JAR) file that is used to package a resource adapter for the Java 2 Connector (J2C) architecture.
* * resource environment reference *
A reference that maps a logical name that is used by the client application to the physical name of an object.
* * resource manager local transaction (RMLT) *
A resource manager view of a local transaction that represents a unit of recovery on a single connection that is managed by the resource manager.
* * resource property *
A property for a Java Database Connectivity (JDBC) data source in a server configuration, for example the server name, user ID, or password.
* Resource Recovery Services (RRS)
A z/OS facility that provides two-phase synchronization point support across participating resource managers.
* response consumer binding
A definition of the security requests for the response message that is received by a Web service
* * response generator binding *
A definition of the security requests for the response message that is sent to a Web service.
* * response receiver binding *
A definition of the security requirements for the response message that is received from a request to a Web service.
* response sender binding
A definition of the security requirements for the response message that is sent to a Web service.
* reverse proxy
An application proxy for servers using Hypertext Transfer Protocol (HTTP).
* reverse routing path
A stack of bus destinations within a request message through which a message is routed back to its origin. When the message is created, the reverse routing path is empty. As the message passes through each destination, the destination is pushed onto the stack. When the message reaches the final destination, the reverse routing path is copied to the forward routing path and the message is routed back through all the appropriate destinations.
* ripplestart
An action where the system waits for each member in a cluster to start before starting the next member of the cluster.
* RMI
See Remote Method Invocation.
* RMI/IIOP
See Remote Method Invocation over Internet Inter-ORB Protocol.
* RMLT
See resource manager local transaction.
* * role *
A logical group of principals that provide a set of permissions. Access to operations is controlled by granting access to a role.
* * role mapping *
The process of associating groups and principals that is recognized by the container to security roles that are specified in the deployment descriptor.
* * role-based authorization *
The use of authorization information to determine whether a caller has the necessary privilege to request a service.
* * routing policy *
A set of rules that determine how the server routes incoming requests.
* * RPC *
See remote procedure call.
* * RRS *
See Resource Recovery Services.
* rule set
A file that contains one or more rules.
* rule
An element that represents a statement in non-elemental form.
* * run time *
The time period during which a computer program runs.
* * RunAs role *
A role that is used by a servlet or an enterprise bean component to invoke and delegate a role to another enterprise bean.
* SAAJ
See SOAP with attachments API for Java.
* SAF
See System Authorization Facility.
* SAML
See Security Assertion Markup Language.
* SAR
See store archive.
* SAS
See Secure Association Service.
* SASL
See Simple Authentication and Security Layer.
* SCA
See Service Component Architecture.
* * scalability *
The ability of hardware, software, or a distributed system to continue to function well as it is changed in size or volume. For example, the ability to retain performance levels when you add processors, memory, and storage.
* scheduler
A service that provides time-dependent services.
* * schema *
1. A collection of database objects such as tables, views, indexes, or triggers that define a database. A database schema provides a logical classification of database objects. 2. In Extensible Markup Language (XML), a mechanism for describing and constraining the content of XML files by indicating which elements are allowed and in which combinations. XML schemas are an alternative to the document type definition (DTD) that you can use to extend functionality in the areas of data typing, inheritance, and presentation.
* * scope *
A specification for the boundary within which you can use system resources.
* * script *
A series of commands, combined in a file, that carry out a particular function when the file runs. Scripts are interpreted as they run.
* * scripting *
A style of programming that reuses existing components as a base for building applications.
* * SDO *
See Service Data Objects.
* SDO repository
A database that the service integration bus for Web services enablement uses for storing and serving Web Services Description Language (WSDL) definitions
* Secure Association Service (SAS)
An authentication protocol that the client principal uses to communicate, by establishing a secure association between the client and server.
* Secure Sockets Layer (SSL)
A security protocol that provides transport layer security, which consists of authenticity, integrity, and confidentiality, for a secure connection between a client and a server. The protocol runs above TCP/IP and below application protocols.
* Security Assertion Markup Language (SAML)
An XML framework for exchanging authentication and authorization information.
* security attribute propagation
The transportation of security attributes from one server to another server in a WebSphere Application Server configuration.
* * security constraint *
A declaration of how to protect Web content, and how to protect data that is communicated between the client and the server.
* * security domain *
The set of all the servers that are configured with the same realm name for the user registry or repository.
* * security permission *
Authorization granted to access a system resource.
* * security policy *
A written document that defines the security controls that you institute for your computer systems. A security policy describes the risks that you intend these controls to minimize and the actions to take if someone breaches your security controls.
* * security role reference *
A role that defines the access levels that users have and the specific resources that they can modify at those levels.
* * security token *
A representation of a set of claims that are made by a client that can include a name, password, identity, key, certificate, group, privilege, and so on.
* selector
A filter that is applied, when a consumer attaches to a bus destination, to indicate which messages the consumer is prepared to accept.
* * sequence grouping *
The specification of the order in which entity beans update relational database tables.
* serial access
An option that prevents the concurrent access and modification of a session in a given server instance.
* * servant region *
A contiguous area of virtual storage that is dynamically started as load increases and automatically stopped as load decreases.
* * server *
In a network, hardware or software that provides facilities to other stations. For example, a file server, a printer server, or a mail server. The station making the request of the server is usually called the client. See also host, client.
* * server cluster *
A group of servers that are typically on different physical machines and have the same applications configured within them, but operate as a single logical server.
* * server implementation object *
Enterprise beans that client applications require to access and implement the services that support those objects.
* * server-side include (SSI) *
A facility for including dynamic information in documents that are sent to clients, such as current date, the last modification date of a file, and the size or last modification of other files.
* service access point
A logical address that allows a system to route data between a remote device and the appropriate communications support.
* * service class *
A subset of a workload that has the same service goals or performance objectives, resource requirements, or availability requirements. For workload management, you assign a service goal to a service class.
* Service Component Architecture (SCA)
An architecture in which all elements of a business transaction, such as access to Web services, enterprise information system (EIS) service assets, business rules, workflows, databases and so on, are represented in a service-oriented way.
* * service context *
Part of a General InterORB Protocol (GIOP) message that is identified with an ID and contains data used in specific interactions, such as security actions, character codeset conversion, and Object Request Broker (ORB) version information.
* * Service Data Object (SDO) *
An open standard for enabling applications to handle data from heterogeneous data sources in a uniform way. SDO incorporates Java 2 Platform, Enterprise Edition (J2EE) patterns, but simplifies the J2EE data programming model.
* * service description *
The description of a Web service, which can be defined in any format such as Web Services Description Language (WSDL), Universal Discovery Description and Integration (UDDI), or Hypertext Markup Language (HTML).
* * service destination *
A specialization of a service integration bus destination. Each service destination can directly represent the Web service implementation or can indirectly represent the service through a Web Services Description Language (WSDL) document.
* * service integration bus *
A managed communication mechanism that supports service integration through synchronous and asynchronous messaging. A bus consists of interconnecting messaging engines that manage bus resources.
* service integration bus link
A link between messaging engines on different service integration buses.
* * service integration bus Web services enablement *
A software component that enables Web services to use IBM service integration technologies. This capability provides a quality of service choice and message distribution options for Web services, with mediations that support message rerouting or modification.
* service oriented architecture (SOA)
A conceptual description of the structure of a software system in terms of its components and the services they provide, without regard for the underlying implementation of these components, services, and connections between components.
* service principal name (SPN)
The name that uniquely identifies a service instance to a client.
* * service type definition *
In Universal Discovery Description and Integration (UDDI), a description of specifications for services or taxonomies.
* * servlet *
A Java program that runs on a Web server and extends the server's functionality by generating dynamic content in response to Web client requests. Servlets are commonly used to connect databases to the Web.
* * servlet filtering *
The process of transforming a request or modifying a response without exposing the resource that is used by the servlet engine.
* * servlet mapping *
A correspondence between a client request and a servlet that defines their association.
* * session *
A series of requests to a servlet that originates from the same user at the same browser.
* * session affinity *
A method of configuring applications in which a client is always connected to the same server. These configurations disable workload management after an initial connection by forcing a client request to always go to the same server.
* * session bean *
An enterprise bean that is created by a client and that usually exists only for the duration of a single client/server session. (Sun) See also entity bean.
* Session Initiation Protocol (SIP)
A protocol that initiates, modifies, and terminates interactive user sessions that involve multimedia. it works with other protocols and is involved specifically in the signaling portion of a communication session.
* * setter method *
A method whose purpose is to set the value of an instance or class variable. This capability allows another object to set the value of one of its variables. See also getter method.
* setup
The physical and logical arrangement of hardware and software that make up a data processing system.
* SGML
See Standard Generalized Markup Language.
* SHA-1
A Secure Hash Algorithm for computing a condensed representation of a message or data file.
* * shared library file *
A file that consists of a symbolic name, a Java class path and a native path for loading Java Native Interface (JNI) libraries. Applications that are deployed on the same node as this file can access this information.
* * short name *
In personal communications, the one-letter name (A through Z) of the presentation space or emulation session.
* Show Me
A link that launches an animated demonstration of the task that is being described in the documentation of the product.
* SIB service
In an application server, the service that provides service integration functions.
* * signer certificate *
The trusted certificate entry that is usually in a truststore file.
* silent installation
An installation that does not send messages to the console, but instead stores messages and errors in log files. A silent installation can use response files for data input.
* Simple and Protected Negotiation Mechanism (SPNEGO)
A protocol by which clients and servers determine an authentication mechanism.
* Simple Authentication and Security layer (SASL)
An Internet protocol that allows Lightweight Directory Access Protocol (LDAP) server and provides security for the data that is transmitted with this protocol.
* * Simple Object Access Protocol (SOAP) *
A lightweight, Extensible Markup Language (XML)-based protocol for exchanging information in a decentralized, distributed environment. You can use SOAP to query and return information and invoke services across the Internet.
* * simple type *
In the XML Schema language (XSL), a type that cannot have element content and cannot carry attributes. Elements that contain numbers, strings, dates, and so on, but do not contain any sub-elements. See also complex type.
* * single signon (SSO) *
An authentication process in a client/server relationship in which the user can enter one name and password and have access to more than one application.
* SIP
See Simple Object Access Protocol.
* * smart card *
An intelligent token that is embedded with an integrated circuit chip that provides memory capacity and computational capabilities
* * SOAP *
See Simple Object Access Protocol.
* * SOAP with attachments API for Java (SAAJ) *
An application programming interface (API) that is used to send XML documents over the Internet from a Java base.
* * socket *
A method of communication between two processes. A socket is an identifier that the application uses to uniquely identify an end point of communications. The user associates a protocol address with the socket by associating a socket address with the socket.
* * Sockets Secure (SOCKS) *
A client/server architecture that transports TCP/IP traffic through a secure gateway. A SOCKS server and a proxy server perform many of the same services.
* * SOCKS *
See Sockets Secure.
* software development kit
A set of tools, application programming interfaces (APIs), and documentation to assist with the development of software in a specific computer language or for a particular operating environment.
* special-subject
A generalization of a particular class of users; a product-defined entity that is independent of the user registry.
* SPN
See service principal name.
* SPNEGO
See Simple and Protected Negotiation Mechanism.
* SQL
See Structured Query Language.
* SQLJ
See Structured Query Language for Java.
* SSI
See server-side include.
* SSL
See Secure Sockets Layer.
* SSL channel
A type of channel within a transport chain that associates a Secure Sockets Layer (SSL) configuration repertoire with the transport chain.
* SSO
See single signon.
* stack
An area in memory that stores temporary register information, parameters, and return addresses of subroutines.
* Standard Generalized Markup Language (SGML)
A standard metalanguage for defining markup languages that is based on the ISO 8879 standard. SGML focuses on structuring information rather than presenting information; it separates the structure and content from the presentation. It also facilitates the interchange of documents across an electronic medium.
* stateful session bean
A session enterprise bean that acts on behalf of a single client and maintains client-specific session information, which is called conversational state, across multiple method calls and transactions.
* * stateless session bean *
A session bean that is a collection of operations. The server can optimize resources by reusing bean instances on every method call.
* statement
An instruction in a program or procedure.
* * static *
A Java programming language keyword that is used to define a variable as a class variable.
* store archive (SAR)
A platform-independent file format that aggregates many files into one.
* * stored procedure *
A block of procedural constructs and embedded Structured Query Language (SQL) statements that is stored in a database and that you can call by name. Stored procedures allow an application program to run in two parts, one on the client and the other on the server, so that one call can produce several accesses to the database.
* * stream decryption *
A symmetric algorithm that decrypts data one bit or byte of data at a time.
* * stream encryption *
A symmetric algorithm that encrypts data one bit or byte of data at a time.
* * string *
In programming languages, the form of data used for storing and manipulating text.
* * Structured Query Language (SQL) *
A standardized language for defining and manipulating data in a relational database. See also data manipulation language.
* * Structured Query Language for Java (SQLJ) *
A standard for embedding SQL in Java programs, defining and calling Java stored procedures and user-defined functions, and using database structured types in Java.
* * Struts *
An open source framework for building Java Web applications.
* * Struts module *
A Struts configuration file and a set of corresponding actions, form beans, and Web pages. A Struts application comprises at least one Struts module.
* * stub *
A small program routine that substitutes for a longer, possibly remote, program. For example, a stub might be a program module that transfers remote procedure calls (RPCs) and responses between a client and a server. In Web services, a stub is an implementation of a Java interface that is generated from a Web Services Description Language (WSDL) document.
* subscription point
A message point that represents a durable subscription and is associated with a publication point.
* * symmetric algorithm *
An algorithm where the encryption key can be calculated from the decryption key and vice versa. In most symmetric algorithms, the encryption key and the decryption key are the same.
* * syntax *
The rules for the construction of a command or statement. See also semantics.
* * sysplex *
See system complex.
* * System Authorization Facility (SAF) *
An interface defined by MVS that enables programs to use system authorization services in order to protect access to resources such as data sets and MVS commands. The IBM Resource Access Control Facility (RACF) is a product that uses the SAF interface.
* * system complex (sysplex) *
A set of MVS or OS/390 systems that communicate and cooperate with each other through certain multisystem hardware components and software services to process customer workloads.
* * system logger *
A central logging facility that system and subsystem components can use.
* * tag library *
In JSP technology, a collection of tags identifying custom actions described using a taglib descriptor and Java classes. A JSP tag library can be imported into any JSP file and used with various scripting languages. (Sun)
* * TAI *
See trust association interceptor.
* target
The destination for an action or operation.
* * target service *
A service that exists outside of the gateway.
* * TCP channel *
A type of channel within a transport chain that provides client applications with persistent connections within a local area network (LAN).
* temporary destination
A bus destination that is created by an application from a model destination that an administrator pre-configured. The application can delete temporary destinations automatically when the application disconnects.
* * temporary file system (TFS)*
A temporary, in-memory physical file system that supports in-storage mountable file systems. Normally, a TFS runs in the kernel address space, but it can be run in a logical file system (LFS) colony address space.
* TFS
See temporary file system.
* * thin application client *
A lightweight, downloadable Java application run time that is capable of interacting with enterprise beans.
* * thin client *
A client that has little or no installed software but has access to software that is managed and delivered by network servers that are attached to it. A thin client is an alternative to a full-function client such as a workstation.
* * thread *
A stream of computer instructions that is in control of a process. A multithread process begins with one stream of instructions, one thread, and might later create other instruction streams to perform tasks.
* * throughput *
The measure of the amount of work that is performed by a device, such as a computer or printer, over a period of time, for example, the number of jobs per day.
* * Time Sharing Option (TSO) *
An option of the MVS operating system that provides interactive time sharing from remote terminals.
* * Tivoli Performance Viewer *
A Java client that retrieves the Performance Monitoring Infrastructure (PMI) data from an application server and displays it in various formats.
* * TLS *
See Transport Layer Security.
* * token *
A particular message or bit pattern that signifies permission or temporary control to transmit on a network. See also token-ring network.
* topic
A character string that describes the nature of the data that is being published in a publish/subscribe system.
* topic space
1. A hierarchical collection of named topics. 2. A bus destination that is used in publish/subscribe messaging.
* topology
The physical or logical arrangement of nodes in a network, especially the relationship among nodes and the links between them.
* * transaction *
A specific set of input data that runs a specific process or job; a message that is destined for an application program.
* transaction class module
A transaction class and Web module pair.
* * transform algorithm *
A procedure that is used to transform the message for Web services security message processing, such as the C14N (canonicalization) transform that is used for Extensible Markup Language (XML) digital signatures.
* * transport *
The request queue between a WebSphere Application Server plug-in for Web servers and a Web container in which the Web modules of an application reside. When a user at a Web browser requests an application, the request is passed to the Web server, and then along the transport to the Web container.
* * transport chain *
A representation of a network protocol stack that is operating within an application server.
* * transport channel chain *
A specification of the transport channels that are used by a server for receiving information. Transport channel chains contain endpoints
* * Transport Layer Security (TLS) *
An Internet Engineering Task Force (IETF)-defined security protocol that is based on Secure Sockets Layer (SSL) and is specified in RFC 2246.
* * trust anchor *
A trusted keystore file that contains a trusted certificate or a trusted root certificate that is used to assert the trust of a certificate.
* * trust association *
An integrated configuration between the security server of the product and third-party security servers. A reverse proxy server acts as a front-end authentication server, while the product applies its own authorization policy onto the resulting credentials passed by the proxy server.
* trust association interceptor (TAI)
The mechanism by which trust is validated in the product environment for every request received by the proxy server. The method of validation is agreed upon by the proxy server and the interceptor.
* * trust file *
A file that contains signer certificates.
* * trust relationship *
An established and trusted communication path through which a computer in one domain can communicate with a computer in the other domain. Users in a trusted domain can access resources in the trusting domain.
* * trusted identity (ID) evaluator *
A mechanism that is used by a server to determine whether to trust a user identity during identity assertion.
* * truststore file *
A key database file that contains the public keys for that target server.
* * TSO *
See Time Sharing Option.
* type
1. In Java programming, a class or interface. 2. In a Web Services Description Language (WSDL) document, a container for data type definitions using some type system, such as W3C XML Schema (XSD).
* * type hierarchy *
The complete context for a Java class or interface including its superclasses and subclasses.
* UDDI
See Universal Discovery Description and Integration.
* UDDI node
A set of Web services that supports at least one of the Universal Description, Discovery, and Integration (UDDI) APIs. A UDDI node consists of one or more instances of a UDDI application running on an application server or a cluster of application servers with an instance of the UDDI database.
* UDDI node initialization
The process by which values are set in the Universal Description, Discovery, and Integration (UDDI) database and the behavior of the UDDI node is established.
* UDDI node state
A description of the current status for the Universal Description, Discovery, and Integration (UDDI) node.
* UDDI policy
A statement of the required and expected behavior for a Universal Description, Discovery, and Integration (UDDI) registry that is specified through policy values that are defined in the UDDI specification.
* UDDI property
A characteristic or attribute that controls the behavior of a Universal Description, Discovery, and Integration (UDDI) node.
* UDP
See User Datagram Protocol.
* * UML *
See Unified Modeling Language.
* * Unified Modeling Language (UML) *
A standard notation for the modeling of real-world objects as a first step in developing an object-oriented design methodology. UML is defined by the Object Management Group (OMG).
* * Uniform Resource Identifier (URI) *
A compact string of characters that identifies an abstract or physical resource.
* * Uniform Resource Locator (URL) *
The unique address of a file that is accessible in a network such as the Internet. The URL includes the abbreviated name of the protocol that is used to access the information resource and the information used by the protocol to locate the information resource.
* * Universal Discovery Description and Integration (UDDI) *
A distributed registry of businesses and their service descriptions that adhere to the Universal Description, Discovery, and Integration (UDDI) standard for managing the discovery of Web services. UDDI registries come in two forms, public and private, both of which are implemented in a common Extensible Markup Language (XML) format.
* * universally unique identifier (UUID) *
The 128-bit numerical identifier that is used to ensure that two components do not have the same identifier. The identifier is unique for all space and time.
* * unmanaged node *
A node that is defined in the cell topology. This node does not have a node agent that manages the process. An unmanaged node is typically used to manage Web servers.
* UOW
See unit of work.
* * URI *
See Uniform Resource Identifier.
* * URL *
See Uniform Resource Locator.
* * URL scheme *
A format that contains another object reference.
* User Datagram Protocol (UDP)
an Internet protocol that provides unreliable, connectionless datagram service. It enables an application program on one machine or process to send a datagram to an application program on another machine or process.
* * user name token *
A type of token that is represented by a user name and optionally, by a password.
* * user registry *
A database of known users and user-provided information that is used for authentication purposes.
* * UUID *
See universally unique identifier.
* * validation *
The checking of data or code for correctness or for compliance with applicable standards, rules, and conventions.
* * variable *
A configuration property that provides a parameter for any value in the system. It has a name and a value to use in place of that name wherever the variable name is located within the configuration files.
* version
A separately licensed program that usually has significant new code or new function.
* * vertical scaling *
Setting up multiple application servers on one machine, usually by creating cluster members.
* view
In Eclipse-based user interfaces, any pane in the workbench that is outside the editor area and can stack (drag and drop) on top of other views. Views provide different ways to work with the resources in the workbench.
* * view synchronous high-availability manager group *
A special class of high availability (HA) group that you can create for components to use that require a certain virtual synchrony (VS) quality of service (QoS) for group communication.
* View Synchrony Protocol
A multipoint communication protocol that provides synchronous message delivery and group membership; also known as Virtual Synchrony.
* * virtual host *
A configuration that enables a single host machine to resemble multiple host machines. Resources that are associated with one virtual host cannot share data with resources that are associated with another virtual host, even if the virtual hosts share the same physical machine.
* * virtual machine *
An abstract specification for a computing device that can be implemented in different ways in software and hardware.
* * virtual private network (VPN) *
An extension of a company's intranet over the existing framework of either a public or private network. A VPN ensures that the data that is sent between the two endpoints of its connection remains secure.
* * virtual synchrony (VS) *
A property of group communication that guarantees how messages are delivered when the view changes, for example, when existing members fail or new members join.
* * VPN *
See virtual private network.
* * VS *
See virtual synchrony.
* * W3C *
See World Wide Web Consortium.
* W3C XML Schema (XSD)
A library that provides an application programming interface (API) for manipulating the components of an XML Schema, as described by the W3C XML Schema specifications.
* * waiter *
A thread waiting for a connection.
* * WAR *
See Web archive.
* * WCCM *
See WebSphere Common Configuration Model.
* * Web application *
An application that consists of one or more related servlets, JavaServer Pages technology, and HyperText Markup Language (HTML) files that are managed as a unit.
* * Web archive (WAR) *
A compressed file format that is defined by the Java 2 Platform, Enterprise Edition (J2EE) standard, for storing all the resources that are required to install and run a Web application in a single file. See also enterprise archive.
* * Web browser *
A client program that initiates requests to a Web server and displays the information that the server returns.
* * Web component *
A servlet, JavaServer Page (JSP) file, or a HyperText Markup Language (HTML) file. One or more Web components make up a Web module.
* * Web container *
A container that implements the Web component contract of the J2EE architecture. (Sun)
* * Web container channel *
A type of channel within a transport chain that creates a bridge in the transport chain between an HTTP inbound channel and a servlet or JavaServer Pages (JSP) engine.
* * Web module *
A unit that consists of one or more Web components and a Web deployment descriptor. (Sun)
* * Web property extension (WPX)*
IBM extensions to the standard deployment descriptors for Web applications. These extensions include Multipurpose Internet Mail Extensions (MIME) filtering and servlet caching.
* * Web resource *
Any one of the resources that are created during the development of a Web application, for example Web projects, HTML pages, JSP files, servlets, custom tag libraries, and archive files.
* * Web resource collection *
A list of URL patterns and HTTP methods that describe a set of resources to be protected. (Sun)
* Web server
A software program that is capable of servicing Hypertext Transfer Protocol (HTTP) requests.
* * Web server plug-in *
A software module that supports the Web server in communicating requests for dynamic content, such as servlets, to the application server.
* * Web server separation *
A topology where the Web server is physically separated from the application server.
* * Web service *
A software system that is designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically Web Services Description Language (WSDL)).
* * Web Services Description Language (WSDL) *
An XML-based specification for describing networked services as a set of endpoints that operate on messages containing either document-oriented or procedure-oriented information.
* * Web Services Invocation Framework (WSIF) *
A Java application programming interface (API) that supports dynamic invoking of Web services, regardless of the format in which the service is implemented or the access mechanism.
* * WebSphere Common Configuration Model (WCCM) *
A model for programmatic access to configuration data that is used by the WebSphere Application Server tooling, run time, and administrative console.
* WebSphere
An IBM brand name that encompasses tools for developing e-business applications and middleware for running Web applications.
* WebSphere MQ client link
An optional component of a messaging engine that presents the messaging engine, and thereby the bus, as a WebSphere MQ queue manager to which WebSphere MQ clients can attach.
* WebSphere MQ link
An optional component of a messaging engine that defines the connection information necessary to establish a connection to a remote WebSphere MQ queue manager.
* * wizard *
An active form of help that guides users through each step of a particular task.
* * work manager *
A thread pool for Java 2 Platform, Enterprise Edition (J2EE) applications.
* * work object *
A type of asynchronous bean that applications implement to run code blocks asynchronously
* * workflow *
The sequence of activities that is performed in accordance with the business processes of an enterprise.
* * workload management *
The optimization of the distribution of incoming work requests to the application servers, enterprise beans, servlets and other objects that can effectively process the request.
* * workspace *
A temporary repository of configuration information that administrative clients use.
* * World Wide Web Consortium (W3C) *
An international industry consortium that develops common protocols to promote evolution and interoperability of the World Wide Web.
* * WPX *
See Web property extensions.
* * wrapper *
An alternate and supported interface that hides unsupported data types that are required by a server object behind a thin intermediate server object.
* * WSDL *
See Web Services Description Language.
* * WSIF *
See Web Services Invocation Framework.
* WS-Security
A Web services security standard that provides secure transmission of Simple Object Access Protocol (SOAP) messages.
* * X.509 certificate *
A certificate that contains information that is defined by the X.509 standard.
* X/Open XA
The X/Open Distributed Transaction Processing XA interface. A proposed standard for distributed transaction communication. The standard specifies a bidirectional interface between resource managers that provide access to shared resources within transactions, and between a transaction service that monitors and resolves transactions.
* XML
See Extensible Markup Language.
* * XML digital signature *
A specification that defines the XML syntax and the processing rules to sign and verify the digital signatures for the digital content.
* * XML encryption *
A specification that defines how to encrypt the content of an XML element.
* * XML parser *
A program that interprets the contents of an XML file and determines what to do with the input.
* * XML token *
A security token that is in an XML format, such as a Security Assertion Markup Language (SAML) token.
* XSD
See W3C XML Schema.
* * zip *
One or more files that are compressed and stored in a single file with a name ending in .zip.

ref: http://www.ibm.com/developerworks/wikis/display/xdcomputegrid/Glossary

How to encrypt the password in websphere and how to use PropFilePasswordEncoder command

2009-10-23T01:34:00.000-07:00

Content in the example file name is pass.properteis which is located in the C drive

Before conversion of the File
------------------------------------
database_username=db2admin
database_password=tirumal

Use the “PropFilePasswordEncoder.bat” command to encrypt the file

The command syntax is as follows:

PropFilePasswordEncoder "file_name" { passwordPropertiesList
| -SAS } [ -profileName profile ] [ -help | -? ]
Parameters
The following option is available for the PropFilePasswordEncoder command:

file_name
This required parameter specifies the name of the file in which passwords are encoded.

passwordPropertiesList
This parameter is required if you are encoding passwords in property files other than the sas.client.props file. Specify one or more password properties that you want to encode. The password properties list should be delimited by commas.

-SAS
This parameter is required if you are encoding passwords in the sas.client.props file.

-profileName
This parameter is optional. The profile value specifies an application server profile name. The script uses the password encoding algorithm that it retrieves from the specified profile. If you do not specify this parameter, the script uses the default profile.

-help or -?
If you specify this parameter, the script ignores all other parameters and displays usage text.

How to use the command?
Go the profile home in the command prompt
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>PropFilePasswordEncoder.bat c:\pass.properties database_password

database_password is the one we need to encrypt.

OUTPUT

#Fri Oct 23 12:46:16 IST 2009
database_username=db2admin
database_password= {xor}KzYtKjI+Mw\=\=

MQ related site with books

2009-09-29T23:19:00.000-07:00

http://publib.boulder.ibm.com/cgi-bin/bookmgr/Shelves/amqza909

* MQSeries Primer
http://www.informatik.uni-leipzig.de/cs/Literature/MQSerPrimer.pdf
* MQ Fundamentals
http://www.redbooks.ibm.com/redbooks/pdfs/sg247128.pdf
* System Administration Guide
http://www-01.ibm.com/software/integration/wmq/library/library53.html#Books

- System Administration Guide MQ Version 7.0 (Lates)http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/fa10120_.htm

- For More Information On System Administration Guide and other Material
http://www-03.ibm.com/certify/tests/edu994.shtml
* MQSeries intercommunication
http://as400bks.rochester.ibm.com/iseries/v5r2/ic2924/books/csqzae05.pdf
* MQ Clusters
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/csqzah03.pdf
* MQ Script (MQSC) Command Reference
http://www-01.ibm.com/support/docview.wss?uid=pub1sc34659700
* Basic UNIX Commands
http://www.sikh-history.com/computers/unix/commands.html

How to use the Windows Task Scheduler

2009-08-20T05:37:00.000-07:00

How to use the Windows Task Scheduler

http://www.iopus.com/guides/winscheduler.htm

Ref:http://forum.iopus.com/viewtopic.php?t=70
http://techgurulive.com/2009/02/23/how-to-block-ip-address-of-any-country-with-iptables/

Crontab

2009-08-20T05:32:00.000-07:00

Crontab

The crontab (cron derives from chronos, Greek for time; tab stands for table) command, found in Unix and Unix-like operating systems, is used to schedule commands to be executed periodically. To see what crontabs are currently running on your system, you can open a terminal and run:

sudo crontab -l

To edit the list of cronjobs you can run:

sudo crontab -e

This wil open a the default editor (could be vi or pico, if you want you can change the default editor) to let us manipulate the crontab. If you save and exit the editor, all your cronjobs are saved into crontab. Cronjobs are written in the following format:

* * * * * /bin/execute/this/script.sh

Scheduling explained

As you can see there are 5 stars. The stars represent different date parts in the following order:

1. minute (from 0 to 59)
2. hour (from 0 to 23)
3. day of month (from 1 to 31)
4. month (from 1 to 12)
5. day of week (from 0 to 6) (0=Sunday)

Execute every minute

If you leave the star, or asterisk, it means every. Maybe that's a bit unclear. Let's use the the previous example again:

* * * * * /bin/execute/this/script.sh

They are all still asterisks! So this means execute /bin/execute/this/script.sh:

1. every minute
2. of every hour
3. of every day of the month
4. of every month
5. and every day in the week.

In short: This script is being executed every minute. Without exception.
Execute every Friday 1AM

So if we want to schedule the script to run at 1AM every Friday, we would need the following cronjob:

0 1 * * 5 /bin/execute/this/script.sh

Get it? The script is now being executed when the system clock hits:

1. minute: 0
2. of hour: 1
3. of day of month: * (every day of month)
4. of month: * (every month)
5. and weekday: 5 (=Friday)

Execute on weekdays 1AM

So if we want to schedule the script to run at 1AM every Friday, we would need the following cronjob:

0 1 * * 1-5 /bin/execute/this/script.sh

Get it? The script is now being executed when the system clock hits:

1. minute: 0
2. of hour: 1
3. of day of month: * (every day of month)
4. of month: * (every month)
5. and weekday: 1-5 (=Monday til Friday)

Execute 10 past after every hour on the 1st of every month

Here's another one, just for practicing

10 * 1 * * /bin/execute/this/script.sh

Fair enough, it takes some getting used to, but it offers great flexibility.
Neat scheduling tricks

What if you'd want to run something every 10 minutes? Well you could do this:

0,10,20,30,40,50 * * * * /bin/execute/this/script.sh

But crontab allows you to do this as well:

*/10 * * * * /bin/execute/this/script.sh

Which will do exactly the same. Can you do the the math? ;)
Special words

If you use the first (minute) field, you can also put in a keyword instead of a number:

@reboot Run once, at startup
@yearly Run once a year "0 0 1 1 *"
@annually (same as @yearly)
@monthly Run once a month "0 0 1 * *"
@weekly Run once a week "0 0 * * 0"
@daily Run once a day "0 0 * * *"
@midnight (same as @daily)
@hourly Run once an hour "0 * * * *

Leave the rest of the fields empty so this would be valid:

@daily /bin/execute/this/script.sh

Storing the crontab output

By default cron saves the output of /bin/execute/this/script.sh in the user's mailbox (root in this case). But it's prettier if the output is saved in a separate logfile. Here's how:

*/10 * * * * /bin/execute/this/script.sh 2>&1 >> /var/log/script_output.log

Explained

Linux can report on different levels. There's standard output (STDOUT) and standard errors (STDERR). STDOUT is marked 1, STDERR is marked 2. So the following statement tells Linux to store STDERR in STDOUT as well, creating one datastream for messages & errors:

2>&1

Now that we have 1 output stream, we can pour it into a file. Where > will overwrite the file, >> will append to the file. In this case we'd like to to append:

>> /var/log/script_output.log

Mailing the crontab output

By default cron saves the output in the user's mailbox (root in this case) on the local system. But you can also configure crontab to forward all output to a real email address by starting your crontab with the following line:

MAILTO="yourname@yourdomain.com"

Mailing the crontab output of just one cronjob

If you'd rather receive only one cronjob's output in your mail, make sure this package is installed:

aptitude install mailx

And change the cronjob like this:

*/10 * * * * /bin/execute/this/script.sh 2>&1 | mail -s "Cronjob ouput" yourname@yourdomain.com

Trashing the crontab output

Now that's easy:

*/10 * * * * /bin/execute/this/script.sh 2>&1 > /dev/null

Just pipe all the output to the null device, also known as the black hole. On Unix-like operating systems, /dev/null is a special file that discards all data written to it.

source:http://kevin.vanzonneveld.net/techblog/article/schedule_tasks_on_linux_using_crontab/

Ref: http://www.crontabrocks.org/
http://linuxcommand.org/man_pages/crontab1.html
http://www.openjs.com/scripts/jslibrary/demos/crontab.php (conversion just try
this)

Scheduling Automatic Builds

2009-08-20T05:27:00.000-07:00

Scheduling Automatic Builds

It's time to add some automation to the build process. When you're working alone, you probably won't need to automate nightly builds, but as part of a team, it's a good idea. Larger projects typically have nightly builds posted to a web site, and using various automation tools and tasks like ftp, that's no problem. I'll take a look at various options here.

Unix

You can schedule recurring builds with Unix utilies like crontab, which you use to configure the cron daemon. For example, say you have a shell script that runs your nightly build, dobuild.sh, something like this:

export ANT_HOME=/usr/local/ant
export JAVA_HOME=/usr/local/jdk1.4
export PATH=${PATH}:${ANT_HOME}/bin
cd /home/work
ant -f nightlybuild.xml

You can schedule that build to happen at various times with crontab by starting its editing mode:

-bash-2.05b$ crontab -e

Edit the crontab file to include this line:

run at 00:01 every day 30 0 * * * $HOME/work/dobuild.sh

That makes your build run every night at 12:01 A.M. Easy enough.

Windows

The Windows at command schedules commands to run in Windows at specific times. For example, say you had a batch file, dobuild.bat, which runs your nightly build:

set ANT_HOME=C:\ant\apache-ant-1.6.1
set JAVA_HOME=C:\jdk1.4
set PATH=%PATH%;%ANT_HOME%\bin
cd C:\work
call %ANT_HOME%\bin\ant.bat -f nightlybuild.xml

You can schedule that build for every night with the Windows at command:

C:\ant>at 00:01 /every:M,T,W,Th,F "C:\work\dobuild.bat"
Added a new job with job ID = 1

To list scheduled at jobs, enter at:
Code View: Scroll / Show All

C:\ant>at
Status ID Day Time Command Line
-------------------------------------------------------------------------------
1 Each M T W Th F 12:01 AM C:\work\dobuild.bat

source:http://my.safaribooksonline.com/0596006098/anttdg2-CHP-4-SECT-4

What is the use of plugin

2009-08-05T04:48:00.000-07:00

1.)The plug-in provides work load management and failover
capabilities by distributing requests evenly to multiple
application servers and routing requests away from a
failed application server.

2.)Static content can be served by the Web server without
doing a full round trip to the application server, thus
providing better performance.

When to we use Tivoli performance viewer

2009-08-05T03:41:00.000-07:00

When to we use Tivoli performance viewer?

1.Failures due to load spikes
2.Application server hangs,
3.Timeout errors in a Web browser

WPAR

2009-08-04T07:38:00.000-07:00

WPAR
====
A workload partition is a new feature in AIX 6.1 that creates multiple AIX virtual partitions based on a single global AIX install.

For more info lookin:

http://www.ibm.com/developerworks/aix/library/au-wpar61aix/index.html

WAS 7.0 New Features and Functions

2009-07-27T23:26:00.000-07:00

WAS 7.0 New Features and Functions
----------------------------------
•IBM WAS V7 is a major release that offers dramatic run time improvements, plus simpler and easier ways to develop and deploy applications.

•WAS V7 provides complete support for the Java EE 5 specification, including the Web services and EJB 3.0 functions.

•WebSphere Application Server V7 also introduces support for Java Platform, Standard Edition (Java SE) 6
•Dependency injection - Developer productivity is further enhanced when it’s time to override the defaults, since this can be accomplished quickly and simply using annotations rather than writing code. Annotations are used in conjunction with a programming pattern known as dependency injection.
•Java Persistence API - Another aspect to the simplification of the programming model in Java EE 5 is the ability to develop EJB components as Plain Old Java Objects (POJOs). Simplifying EJB development even further is the Java Persistence API (JPA), which enables entities to be created using annotated POJOs. Aside from making EJB development and usage even easier, this also enables Java SE developers to quickly learn Java EE and develop enterprise applications.
•Web services - The improvements to the Java EE 5 programming model are not limited to EJB development. Web services development is also greatly simplified via annotations.
•Another important new systems management capability in V7 in the area of Web services, in addition to the programming model improvements, are Web service policy sets that are the mechanisms provided by WebSphere Application Server V7 for centrally defining various quality of service polices that you might want to apply to Web services that are already deployed. There are two types of policy sets: Application policy sets and System policy sets.
•JAX-WS implementation in WebSphere Application Server V7 also provides support for SOAP 1.2, as well as for generic XML or HTTP as a protocol binding, which enables the creation of WS clients and WS providers that do not use SOAP for their wire level message format.
•Another important addition in WebSphere Application Server V7 is its support for Message Transmission Optimization Mechanism (MTOM), an improved method for sending binary attachments. MTOM is the preferred attachment mechanism for non-Java EE-based Web services, so support for MTOM improves the interoperability between Java EE Web services and non-Java EE Web services.
•Portlet 2.0 API - WebSphere Application Server V7 also introduces support for the Portlet 2.0 API, also known as the Portlet JSR 286 specification.
•Intelligent provisioning - It selects only the run time function needed for an application, reducing both memory footprint and application server startup time. WebSphere Application Server examines each application at application installation time to generate an activation plan; at run time, the server starts only those components that are required by the activation plan.

•WAS V7 contains support for a Web/JDBC application scenario in which only the Web container and core run time components are started. This is in contrast to V6.1, in which the EJB container, SIP container, and Web services runtime would also have been started.

•The above capability can also help to reduce the memory footprint, and is designed for extension by other WebSphere products that run on top of WebSphere Application Server.

•Additional run time footprint reductions are delivered in the form of the Java SE 6 implementation that ships with WebSphere Application Server V7.

•The shared class cache that was introduced in IBM's Java SE 5 implementation has been improved so that the cache can now be persistent. As a result, the cache can survive a shutdown and restart of all WebSphere processes on a server. This lead to a significantly faster application server startup times.

•Another improvement in IBM's Java SE 6 is the use of compressed references (or pointer compression) in 64-bit WebSphere Application Server JVMs. The use of compressed references can provide a very significant reduction in the process footprint of a 64-bit JVM, when previously compared to a 32-bit JVM. Prior to IBM's Java SE 6 implementation, it wasn’t unusual for a 64-bit heap to be 1.7 to 2 times the size of an equivalent 32-bit heap.

•Flexible management is a new feature in WAS V7 that separate most of the administrative components from the application server runtime. Now, each application server is no longer a single point of management. This is accomplished with a separate administration process for (base) WebSphere Application Servers known as the administrative agent. This help to reduce the cost of administering large deployments in several ways.

•The job manager is another aspect of flexible management that is available in WebSphere Application Server Network Deployment V7. Its feature is for WAS V7 remote administration and scheduling of administrative functions.
•Messaging - Beyond the Web services improvements in WebSphere Application Server V7, there are also improvements to a related SOA component: messaging. New administrative wizards for System Integration Bus (SIBus) configuration are provided for configuring a cluster bus member and a foreign bus connection, as well as new panels for SIBus authorizations, WebSphere MQ JCA Resource Adapter configuration, and for inspecting an application's use of SIBus resources.
•WAS V7 also includes a WebSphere MQ JMS JCA 1.5 resource adapter, as well as associated new panels and administrative commands. Having the JCA 1.5 resource adapter also means that message-driven beans that consume messages from WebSphere MQ can now use activation specifications instead of listener ports.

•Improved management of activation specifications -- stop, start, message retry limits (or "poison" message filtering) -- is also included in WebSphere Application Server V7.
•Centralized installation - Network Deployment also adds the capability to perform centralized installation from the deployment manager to remote nodes. This enables a single installation to the deployment manager to be pushed out as an installation package from the deployment manager to a series of endpoints. The endpoint can be either a node that is not part of a Network Deployment cell.
•Business level applications - Another new function in WebSphere Application Server V7 is the notion of an "application" beyond J2EE™, or a business level application (BLA). This is a new administration concept that expands upon what was previously provided by J2EE.
•Security - Security management and auditing improvements are also a significant portion of what’s new in WebSphere Application Server V7. Perhaps the most prominent change is the capability to create multiple security domains within a single WebSphere Application Server cell. Each security domain can have its own user population (and underlying repository), and, additionally, the application domain can be separated from the administrative domain. Not only can each domain have its own separate user population, but each domain can also be customized with a separate security configuration -- for example, JAAS login configuration, TAI, authorization provider, JCA authentication data, and auditing -- in addition to the current application server level security configuration options.
•Further, the fine-grained administrative security function that was introduced in WebSphere Application Server V6.1 but limited to wsadmin is now expanded in V7 to include the administrative console. Within the administrative security domain for a cell, this enables administrative roles to be restricted to specific components, such as a cluster, node, application server, or application.
•Auditing - Another security enhancement is the option to generate security-auditing records of WebSphere Application Server administrative actions. These actions can be security configuration changes, key and certificate management, access control policy changes, bus and other system resources management, and so on. This feature enables you to hold administrative users accountable for configuration and run time changes.
•Further, the review and control of audit records and audit configurations is entrusted to a new auditor role, which enables the separation of administrative user privileges, in that an administrator cannot change audit policy and cannot view audit records, nor can an auditor change WebSphere configuration and run time state.
•Kerberos - WebSphere Application Server V7 provides support for Kerberos Authentication, which can be used in a variety of single sign-on scenarios. The Kerberos support in V7 expands on the SPNEGO TAI support in V6.1 to provide better interoperability and identity propagation with other applications that support Kerberos authentication (such as IBM DB2®, .NET®, and others).
•Application development and management - WebSphere Application Server V7 includes two tooling options for application development that let you leverage the standards supported in this new release:
•IBM Rational® Application Developer Assembly and Deploy V7.5 replaces the Application Server Toolkit (AST) function provided with WebSphere Application Server V6.1. This development tool expands on the functions provided in the AST with Java EE 5 XML-form based DD editors, Java EE 5 application support, and more.
• IBM Rational Application Developer V7.5 for WebSphere adds functions to Rational Application Developer Assembly and Deploy, including EJB 3 application development productivity features, visual editing domain modeling and Web development; Web services productivity features, and relational data tools.

WAS 6.1 New Features and Functions Updated

2009-07-27T23:08:00.000-07:00

WAS 6.1 New Features and Functions Updated
------------------------------------------

•Multiple installations of any WAS 6.1 edition are now allowed. Just specify a unique installation directory and default profile location.
•The products require Java* Developer Kit (JDK) 5.0 to install and run.
•By default, the ND installer creates a deployment manager profile and a federated node profile, which are part of the deployment manager cell.
•Administrative security is enabled by default when you install. You only need to specify the user name and password to use administrative security when installing, and the default profile is created with administrative security enabled.
•Portlet programming model.
•Installation factory to create customized installation packages (CIPs) from the installation image for a version or release of a WebSphere software product with applicable maintenance packages.
•High-availability (HA), scalability and Web services improvements.
•Ability to run your application server using either of the two supported i5/OS JDK 5 JVMs.
•Ability to install with CDs or DVDs.
•6.1 has a new way of configuring SSL
•6.1 is 64 bit enabled for better performance
•6.1 has a partitioned "profile" architecture that gives more flexibility for backups and updates
•6.1 come with better Admin Console - 6.1 now features a standalone thin admin client that can be used to administer application servers remotely.
•The IBM HTTP Server can also now be managed from the admin console.
•6.1 includes WebSphere Identity Manager (WIM)
•6.1 introduced SIP support (Session Initiation Protocol) - This is a key technology for IP Telephony like VOIP, IPTV, Internet chat etc.
•6.1 has small footprint of Portlet container
•It has future support for EJB 3.0 (Enterprise Java Beans)
•RAD 7 works with 6.1 not lower than RAD7
•For WAS 6.1, the TPV is running under the deployment manager, so it is recommended to get a more powerful server due to the PMI and GUI.
•In 6.1, it is recommended to code your own java client to get the PMI reading or install ITCAM.
•There is no problem found with 6.0 and 6.1 co-existing in the same cell, the same Node or machine.
•The JSR 168 portlet-programming model is supported - meaning portlets can be accessed like servlets via a URL without a full portal server. It is JSR 168 compliant.
•Integration (Service) between WebSphere MQ for z/OS and the default-messaging provider in WebSphere Application Server has been enhanced in Version 6.1, enabling you to add a queue manager or queue sharing group as a member of a service integration bus.
•The IBM Support Assistant is now bundled with WebSphere Application Server V6.1 for more effective and faster self-help and problem reporting. (PMR) submission
•Java Server Faces (JSF) support has been enhanced for you to easily build web applications
•Edge Components like Dynamic Cache Support, Cache identification and management capabilities has been enhanced.
•6.1 supports IPv6 at the node level; both IPv4 and IPv6 nodes can be federated into the same cluster. A node can also be configured in "dual mode" to support both protocols.
•The Packaging structure is supplied with only platform specific images
•In 6.1 - WebSphere Application Server can now be installed by a non-root user -In 6.0 IHS require root
•Application Server Toolkit (AST) in V6.1 reaches a key milestone because it includes a J2EE perspective and a Web perspective, Eclipse 3.1, and Version 1.0 of the Eclipse Web Tools Platform (WTP).
• In 6.1 AST is a complete J2EE development environment, thus you can use it to construct, debug, and deploy new applications directly to WebSphere Application Server V6.1.
•Web Services has been enhanced for better performance - e.g SAAJ changes, SOAP/JMS, WS-I BSP(Basic Security Profile 1.0) and W3C WS-Addressing.

cheat sheets for Linux,AIX,Solaries...............

2009-07-23T05:33:00.001-07:00

http://www.scottklarr.com/topic/115/linux-unix-cheat-sheets---the-ultimate-collection/

AIX:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.doc/doc/base/commandsreference.htm

About JVM logs

2009-07-20T07:56:00.000-07:00

JVM logs(SystemOut and SystemErr logs)

SystemOut and SystemErr logs are created for every WebSphere Application
Server process (application server, cluster member, node agent, and
deployment manager). These logs are known as JVM logs.

Your applications can also write to them by using the print(), println(), and
printStackTrace() methods.

Location:
WAS_install_root/profiles/profile/logs/process

To configure the properties of these logs from the administrative console, select
1.) Troubleshooting → Logs and Trace.
2.) Select the process (application server, cluster member, node agent, and
deployment manager) whose logs you want to configure,
3.) and then click JVM Logs

The SystemOut and SystemErr logs are self-managing. They write to the
specified file until either the maximum file size or a certain time is reached.
When that happens, the current log file is renamed as the current file name
plus the current time stamp. Then a new SystemOut or SystemErr file is
created for further logging. The older log files are called historical log files.

Example– SystemOut.log, the current log file
SystemOut_05.06.07_10.28.48.log, the historical log file

Example that tells us the format of the message that comes in the systemout.log

[7/12/05 14:46:00:264 EDT] 0000001a ApplicationMg A WSVR0221I: Application
started: adminconsole

Each entry can be deciphered as follows:
Time stamp
In the example, the time stamp is [7/12/05 14:46:00:264 EDT].
The time stamp is formatted using the locale of the process where it is
formatted. It includes a fully qualified date (for example MM/DD/YY), 24-hour
time with millisecond precision, and a time zone.

Thread ID
In the example, the thread ID is 0000001a.
The thread ID is an eight-character hexadecimal value that is generated from
the hash code of the thread that issued the message.

Short name
In the example, the short name is ApplicationMg.
The short name is the abbreviated name of the component that issued the
message. This name is typically the class name of a WebSphere Application
Server component and would be some other identifier for applications.

Event type
In the example, the event type is A.
The event type is a one character field that indicates the type of the message.
The possible values are:
– F - fatal message
– E - error message
– W - warning message
– A - audit message
– I - informational message
– C - configuration message
– D - detail message
– O - message that was written directly to System.out by an application or
internal components
– R - message that was written directly to System.err by the user application
or internal components
– Z - a placeholder to indicate that the type was not recognized
_ Message Identifier

In the example, the message identifier is WSVR0221I.

The message identifier is a string that is nine characters in length and is in the
form CCCC1234X. The first four characters (CCCC) indicate the WebSphere
Application Server component that issued the message. The next four
characters (1234) indicate the specific message that the component is
issuing. The last character (X) indicates the severity of the message. Its value
is either I (informational), W (warning), or E (error).

Interview Question

2009-07-14T04:22:00.000-07:00

How do u connect to Linux(GUI mode) ?

Nxclient for Windows is the tool, we use to connect to Linux box(GUI mode).

What is the difference between fix pack and Refresh pack?

Fix pack contains fixes for APAR(Authorized program analysis report).
Refresh pack contains some new features and functionality apart from fixes for APAR.

How to install gems and update them

2009-07-01T03:25:00.000-07:00

go to the command prompt and give :

c:\> gem update --system

c:\> gem install watir

c:\> gem uninstall watir

if ur having any problem .....then delete the folders in the Ruby....
and copy the folders of someone who installation is success(i.e all scripts are
running successfully) ..........this is the cheat cote

WSRR(Interview questions)

2009-06-12T03:02:00.000-07:00

1) What is the IBM WebSphere Service Registry and Repository?

WebSphere Service Registry and Repository is a system for storing, accessing and managing information, commonly referred as service metadata, used in the selection, invocation, management, governance and reuse of services in a successful SOA. In other words, it is where you store information about services in your systems, or in other organizations' systems, that you already use, plan to use, or want to be aware of. For example, an application can check the Registry & Repository just before invoking a service to locate the service instance best satisfying its functionality and performance needs. Registry & Repository also play a role in other stages of the SOA lifecycle.
Our view of a Registry & Repository encompasses:

Service Registry that contains information about services, such as their interfaces, operations and parameters
Metadata Repository providing a robust, extensible framework to suit the diverse nature of service usage.

2) What is a Service Registry?

A Service Registry contains information about services, such as the service definitions, interfaces, operations and parameters.

3) What is a Service Metadata Repository?

A Service Metadata Repository is a store to address the diverse nature of service usage. It stores service policies and other service metadata such as version, status, relationships and others that govern the service usage.

4) How do I know if I need the WebSphere Service Registry and Repository?

The promise of SOA depends heavily on the ability to share assets. Such sharing requires coordinated facilities for access and control. With SOA adoption, the increase in the number of services that an organization needs to track and manage becomes evident. Also, with adoption comes the recognition of a need for better processes to manage the lifecycle of services. A disciplined approach to lifecycle management, part of the overall governance, helps ensure that the design, development, deployment, and operation of services adhere to policies. In the most effective SOA deployments, governance processes are woven throughout all phases of the lifecycle. Governance addresses the need for financial transparency, the alignment between business and IT, and process control, as well as how these business imperatives are achieved. The right software tools can greatly facilitate governance. These are some of the primary indications on when one should consider WebSphere Service Registry and Repository as part of the SOA solution.

5) Why is WebSphere Service Registry and Repository so important to my business?

The WebSphere Service Registry and Repository is critical when deploying significant SOA projects because it enables you to:

Associate services with business tasks - Mapping IT services to your business design supports service lifecycle management and governance, giving you better control of your SOA environment.
Share your services - Identify common services to avoid duplication and foster reuse. WebSphere Service Registry and Repository supports not only discovery and reuse of services, but also associated metadata and artifacts.
Integrate with standard registries and repositories - With support for standards, WebSphere Service Registry and Repository federates multiple registries and repositories to ensure a unified view across many sources of service information.
Support interoperable services with governance - Interoperably leverage existing investments and infrastructure with WebSphere Service Registry and Repository support for WSDL, XML, XSD, BPEL, SCA and other standards.
Unlock the value of mainframe applications and databases - Expose mainframe applications and database interactions by publishing them as services. WebSphere Service Registry and Repository enables access to both mainframe and non-mainframe applications without invasive API-level coding.
Enforce best practices - WebSphere Service Registry and Repository provides functions and flexibility to help IT groups institute standards and best practices in their SOA deployments.
Incrementally adopt SOA - Institute cultural change incrementally and accelerate via best practices.

6) What are the key features of the WebSphere Service Registry and Repository?

The WebSphere Service Registry and Repository plays a major role in all four phases of the SOA lifecycle (Model, Assemble, Deploy and Manage). It helps you:

Manage Service Metadata: During service modeling, use the WSRR to create or re-use service descriptions, taxonomies, XML Schemas and other service metadata artifacts.
Find a Service: During service development or assembly, use the WSRR to locate services for reuse and enable the composition of new composite applications from existing services.
Publish a Service: During service deployment, publish service descriptions to the WSRR. You can augment the service descriptions generated by other tools, promoting reuse.
Facilitate Service Interaction: During service execution (e.g., WebSphere ESB mediations, ITIL processes, etc.) use the WSRR to access service metadata and endpoint information as well as capture service metrics key so you can assess key performance indicators against your business and operational objectives.
Enable SOA Governance: The WebSphere Service Registry and Repository is the core that underpins governance in the SOA Foundation, to help you manage your overall SOA infrastructure.

*For details, please see the IBM SOA Foundation white paper (PDF, 226KB).

7) What kind of information can be stored in WebSphere Service Registry and Repository?

You can put WSDL files, XSDs, WS-Policy documents and any XML file in WSRR. We also support storing SCDL and BPEL documents. WSRR automatically derives the service related information from these documents like operations, interface, types etc. You can then add metadata to these physical as well as derived entities by using the classification system and/or properties (which are user-defined name-value pairs). You can also define relationships/dependencies between various entities e.g. between two services or between service and policies.

8) How is it different from UDDI (Universal Description, Discovery, and Integration)?

UDDI provides basic publish and discovery of Web service descriptions. It does not provide a standard repository capable of storing artifacts, nor governance capabilities for managing the end-to-end life cycle of the various types of artifacts related to services. UDDI has other limitations as well. For example, UDDI data model is restrictive which puts constraints on both the information that can be managed as well as the ability to support different usage models e.g. development, runtime, and management – this is due to the fact that the classification system used in UDDI is highly technical taxonomy which fails to capture the web service semantic that is required to fully exploit the potential of web services i.e. dynamic discovery, selection, and binding. UDDI also requires multiple communication exchanges to perform a single operation, which may not be suitable for all environments.

9) Is WSRR a Runtime or Development Time repository?

IBM views WSRR as relevant to overall SOA lifecycle in driving the service lifecycle. It is optimized for and primary interactions are for run-time operations. There maybe Find and Publish interaction at design/development/assembly stages to find a deployed service or update a service metadata to reflect it’s lifecycle state.

10) What's the level of effort needed to organize services in WSRR?

This is fairly minimal since the organization of services is browser based and intuitively aligns with how you want to view the services.

11) Does WSRR provide a workflow capability?

WSRR provides a state transition engine that enables service lifecycle capability. The more complete workflow/process engine is provided by IBM WebSphere Process Server. WebSphere Service Registry and Repository is integrated to WebSphere Process Server and leverages the process flows, as applicable to service lifecycle transitions.

For more information on WebSphere Process Server, please refer to: http://www.ibm.com/software/integration/wps/

13) Many products on the market build upon and extend UDDI to support additional functions needed for SOA implementation and management. Are we also following the same approach?

No. It is possible to address some of the UDDI problems by extending UDDI but that is an inefficient way of solving the problem. Moreover, there are emerging standards and classification systems that are better suited to the needs of service registries. WebSphere Service Registry and Repository will instead align with these focused standards. We will however integrate with UDDI and UDDI based registries using copy and synchronize approach.

14) What emerging standards are being published around Web Services and Service Registries? What are the emerging standards and classification systems?

IBM, Microsoft, HP and Intel recently published a roadmap for converging Web Services standards for resources, events and management, which will result in new specifications e.g. WS-ResourceTransfer and WS-EventNotification, and new versions of existing specifications e.g. WS-MetadataExchange. For details please refer to http://www.ibm.com/autonomic/wsdm/convergence. As far as classification systems are concerned, WebSphere Service Registry and Repository offers OWL-based user-defined semantic classifications on all parts of the object model, including operations, data types and interfaces.

15) Does that mean that WebSphere Service Registry and Repository will have a standards based Web Services interface?

That is correct. WebSphere Service Registry and Repository is a J2EE application that installs on top of a WebSphere Application Server. Persistence is provided by IBM metadata management technology (Metadata Server) which interacts with a Relational Data Base configured through the Application Server. WebSphere Service Registry and Repository provides both Java and SOAP APIs. Basic CRUD operations as well as governance operations and a flexible query capability based on XPath are provided through both APIs. The product also has a web-based user interface for users representing different roles to interact with the WSRR, supporting lookup and publish scenarios, metadata management and analysis scenarios, and functions that support SOA governance.

16) How does the WebSphere Service Registry and Repository integrate with other IBM products?

WSRR integrates with development tooling using an Eclipse plug-in to support lookup, retrieval and publishing of service metadata. The product will provide an ESB Mediation and Routing Node based on metadata query for WebSphere ESB and Message Broker respectively.

17) What is the roadmap of WebSphere Service Registry and Repository in relation to Web Services Gateway/UDDI in WAS?The WebSphere Service Registry and Repository is a crucial part of the SOA foundation that fills governance needs by providing a registry for information (metadata) about services and the interaction of services with other SOA infrastructure elements. Not merely a governance tool, the WebSphere Service Registry and Repository also helps unlock the full potential of SOA by promoting the rapid integration of services. It supports service creation and access, publication of information about services - enabling software reuse - and subscription to services, speeding up enterprise-wide adoption of SOA. These capabilities are more focused towards SOA with optimizations for SOA runtimes and the evolving needs in SOA Governance along with service metadata needs. The WebSphere Service Registry and Repository with its more advanced capabilities, fostering reuse and leverage of services becomes core to SOA deployments. Web services gateway and UDDI within WAS are basic offering to enable base web services access. They will continue to function as they are offered today within WAS although the need for addressing some of the more advanced and evolving needs of SOA will quickly lead towards a WebSphere Service Registry and Repository. The WebSphere Service Registry and Repository will federate service endpoint information that may be residing in the UDDI within WAS so that the service information is consistent to access either within WebSphere Service Registry and Repository or just the UDDI and WS Gateway. Increasingly the ESB (WebSphere ESB or the Message Broker) will function as the gateway to all the services within a SOA deployment. Overtime, the capabilities of UDDI will be subsumed with the WebSphere Service Registry and Repository and the Web Services Gateway within WebSphere ESB

18) What is the interaction, linkage and roadmap of IBM Business Partners focused SOA Business Catalog and the SOA Foundation component - IBM WebSphere Service Registry and Repository?

IBM WebSphere Service Registry and Repository will be used across the enterprise SOA infrastructure to raise the visibility of reusable services fostering reuse. There will be situations where the services internally within the enterprise may not be complete to drive the SOA solution and there may be a need to access other services provided by IBM SOA partners. This is where the linkage between the internally focused WebSphere Service Registry and Repository with the external SOA Business Catalog will be beneficial for IBM SOA offering. Overtime the WebSphere Service Registry and Repository may not only link to the external SOA Business Catalog but also host these services (Plans subject to change). This interaction and linkage along with the roadmap is key to understand when business partners are building assets towards the SOA Business Catalog. The business partners who have services - and repositories today can work with IBM to interact with the IBM WebSphere Service Registry and Repository solution, so that customers will see the benefit of an IBM solution - and can consume it that way.

19) Are there other IBM products that will help me get the most out of my WebSphere Service Registry and Repository?

Yes, typical patterns in SOA leads to the following complimentary products:

WebSphere ESB
WebSphere Message Broker
WebSphere Process Server
ITCAM for SOA
Rational Portfolio Manager
WebSphere Metadata Server
WebSphere Application Server

20) What is the difference between a registry, catalog and a repository?

A registry is an authoritative store of information that relates to a particular task at hand. Registries are typically built for a particular purpose such as a "gift registry".

A repository stores assets. Repositories are built for the specific kind of assets they are meant to hold and the modes of interaction they must support. Databases, file systems, and content management systems are all repositories of one sort or another, and they are all tailor-made for their specific requirements.

A catalog is where you advertise – For ex, IBM SOA Business Catalog advertising IBM SOA Business partners services.

These info is from

http://www-01.ibm.com/software/integration/wsrr/library/faqs.html

Why Drivers Matter (part 3)

2009-05-23T23:28:00.000-07:00

Why Drivers Matter
A JDBC driver can make a world of difference in how well your application performs. Features supported by your JDBC driver are in fact critical to system performance. This is particularly true in enterprise database applications, and more so in applications accessing distributed data sources.

Many database products ship with their own JDBC drivers. So why should you purchase a separate driver when you already may get one free in your DBMS? There are several reasons. First, the handful of vendors who actually develop these drivers (most database vendors license their drivers) can offer you better support for their drivers than the database vendors can offer for drivers they only license. This is not surprising: Creating commercial-quality drivers is hard work. The driver creator would be expected to know the driver details better than anyone else—Driver design is what they do.

Many developers don't realize that their JDBC driver can be a performance bottleneck for their application because of issues like connection handling. They are pleasantly surprised, for example, when they upgrade their native database JDBC driver to a Type 3 or Type 4 JDBC product from a dedicated driver vendor. Many companies make major purchases of a JDBC driver vendor's product even when a version of that product is part of the DBMS that they already own.

As you look to the future, consider the features that JDBC 3.0 provides as a marker in deciding which driver to consider, including DataSource objects, connection pooling, distributed transaction support, RowSets, and prepared statement pooling. When possible, choose a vendor whose drivers work directly with database vendors APIs, and not drivers that have been reversed engineered to work with those APIs. The former type is typically a faster performer.

Type 3 and Type 4 drivers are the drivers to use when performance and compliance with Java standards is a must. It's extremely worthwhile to find a vendor whose drivers support the very latest versions of JDBC and the widest array of JDBC features. Another factor to consider is that different JDBC drivers offer tools that don't normally come with native DBMS drivers—tools that can be quite important in your development work.

JDBC Drivers: How Do You Know What You Need?(part 2)

2009-05-23T23:26:00.000-07:00

JDBC Drivers: How Do You Know What You Need? (cont.)
JDBC Driver Features
Sun Microsystems maintains a listing of JDBC drivers at: http://industry.java.sun.com/products/jdbc/drivers, shown in Figure 3. This web page offers a driver selector tool that allows you to generate a list of drivers that support specific features, including driver types, JDBC version support, and access to one or multiple specific databases. As of the writing of this article (March 2002) there were 155 drivers listed on this page!

Note: The driver selector tool shown in Figure 3 hasn't yet been updated to account for JDBC version 3.0, so expect to see some changes in this tool in the months to come. What you see in Figure 3 might not match what is on the Sun Microsystems web page at a later date.

Let's consider the feature choices listed on the Sun Microsystems JDBC driver web page in a little detail, because, as we said, many people use this tool to select one driver over another:

JDBC API version number (Any, 1.x or 2.x (select one)).

Certified for J2EE: J2EE 1.3 or J2EE 1.2 (select any or all).

Driver Type: 1, 2, 3, 4, All, or Any (select any or all).

Supported DBMS. There are 83 choices, mostly vendor products, but a few of which are industry standards like JDBC, LDAP, ODBC, OLE DB Provider, Text (TSV), SQL/DS, and XML. One or a group of selections are supported.

Required Features: DataSource, Connection Pooling, Distributed Transactions, and RowSets (pick any or all).

Returns per page (specifies the number of matches returned).

Figure 3. Sun's JDBC Driver home page offers a selection tool that helps a developer select a driver based on its type and a number of other factors.

Let's take a look at each feature in turn, and see if we can make sense out of each feature and their options.

JDBC API
The JDBC API is important because it determines the Java functionality available to a developer. While older Java applications may not be able to take advantage of the more advanced features provided by JDBC 3.0, any high-transaction, distributed application certainly would. What developers get when they use later versions of the API is any new DBMS and operating-system security enhancements, and the latest performance improvements such as advancements in connection pooling, statement pooling, RowSet objects, and so forth.

Certification
Remember that JDBC is a specification, and not a standardized piece of software. Vendors are free to implement their JDBC drivers to that specification as they see fit, and while some JDBC drivers are fully J2EE compliant; many other drivers are not. When considering one driver over another, the Certified for J2EE logo, as specified by the Sun Certification Test Suite (CTS) and administered by Key Labs, is one yardstick a company can use to measure a driver's quality. Any company who undertakes the certification process is more likely to pay attention to quality control in their product. You will find a listing of vendors who have endorsed the JDBC standard and have products in this area at: http://java.sun.com/products/jdbc/industry.html.

Required Features
The "Required Features" section shown in Figure 3 lists some features, introduced in JDBC 2.0, but required for JDBC version 3.0.

A DataSource is an object containing the connection information to a database that is managed by a JDBC driver. Data sources work with a JNDI (the Java Naming Directory Interface) service, and a connection is instantiated and managed independently of the applications that use it. Connection information, such as path and port number, can be quickly changed in the properties of the DataSource object without requiring code changes in the applications that use the data source. Currently 50 of the 155 listings (not all are drivers) on the Sun Microsystems web page support this feature.

JDBC supports connection pooling, which essentially involves keeping open a cache of database connection objects and making them available for immediate use for any application that requests a connection. Instead of performing expensive network roundtrips to the database server, a connection attempt results in the re-assignment of a connection from the local cache to the application. When the application disconnects, the physical tie to the database server is not severed, but instead, the connection is placed back into the cache for immediate re-use, substantially improving data access performance.

Opening a connection is the most resource-expensive step in database transactions. When an application creates a connection, multiple separate network roundtrips must be performed to establish that connection (for an Oracle connection, that number is nine). However, once the connection object has been created, there is little penalty in leaving the connection object in place and reusing it for future connections. This feature offers significant potential to improve data transfer performance and scalability, especially for application servers. This feature is supported by 50 of the listings on the Sun Microsystems web page.

In a distributed system, applications often must retrieve data using multiple transactions, and often from multiple data sources. Any transaction that requires the coordination of independent cooperating transactional systems is referred to as a distributed transaction. Aside from the performance characteristics of JDBC drivers, distributed transaction support is probably the most requested feature by Java database developers.

Distributed transactions require additional resources to be reliably supported, primarily because of the differences in latencies when retrieving data from different data sources, and because of interoperability issues. For example, a failed transaction is not easily differentiated from a slow transaction, requiring resource managers in a DTS be both registered and coordinated to handle ROLLBACK or COMMIT operations correctly without a lot of code development.

Typically, distributed transactions use a transaction manager to provide the coordination that the different resource managers need. With a transaction manager in a Distributed Transaction Processing (DTP) architecture providing the mediation between applications and resources, it's possible to provide applications with ACID transactions across multiple data sources.

In a situation where multiple steps are required to produce the desired result, there needs to be a software module, which is often a transaction manager, coordinating the process. A product like iPlanet Trustbase Transaction Manager is one example of this type of software. It's used in global banking and B2B systems to provide the services required to secure processing and routing based on a key structure, and includes cryptographic support and identity checking. Only 34 of the drivers on the Sun Microsystems JDBC driver web page offer this feature.

A RowSets object is the result set of a query containing rows from a tabular data source. RowSets have properties and event notification similar to JavaBeans and are a JavaBean component that can be created and used programmatically in a development tool. There are connected and disconnected rowsets. Disconnected rowsets are connected to a data source that is populated and do not require a JDBC driver when disconnected. These types of rowsets are small, and often are used to send data to a thin client. Disconnected rowsets are stored in memory along with their metadata and connection and execution instructions. A connected rowset maintains an open connection while the rowset is being used. Only 18 of the drivers now listed support the rowsets feature, which as this small number suggests, isn't an often used feature.

A note worth mentioning: On the Sun JDBC Driver site, Sun defines "support" for RowSets to mean actually packaging and shipping the RowSets with the JDBC driver. Thus, you will find that there are drivers on this site that, while not showing a check mark next to "RowSets," in fact do support multiple types of RowSets.

Not on the current list, but sure to be added as a searchable feature because it's in JDBC version 3.0, is a feature called prepared statement pooling. Essentially, statement pooling caches SQL queries that have been previously optimized and run so that, should they be needed again, they do not have to go through optimization pre-processing again. Statement pooling can be a significant performance booster and is something to look for in any JDBC driver.

Prepared statements are particularly valuable when the same SQL statement is executed many times. A query that populates the current status of a particular category of inventory, run many times during the day, would be one example. To execute the statement a second time, only the values of the statement's parameters need to be passed to it. All the optimization steps, such as checking syntax, validating addresses, and optimizing access paths and execution plans, are already cached in memory. Statement caching is a JDBC driver feature.

What's even better from a developer's standpoint is that statement pooling operates without a developer having to code for it (as does connection pooling). You get the performance enhancement when you buy a driver that supports this feature.

Statement pooling and connection pooling can work together in your applications, as long as your driver supports them. When a J2EE Enterprise JavaBean and session bean makes use of a connection from the connection pool, any connection that was previously used to run a SQL statement will have its statement pool already defined. Therefore, even the application's first attempt to prepare a statement for a particular connection will not require the statement preparation process. Statement pooling can be used on any connection, regardless of whether the connection came from a non-pooled data source, or from an application server that uses a pooled data source or a JDBC driver's connection pool.

JDBC Drivers: How Do You Know What You Need?(part 1)

2009-05-23T23:24:00.000-07:00

JDBC Drivers: How Do You Know What You Need? (cont.)
The JDBC Specification
Now let's take a look at the specifics. JDBC has gone through several major version releases:

JDBC 1.0 was designed to provide basic functionality with an emphasis on ease of use.

JDBC 2.0 offered more advanced features and server-side capabilities.

JDBC 3.0 "rounded out" the API by providing performance optimization. It added improvements in the areas of connection pooling, statement pooling, and provided a migration path to Sun Microsystems' connector architecture.

The optional features in JDBC 2.0 (such as connection and distributed transactions) are now required features in JDBC 3.0, along with the new features in JDBC 3.0, such as prepared statement pooling.

JDBC Driver Types—Know the Difference
Database access by Java applications wasn't part of the original Java specification. It didn't take long for Sun Microsystems and other vendors to fill the gap. Early data-access Java methods relied on bridging the Microsoft-sponsored ODBC (Open Database Connectivity) standard for access to data sources, resulting in the JDBC-ODBC bridge drivers.

Today, there are four types of JDBC drivers in use:

Type 1: JDBC-ODBC bridge, plus an ODBC driver

Type 2: native API, part-Java driver

Type 3: pure Java driver for database middleware

Type 4: pure Java driver for direct-to-database

Type 3 and Type 4 JDBC drivers are both pure Java drivers, and therefore, offer the best performance, portability, and range of features for Java developers.

Type 1
A Type 1 JDBC driver is a JDBC-ODBC Bridge, plus an ODBC driver. Sun Microsystems recommends using Type 1 drivers for prototyping only and not for production purposes. The bridge driver is provided by Sun without support to developers and is intended to support legacy products. When a major patch is required, Sun provides it, but they do not provide end-user support for this software. Typically, the bridge is used when there is already an investment in ODBC technology, such as in Windows application servers.

Sun Microsystems provides a JDBC-ODBC Bridge driver, but because ODBC loads binary code and database client code on the client using the bridge, this technology isn't suitable for a high-transaction environment. Type 1 drivers also don't support the complete Java command set and are limited by the functionality of the ODBC driver.

Type 2
A Type 2 JDBC driver is a native-API, part-Java driver. Type 2 drivers are used to convert JDBC calls into native calls of the major database vendor APIs. These drivers suffer from the same performance issues as Type 1 drivers, namely binary-code client loading, and they are platform-specific.

Type 2 drivers force developers to write platform-specific code, something no Java developer really wants to do. But, because large database vendors, such as Oracle and IBM, use Type 2 drivers for their enterprise databases, developers who use these drivers must keep up with different driver releases for each database vendor's product release and each operating system.

Also, because Type 2 drivers don't use the full Java API, developers find themselves having to perform additional configuration when connecting Java applications to data sources. Often, Type 2 drivers aren't architecturally compatible with mainframe data sources, and when they are, they are less than ideal.

For these reasons and others, most Java database developers opt for either Type 3 or the newer and more flexible Type 4 pure Java JDBC drivers.

Figure 1. The Architectural Difference Between Type 1 and Type 2 Drivers. While Type 1 JDBC drivers offer convenience of access to ODBC data sources, they are limited in their functionality and performance. Type 2 JDBC drivers are OS-specific and compiled, and although they offer more Java functionality and higher performance than Type 1 drivers, still require a controlled environment. Figure courtesy of Sun Microsystems.

Type 3
Type 3 JDBC drivers are pure Java drivers for database middleware. JDBC calls are translated into a middleware vendor's protocol, and the middleware converts those calls into a database's API. Type 3 JDBC drivers offer the advantage of being server-based, meaning that they do not require native client code, which makes Type 3 drivers faster than Type 1 and Type 2 drivers. Developers can also use a single JDBC driver to connect to multiple databases.

Type 4
Type 4 JDBC drivers are direct-to-database pure Java drivers ("thin" drivers). A Type 4 driver takes JDBC calls and translates them into the network protocol (proprietary protocol) used directly by the DBMS. Thus, client machines or application servers can make direct calls to the DBMS server. Each DBMS requires its own Type 4 driver; therefore, there are more drivers to manage in a heterogeneous computing environment, but this is outweighed by the fact that Type 4 drivers provide faster performance and direct access to DBMS features.

Figure 2. The architectural difference between Type 3 and Type 4 drivers. Type 3 drivers leverage the advantages of middleware products to supply heterogeneous database access, and are a strong server-side solution when that middleware product runs on a single OS. Type 4 drivers provide fast and powerful direct access from Java clients to the databases themselves, but do not provide some of the server-side OS optimization found in Type 3 drivers. Figure courtesy of: Sun Microsystems.

JDBC Driver Types

2009-05-23T23:22:00.000-07:00

JDBC Driver Types

JDBC drivers are divided into four types or levels. The different types of jdbc drivers are:

Type 1: JDBC-ODBC Bridge driver (Bridge)
Type 2: Native-API/partly Java driver (Native)
Type 3: AllJava/Net-protocol driver (Middleware)
Type 4: All Java/Native-protocol driver (Pure)

4 types of jdbc drivers are elaborated in detail as shown below:

Type 1 JDBC Driver

JDBC-ODBC Bridge driver

The Type 1 driver translates all JDBC calls into ODBC calls and sends them to the ODBC driver. ODBC is a generic API. The JDBC-ODBC Bridge driver is recommended only for experimental use or when no other alternative is available.

Type 1: JDBC-ODBC Bridge

Advantage

The JDBC-ODBC Bridge allows access to almost any database, since the database's ODBC drivers are already available.

Disadvantages

1. Since the Bridge driver is not written fully in Java, Type 1 drivers are not portable.
2. A performance issue is seen as a JDBC call goes through the bridge to the ODBC driver, then to the database, and this applies even in the reverse process. They are the slowest of all driver types.
3. The client system requires the ODBC Installation to use the driver.
4. Not good for the Web.

Type 2 JDBC Driver

Native-API/partly Java driver

The distinctive characteristic of type 2 jdbc drivers are that Type 2 drivers convert JDBC calls into database-specific calls i.e. this driver is specific to a particular database. Some distinctive characteristic of type 2 jdbc drivers are shown below. Example: Oracle will have oracle native api.

Type 2: Native api/ Partly Java Driver

Advantage

The distinctive characteristic of type 2 jdbc drivers are that they are typically offer better performance than the JDBC-ODBC Bridge as the layers of communication (tiers) are less than that of Type
1 and also it uses Native api which is Database specific.

Disadvantage

1. Native API must be installed in the Client System and hence type 2 drivers cannot be used for the Internet.
2. Like Type 1 drivers, it’s not written in Java Language which forms a portability issue.
3. If we change the Database we have to change the native api as it is specific to a database
4. Mostly obsolete now
5. Usually not thread safe.

Type 3 JDBC Driver

All Java/Net-protocol driver

Type 3 database requests are passed through the network to the middle-tier server. The middle-tier then translates the request to the database. If the middle-tier server can in turn use Type1, Type 2 or Type 4 drivers.

Type 3: All Java/ Net-Protocol Driver

Advantage

1. This driver is server-based, so there is no need for any vendor database library to be present on client machines.
2. This driver is fully written in Java and hence Portable. It is suitable for the web.
3. There are many opportunities to optimize portability, performance, and scalability.
4. The net protocol can be designed to make the client JDBC driver very small and fast to load.
5. The type 3 driver typically provides support for features such as caching (connections, query results, and so on), load balancing, and advanced
system administration such as logging and auditing.
6. This driver is very flexible allows access to multiple databases using one driver.
7. They are the most efficient amongst all driver types.

Disadvantage

It requires another server application to install and maintain. Traversing the recordset may take longer, since the data comes through the backend server.

Type 4 JDBC Driver

Native-protocol/all-Java driver

The Type 4 uses java networking libraries to communicate directly with the database server.

Type 4: Native-protocol/all-Java driver

Advantage

1. The major benefit of using a type 4 jdbc drivers are that they are completely written in Java to achieve platform independence and eliminate deployment administration issues. It is most suitable for the web.
2. Number of translation layers is very less i.e. type 4 JDBC drivers don't have to translate database requests to ODBC or a native connectivity interface or to pass the request on to another server, performance is typically quite good.
3. You don’t need to install special software on the client or server. Further, these drivers can be downloaded dynamically.

Disadvantage

With type 4 drivers, the user needs a different driver for each database.

Interview questions (Webserver errors)

2009-05-23T23:12:00.000-07:00

Web Server Error Messages
Errors on the Internet, and those annoying error messages, occur quite frequently -- and can be quite frustrating, especially if you do not know the difference between a 404 error and a 502 error. Many times they have more to do with the Web servers you're trying to access rather than something being wrong with your computer. Here is a list of error messages you might encounter while surfing the Web and their respective meanings to help you figure out just what the problem is.

400 Bad File Request	Usually means the syntax used in the URL is incorrect (e.g., uppercase letter should be lowercase letter; wrong punctuation marks).
401 Unauthorized	Server is looking for some encryption key from the client and is not getting it. Also, wrong password may have been entered. Try it again, paying close attention to case sensitivity.
403 Forbidden/Access Denied	Similar to 401; special permission needed to access the site -- a password and/or username if it is a registration issue. Other times you may not have the proper permissions set up on the server or the site's administrator just doesn't want you to be able to access the site.
404 File Not Found	Server cannot find the file you requested. File has either been moved or deleted, or you entered the wrong URL or document name. Look at the URL. If a word looks misspelled, then correct it and try it again. If that doesn't work backtrack by deleting information between each backslash, until you come to a page on that site that isn't a 404. From there you may be able to find the page you're looking for.
408 Request Timeout	Client stopped the request before the server finished retrieving it. A user will either hit the stop button, close the browser, or click on a link before the page loads. Usually occurs when servers are slow or file sizes are large.
500 Internal Error	Couldn't retrieve the HTML document because of server-configuration problems. Contact site administrator.
501 Not Implemented	Web server doesn't support a requested feature.
502 Service Temporarily Overloaded	Server congestion; too many connections; high traffic. Keep trying until the page loads.
503 Service Unavailable	Server busy, site may have moved ,or you lost your dial-up Internet connection.
Connection Refused by Host	Either you do not have permission to access the site or your password is incorrect.
File Contains No Data	Page is there but is not showing anything. Error occurs in the document. Attributed to bad table formatting, or stripped header information.
Bad File Request	Browser may not support the form or other coding you're trying to access.
Failed DNS Lookup	The Domain Name Server can't translate your domain request into a valid Internet address. Server may be busy or down, or incorrect URL was entered.
Host Unavailable	Host server down. Hit reload or go to the site later.
Unable to Locate Host	Host server is down, Internet connection is lost, or URL typed incorrectly.
Network Connection Refused by the Server	The Web server is busy.

Setting the ANT

2009-05-20T21:53:00.001-07:00

First u need to click on the "New " button
and specify the variable name: ANT_HOME
variable value: the location of the
ant folder.

in the user variables section --> click on the new button
and specify the variable name: PATH

variable value: the location of the ant bin folder.

and open command prompt(cmd),and type "ant"
then u can see build failed message.

To set the path for the Cygwin

JAVA_HOME = /cygdrive/c/Progra~1/Java/jdk1.5.0

MQ1(Introduction)

2009-05-18T03:37:00.000-07:00

Queue:

A queue is a container of messages.

Queues are optimized to contain small numbers of messages that flow through the queue before reaching their destination.

By placing a queue between the producer of the message and the consumer, the
Producer can send a message without knowing whether the customer of the message is currently available, and this type of scenario is called as “asynchronous communication”.

With the synchronous communication, where the producer must wait for the customer to
become available and complete processing on the message before being able to continue.

Queue Manager:
The system within a Websphere MQ message queuing infrastructure are called
Queue Manager.

Multiple Queue Manager can run on a single physical server.

The queue managers within the infrastructure are connected with Channels.

Errors........

2009-03-17T00:46:00.000-07:00

http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp

in that click on Message reference

Scripting:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/txml_createserver.html

scripts for automation
http://www.webspheretools.com/sites/webspheretools.nsf/docs!searchview&query=[pagetitle]+CONTAINS+*A,sample,ant,build,file,to,deploy,application*&SearchOrder=1

AIX commands you should not leave home without

http://www.ibm.com/developerworks/aix/library/au-dutta_cmds.html

Interview questions.........

2009-03-16T23:55:00.000-07:00

Increasing the Java virtual machine heap size using scripting

Using Jython:

AdminTask.setJVMMaxHeapSize ('[-interactive]')

Using Jacl:

$AdminTask setJVMMaxHeapSize {-interactive}

Then specify the ServerName,NodeName,ProcessType,Maximum HeapSize

What is a Virtual host ?

Virtual host refer to the capability of most HTTP servers to support multiple logical hosts sharing one IP address on a server.

To delete a service from services.msc
C:\>sc delete SVNService
SVNService -- service name is case sensitive

Creating a server using scripting(Using wsadmin)

2009-03-16T23:05:00.000-07:00

Creating an application server involves a configuration command. Perform the following steps to create a server:

Procedure

Obtain the configuration ID of the object and assign it to the mynode variable, for example:
Using Jacl:
```
set node [$AdminConfig getid /Node:mynode/]
```
Using Jython:
```
node = AdminConfig.getid('/Node:mynode/')
```

There are two ways to create the server using the node that you specified in the first step. Perform one of the following:

Using the AdminTask object:

Using Jacl:

$AdminTask createApplicationServer mynode
{-name test1 –templateName default}

Using Jython:

AdminTask.createApplicationServer(mynode,
['-name', 'test1', '-templateName', 'default'])

Using the AdminConfig object:

Using Jacl:

$AdminConfig create Server $node {{name myserv}
{outputStreamRedirect {{fileName myfile.out}}}}

Using Jython:

AdminConfig.create('Server', node, [['name', 'myserv'],
['outputStreamRedirect', [['fileName', 'myfile.out']]]])

Save the configuration changes.

The wsadmin tool uses the workspace to hold configuration changes. You must save your changes to transfer the updates to the master configuration repository. If a scripting process ends and you have not saved your changes, the changes are discarded.

Procedure

Use the following commands to save the configuration changes:

Using Jacl:
```
$AdminConfig save
```
Using Jython:
```
AdminConfig.save()
```

where:

`$`	is a Jacl operator for substituting a variable name with its value
`AdminConfig`	is an object representing the WebSphere Application Server configuration
`save`	is an AdminConfig command

If you are using interactive mode with the wsadmin tool, you will be prompted to save your changes before they are discarded.

If you are using the -c option with the wsadmin tool, changes are automatically saved. On a Unix operating system, if you invoke a command that includes a dollar sign character ($) using the wsadmin -c option, the command line attempts to substitute a variable. To avoid this problem, escape the dollar sign character with a backslash character (\). For example: wsadmin -c "\$AdminConfig save".

If a scripting process ends and no save has been performed, any configuration changes made since the last save are discarded. If there are multiple clients (scripts or browser clients) updating the configuration at the same time, it is possible that the changes requested by a script may not be saved. If this happens, you will receive an exception and you must make the updates again. If the save fails, the updates will not be saved to the configuration. If it succeeds, all updates are saved. To avoid save failures, you can invoke the save command after every configuration update.

You can use the reset command of the AdminConfig object to undo changes that you made to your configuration since your last save.

4.In a network deployment environment only, synchronize the node.

A node synchronization is necessary in order to propagate configuration changes to the affected node or nodes. By default, this situation occurs periodically, as long as the node can communicate with the deployment manager. You can propagate changes explicitly by performing the following steps:

Procedure

Set the variable for node synchronization.

Using Jacl:

set Sync1 [$AdminControl completeObjectName type=NodeSync,node=myNodeName,*]

Using Jython:

Sync1 = AdminControl.completeObjectName('type=NodeSync,node=myNodeName,*')

where:

`set`	is a Jacl command
`Sync1`	is a variable name
`$`	is a Jacl operator for substituting a variable name with its value
`AdminControl`	is an object that enables the manipulation of MBeans running in a WebSphere Application Server process
`completeObjectName`	is an AdminControl command
`type=NodeSync,node=myNodeName`	is a fragment of the object name. The complete name is returned by this command. This fragment is used to find the matching object name which is the SyncNode object for the myNodeName node, where myNodeName is the name of the node that you use to synchronize configuration changes. For example: `type=Server, name=serv1`. It can be any valid combination of domain and key properties. For example, type, name, cell, node, process, and so on.

Example output:

WebSphere:platform=common,cell=myNetwork,version=5.0,name=node
Sync,mbeanIdentifier=nodeSync,type=NodeSync,node=myBaseNode,
process=nodeagent

Synchronize the node by issuing the following command:

Using Jacl:
```
$AdminControl invoke $Sync1 sync
```
Using Jython:
```
AdminControl.invoke(Sync1, 'sync')
```

where:

`$`	is a Jacl operator for substituting a variable name with its value
`AdminControl`	is an object that enables the manipulation of MBeans that run in a WebSphere Application Server process
`invoke`	is an AdminControl command
`Sync1`	evaluates the ID of the server that is specified in step number 1
`sync`	is an attribute of modify command

Example output:

true

You receive an output value of true, if the synchronization completes.

Configure LDAP

2009-03-16T22:25:00.001-07:00

Install the Lightweight Directory Access Protocol (LDAP) server, and then prepare it to communicate with WebSphere^® Application Server.

Install the LDAP server before WebSphere Application Server.

To prepare the LDAP server to communicate with WebSphere Application Server, complete the following steps:

Install a supported LDAP server.
Populate the LDAP directory with user data.
Note: The mail attribute is required for all users.
Note the values of the following LDAP properties; you must provide these values when you configure WebSphere Application Server:
- Directory Type
- Primary host name
- Port
- Bind distinguished name
- Bind password
- Login properties. For example: mail
- Certificate Mapping
- Certificate Filter, if applicable.
- LDAP Entity types or classes. For example: Group, OrgContainer, PersonAccount, or inetOrgPerson
- Search base
You are now ready to install WebSphere Application Server.

SSL(Secure Socket Layer)

2009-02-19T03:03:00.000-08:00

What is SSL?
SSL is a protocol that provides privacy and integrity between two communicating applications using TCP/IP. The data going back and forth between client and server is encrypted using a symmetric algorithm.

A public-key algorithm (RSA) is used for the exchange of the encryption keys and for digital signatures. Public key cryptography defines an algorithm that uses two keys, each of which may be used to encrypt a message. If one key is used to encrypt a message, the other must be used to decrypt it. This makes it possible to receive secure messages by simply publishing one key (the public key) and keeping the other undisclosed (the private key).

Fig: Client/server authentication

Key file versus trust file

The SSL implementation used by the WebSphere® Application Server stores personal certificates in an SSL key file and signer certificates in a trust file.
A key file contains a collection of certificates, each one of which may be presented during an SSL connection initiation in order to prove identity.

A trust file contains a collection of certificates that are considered trustworthy and against which the presented certificate will be matched during an SSL connection initiation in order to assure identity.
A key store contains the personal certificates that can be used as the identity for the SSL end point referencing the key store. If more than one certificate is present, a certificate alias on the SSL configuration specifies one of the personal certificates. When an SSL connection is made (on either the client or the server side), certificates may be exchanged. The personal certificate referenced by the SSL configuration and stored in the key store is the certificate that will be used.
A personal certificate represents the identity of the end point and contains a public and private key for signing/encrypting data.
A trust store contains the signer certificates which this end point trusts when either making connections (from an outbound end point) or accepting connections (for an inbound end point).
A signer certificate represents a certificate and public key associated with some personal certificate. The purpose of the signer certificate is to verify personal certificates. By accepting the signer certificate into an end point's trust store, you are allowing the owner of the private key to establish connections with this end point; that is, the signer certificate explicitly trusts connections made to or by the owner of the associated personal certificate. The signer certificate is typically made completely public by the owner of the personal certificate, but it's up to the receiving entity to determine if it is a trusted signer prior to adding it to the trust store.

Some of the security features provided by SSL are:

Data encryption to prevent the exposure of sensitive information while data flows across the wire.
Data signing to prevent unauthorized modification of data while data flows across the wire.
Client and server authentication to ensure that you talk to the appropriate person or machine.

JMX Architecture

2009-02-19T02:28:00.001-08:00

Overview of JMX:

JMX is the Java standard for managing an application's resources. The management architecture defined by JMX is divided into three levels:

The bottom level is management instrumentation. Each manageable resource is described by an interface that specifies the attributes it has, the operations it supports, and the notifications it sends. This resource is a managed bean (MBean).
The middle level is the management agent. Each managed process contains a JMX agent that includes an MBean server, which provides a registry and access point for MBeans. Management clients must use the MBean server to access the registered MBeans.
The top level of the architecture is identified, but undefined in the current level of the JMX specification. It is the distributed services level, and its role is to facilitate remote access to JMX agents. This task is accomplished through connectors, which provide a protocol-independent, location-transparent, client-side interface to the MBean server (for example, an RMI connector), or protocol adapters, which provide protocol-specific, server-side access to the MBean server (for example, an HTTP adapter).

Fig: JMX Architecture

Fig: Communication of AdminClient In Appl Server

Cell Structure in Network deployment package

2009-02-14T04:29:00.000-08:00

SSL(Secure Socket Layer)

2009-02-12T03:38:00.000-08:00

ScreenShots and Videos will be in the Next posts

SSL provides secure communications between the Internet web client and the Administrative server.

You must have a digital certificate, keystore file, and truststore file to fully implement SSL communications key store file is used to setup secure MQ channels to the message flow servertruststore: set SSl security for the websphere application server

digital certificates are issued by trusted parties called certificate authoritiesYou can create self signed certificate if you do not have a certificate issued by a CADigital certificate

A digital certificate reveals information about its owner, including their identity. During the initialization of an SSL connection, the server must present its certificate to the client for the client to determine the server identity.

Keystore file

The keystore file is a key database file that contains both public keys and private keys. Public keys are stored as signer certificates while private keys are stored in the personal certificates. The keys are used for a variety of purposes, including authentication and data integrity. You can use both the key management utility (iKeyman) and the keytool utility to create.

Truststore file

A truststore file is a key database file that contains the public keys for target servers. The public key is stored as a signer certificate. If the target uses a self-signed certificate, extract the public certificate from the server keystore file. Add the extracted certificate into the truststore file as a signer certificate. For a commercial certificate authority (CA), the CA root certificate is added. The truststore file can be a more publicly accessible key database file that contains all the trusted certificates.

Start the IBM Key Management application c:\Program Files\IBM\gsk7\bin\gsk7ikm.exeNote: The JAVA_HOME variable must be set. The default location is C:\Program Files\WebSphere\AppServer\java.

For example:

set JAVA_HOME=C:\Program Files\WebSphere\AppServer\java
To Create a key file and self-signed certificate:

Select KeyDatabaseFile > New and enter the followingSelect KeyDatabaseFile > New and enter the following:

Table 1. KeyDatabaseFile values File Name HCNAdminServerKeyFile.jks Location WAS_HOME\etc\
Click OK.

Enter the Key File Password as defined in Table 1 table.
Click OK.

Under Key database content select Personal Certificates.

Click New self-signed.
Enter the following:
Table 2. Administrative server Key file properties Propery Value
Key Label HCN Admin
Common Name Administrative server host name
Example: hcnadmin.ibm.com

Organization Enter an organization name.
Validity Period Enter 7300 days, this is the maximum.
Country or Region Change if default not appropriate.

Create Trust File HCNAdminServerTrustFile.jks using the same values as in step 2. Place HCNAdminServerTrustFile.jks in WAS_HOME\etc.
Start IBM WebSphere Application Server Base V5.1.1 Administration Console.
Click Security > SSL > New Enter the following values:
Table 1. SSL Values Property Value

Alias HCNAdminSSLSettings Key File Name ${USER_INSTALL_ROOT}/etc/HCNAdminServerKeyFile.jks
Key File Password password
Trust File Name ${USER_INSTALL_ROOT}/etc/HCNAdminServerTrustFile.jks
Trust File Password password

${USER_INSTALL_ROOT} expands to the WebSphere Application Server installation path on your machine. It is defined in the IBM WebSphere Application Server Administrative Console.
Click OK
Click Servers > Application Servers > server1 > Web Container > HTTP Transports
Click * next to SSL port 443
Select the ADMIN_SERVER_NAME/HCNAdminSSLSettings.
Click OK > Save > Save.
Restart WebSphere.
Test the Administrative server main page (https://ADMIN_SERVER_NAME/hcn/index.html).

Wsadmin CMD(ADMINCONTROL)

2009-02-12T02:56:00.000-08:00

Example: Identifying running objects

In the WebSphere Application Server, MBeans represent running objects. You can interrogate the MBean server to see the objects it contains. Use the AdminControl object to interact with running MBeans.

Use the queryNames command to see running MBean objects. For example:

$AdminControl queryNames *

This command returns a list of all MBean types. Depending on the server to which your scripting client attaches, this list can contain MBeans that run on different servers:

If the client attaches to a stand-alone WebSphere Application Server, the list contains MBeans that run on that server.
If the client attaches to a node agent, the list contains MBeans that run in the node agent and MBeans that run on all application servers on that node.
If the client attaches to a deployment manager, the list contains MBeans that run in the deployment manager, all of the node agents communicating with that deployment manager, and all application servers on the nodes served by those node agents.

· The list that the queryNames command returns is a string representation of JMX ObjectName objects. For example:

WebSphere:cell=MyCell,name=TraceService,mbeanIdentifier=TraceService,
type=TraceService,node=MyNode,process=server1

This example represents a TraceServer object that runs in server1 on MyNode.

The single queryNames argument represents the ObjectName object for which you are searching. The asterisk ("*") in the example means return all objects, but it is possible to be more specific. As shown in the example, ObjectName has two parts: a domain, and a list of key properties. For MBeans created by the WebSphere Application Server, the domain is WebSphere. If you do not specify a domain when you invoke queryNames, the scripting client assumes the domain is WebSphere. This means that the first example query above is equivalent to:

$AdminControl queryNames WebSphere:*

WebSphere Application Server includes the following key properties for the ObjectName object:
name
type
cell
node
process mbeanIdentifier

These key properties are common. There are other key properties that exist. You can use any of these key properties to narrow the scope of the queryNames command. For example:

$AdminControl queryNames WebSphere:type=Server,node=myNode,*

This example returns a list of all MBeans that represent server objects running the node myNode. The, * at the end of the ObjectName object is a JMX wildcard designation. For example, if you enter the following:

$AdminControl queryNames WebSphere:type=Server,node=myNode

you get an empty list back because the argument to queryNames is not a wildcard. There is no Server MBean running that has exactly these key properties and no others.

If you want to see all the MBeans representing applications running on a particular node, invoke the following example:

$AdminControl queryNames WebSphere:type=Application,node=myNode,*

Example: Turning traces on and off in a server process with the wsadmin tool

The following example turns on tracing in a server process:

Identify the object name for the TraceService MBean running in the process:

$AdminControl completeObjectName type=Server,name=server1,*

Obtain the name of the object and set it to a variable:

set ts [$AdminControl completeObjectName type=TraceService,process=server1,*]

Turn on traces for the server:

$AdminControl setAttribute $ts traceSpecification com.ibm.*=all=enabled

Example: Dumping threads in a server process

Use the AdminControl object to dump the Java threads of a running server.

For example, in Jacl:

set jvm [$AdminControl completeObjectName type=JVM,process=server1,*]

$AdminControl invoke $jvm dumpThreads

This example produces a Java core file. You can use this file for problem determination.

Example: Starting a server using wsadmin

The following example starts an application server with the node specified.

The following command starts server1 in mynode node:

$AdminControl startServer server1 mynode

Example output:

WASX7319I: The serverStartupSyncEnabled attribute is set to false. A startwill be attempted for server "server1" but the configuration information fornode "mynode" may not be current.WASX7262I: Start completed for server "server1" on node "mynode"

The startServer command has several command syntax options. If you have Network Deployment installation, you have to use one of following:

$AdminControl startServer serverName nodeName

$AdminControl startServer serverName nodeName waitTime

If you have an application server base installation, you can use the following syntax in addition to the previous syntax:

$AdminControl startServer serverName

$AdminControl startServer serverName waitTime

Example: Stopping a server using wsadmin

The following example stops an application server with the node specified.

The following command stops server1 in node mynode.

$AdminControl stopServer server1 mynode

Example output:

WASX7337I: Invoked stop for server "server1" Waiting for stop completion.
WASX7264I: Stop completed for server "server1" on node "mynode"

The stop command has serveral command syntaxes.

If you have Network Deployment installation, use the one of following command syntax:

$AdminControl stopServer serverName nodeName

$AdminControl stopServer serverName nodeName immediate

If you have application server base installation, you can use the following syntax, in addition to the previous syntax:

$AdminControl stopServer serverName

$AdminControl stopServer serverName immediate

Example: Querying the server state using the wsadmin tool

The following example queries the server state.

Identify the server and assign it to the server variable.

set server [$AdminControl completeObjectName cell=mycell,node=mynode,name=server1,type=Server,*]

This command returns the server MBean that matches the partial object name string.

Example output:

WebSphere:cell=mycell,name=server1,mbeanIdentifier=server.xml#Server_1,
type=Server,node=mynode,process=server1,processType=ManagedProcess

Query for the state attribute.

$AdminControl getAttribute $server state

The getAttribute command returns the value of a single attribute.

Example output:
STARTED

Example: Starting a listener port using wsadmin

The following example starts a listener port on an application server.

Identify the listener port MBeans for the application server and assign it to the lPorts variable.

set lPorts [$AdminControl queryNames type=ListenerPort,cell=mycell,node=mynode,process=server1,*]

This command returns a list of listener port MBeans.

Example output: WebSphere:cell=mycell,name=ListenerPort,mbeanIdentifier=server.xml#ListenerPort_1,

type=ListenerPort,node=mynode,process=server1

WebSphere:cell=mycell,name=listenerPort,mbeanIdentifier=ListenerPort,type=server.xml#ListenerPort_2,

node=mynode,process=server1

Start the listener port if it is not started with the following example:·

foreach lPort $lPorts

{ set state [$AdminControl getAttribute $lport started]

if {$state == "false"} {

$AdminControl invoke $lPort start

}

This piece of Jacl code loops through the listener port MBeans. For each listener port MBean, get the attribute value for the started attribute. If the attribute value is set to false, then start the listener port by invoking the start operation on the MBean.

Example: Testing data source connection using wsadmin

The following example tests a dataSource, to ensure a connection to the database.

Identify the DataSourceCfgHelper MBean and assign it to the dshelper variable.

set dshelper [$AdminControl queryNames type=DataSourceCfgHelper,process=server1*]

Example output:

WebSphere:cell=mycell,name=DataSourceCfgHelper,mbeanIdentifier=DataSourceCfgHelper,

type=DataSourceCfgHelper,node=mynode,process=server1

Test the connection.

$AdminControl invoke $dshelper testConnectionToDataSource "COM.ibm.db2.jdbc.DB2XADataSource dbuser1 dbpwd1 {{databaseName jtest1}} c:/sqllib/java12/db \"\" \"\""

This example command invokes the testConnectionToDataSource operation on the MBean, passing in the classname, userid, password, database name, JDBC driver class path, language, and country.

Example output:

DSRA8025I: Successfully connected to DataSource

Example: Starting an application using wsadmin

The following example starts an application:

Identify the application manager MBean for the server where the application resides and assign it the appManager variable.

set appManager [$AdminControl queryNames cell=mycell,node=mynode,type=ApplicationManager,process=server1,*]

This command returns the application manager MBean.

Example output:

WebSphere:cell=mycell,name=ApplicationManager,mbeanIdentifier=ApplicationManager,

type=ApplicationManager,node=mynode,process=server1

Start the application.

$AdminControl invoke $appManager startApplication myApplication

This command invokes the startApplication operation on the MBean, passing in the application name to start.

Example: Stopping running applications on a server using wsadmin

The following example stops all running applications on a server:

Identify the application manager MBean for the server where the application resides, and assign it to the appManager variable.

set appManager [$AdminControl queryNames cell=mycell,node=mynode,type=ApplicationManager,process=server1,*]

This command returns the application manager MBean.

Example output: WebSphere:cell=mycell,name=ApplicationManager,mbeanIdentifier=ApplicationManager,

type=ApplicationManager,node=mynode,process=server1

Query the running applications belonging to this server and assign the result to the apps variable.

set apps [$AdminControl queryNames cell=mycell,node=mynode,type=Application,process=server1,*]

This command returns a list of application MBeans.
Example output:

WebSphere:cell=mycell,name=adminconsole,mbeanIdentifier=deployment.xml#ApplicationDeployment_1,

type=Application,node=mynode,Server=server1,process=server1,J2EEName=adminconsole

WebSphere:cell=mycell,name=filetransfer,mbeanIdentifier=deployment.xml#ApplicationDeployment_1,

type=Application,node=mynode,Server=server1,process=server1,J2EEName=filetransfer

Stop all the running applications.

foreach app $apps

{

set appName [$AdminControl getAttribute $app name]

$AdminControl invoke $appManager stopApplication $appName

}

This command stops all the running applications by invoking the stopApplication operation on the MBean, passing in the application name to stop.

Example: Querying application state using wsadmin

The following examples queries for the presence of Application MBean to find out whether the application is running.

$AdminControl completeObjectName type=Application,name=myApplication,*

If myApplication is running, then there should be an MBean created for it. Otherwise, the command returns nothing. If myApplication is running,
the following is the example output:

WebSphere:cell=mycell,name=myApplication,mbeanIdentifier=cells/mycell/applications/myApplication.ear/deployments/myApplication/deployment.xml#ApplicationDeployment_1,
type=Application,node=mynode,Server=dmgr,process=dmgr,J2EEName=myApplication

Example: Updating the Web server plug-in configuration files using wsadmin

This examples regenerates the web serer plugin configuration file.

Identify the web server plugin configuraiton file generator MBean and assign it to the pluginGen variable.

EX:
set pluginGen [$AdminControl completeObjectName type=PluginCfgGenerator,*]

Example output:
WebSphere:cell=pongoNetwork,name=PluginCfgGenerator,
mbeanIdentifier=PluginCfgGenerator,type=PluginCfgGenerator,node=pongoManager,
process=dmgr

Generate the updated plugin configuration file.

EX:

$AdminControl invoke $pluginGen generate "c:/WebSphere/DeploymentManager c:/WebSphere/DeploymentManager/config mycell null null plugin-cfg.xml"

This example command assumes a Windows system install. It invokes the generate operation on the MBean, passing in the install root directory, configuration root directory, cell name, node name, server name, and output file name. To pass in null as the value of an argument, enter null as given in the example. This is provided for operation that allows null as the value of its argument and processes null differently from an empty string. In this example, both node and server are set to null. The generate operation generates plugin configuration for all the nodes and servers resided in the cell. The output file plugin-cfg.xml is created in the config root directory.

You can modify this example command to generate plugin configuration for a particular node or server by specifying the node and server names.

Sample Wsadmin Commands

2009-02-03T00:20:00.000-08:00

wasadmin
----------
wasadmin>$AdminConfig list servers
Wasadmin>$AdminApp install c:\plantsWebsphere
wasadmin>$AdminControl get port
Wasadmin>$Adminconfig save
wasadmin>$AdminControl trace com.ibm.*=all=enable
wasadmin>$AdminControl trace com.ibm.*=all=disable
wasadmin>$AdminControl stopServer server1
Wasadmin>$Admincontrol startServr server1
Listing installed application

wasadmin-ApplicationManagement
------------------------------------
$AdminApp listModules DefaultApplicatons -server
Export an enterprise application to a location of your choice$AdminApp export app1 c:/mystuff/exported.ear
$AdminApp exportDDL app1 c:/mystuff

wasadmin-Application configurations
-----------------------------------
$AdminConfig listTemplates JDBCProvider
$AdminConfig listTemplates JDBCProvider DB2

listing configations objects
--------------------------
$Adminconfig list server $AdminConfig attributes Node

wasadmin-$AdminTask createApplicationServer -interactive

Wsadmin Commands(ADMINAPP)

2009-02-03T00:14:00.000-08:00

Example: Listing the modules in an installed application
Use the AdminApp object listModules command to list the modules in an installed application. For example, invoke the following command interactively in a script, or use wsadmin -c from an operating system command prompt:$AdminApp listModules DefaultApplication -server
This example produces the following output:wsadmin>$AdminApp listModules DefaultApplication -serverDefaultApplication#IncCMP11.jar+META-INF/ejb-jar.xml#WebSphere:cell=mycell,node=mynode,server=myserverDefaultApplication#DefaultWebApplication.war+WEB-INF/web.xml#WebSphere:cell=mycell,node=mynode,server=myserver

Example: Obtaining task information while installing applications
The installInteractive command of the AdminApp object prompts you through a series of tasks when you install an application. You are presented with the title of the task, a description of the task, and the current contents of the task that you can modify.
· Use the install command instead of the installInteractive command, provide updates for each task, but you must provide all of the information on the command line. The task name specifies each task and the information you need to update the task. You can treat the task information as a two-dimensional array of string data. For example:-taskname {{item1a item2a item3a} {item1b item2b item3b} ...}
This example is a linear representation of rows and columns, where {item1a item2a item3a} represents the first row, and each row for the task name has three columns.
The number and type of the columns in this list depend on the task you specify.
· Obtain information about the data needed for each task using the taskInfo command of the AdminApp object. For example, there is a task called MapWebModToVH used to map Web modules to virtual hosts. To specify this task as part of the option string on the command line, enter the following:-MapWebModToVH {{"JavaMail Sample WebApp" mtcomps.war,WEB-INF/web.xml default_host}}
Using the taskInfo command, you can see which of the items you can change for a task. Supply the columns for each row you modify, and the columns that you are not allowed to change must match one of the existing rows. In this case, taskInfo tells you that there are three items in each row, called webModule, uri, and virtualHost and the current column values for every row.
· Obtain help while creating complex installation commands, by using a feature of the installInteractive command. Install the application interactively once and specify the updates that you need. Then look for message WASX7278I in the output log for the wsadmin tool. You can cut and paste the data in this message into a script, and modify it. For example: · WASX7278I: Generated command line: install c:/websphere/appserver/installableapps/jmsample.ear {-BindJndiForEJBNonMessageBinding {{deplmtest.jar MailEJBObject deplmtest.jar,META-INF/ejb-jar.xml ejb/JMSampEJB1 }} -MapResRefToEJB {{deplmtest.jar MailEJBObject deplmtest.jar,META-INF/ejb-jar.xml mail/MailSession9 javax.mail.Session mail/DefaultMailSessionX } {"JavaMail Sample WebApp" mtcomps.war,WEB-INF/web.xml mail/MailSession9 javax.mail.Session mail/DefaultMailSessionY }} -MapWebModToVH {{"JavaMail Sample WebApp" mtcomps.war,WEB-INF/web.xml newhost }} -nopreCompileJSPs -novalidateApp -installed.ear.destination c:/mylocation -distributeApp -nouseMetaDataFromBinary}

Example: Identifying supported tasks and options for an Enterprise Archive file
The AdminApp object install command takes a set of options and tasks. The following examples use the AdminApp object to obtain a list of supported tasks and options for an Enterprise Archive (EAR) file:
· To identify supported options and tasks, use the AdminApp object options command:$AdminApp options c:/MyStuff/myapp1.ear
This command displays a list of tasks and options.
· To identify supported options only, use the following command:$AdminApp options
· To learn more about any of the tasks or options, use the AdminApp object help command. For example:$AdminApp help deployejb

Example: Configuring applications for session management using the wsadmin tool
You can use the AdminApp object to set configurations in an application. Some configuration settings are not available through the AdminApp object. This example uses the AdminConfig object to configure session manager for the application.
· Identify the deployment configuration object for the application and assign it to the deployment variable:set deployment [$AdminConfig getid /Deployment:myApp/]
Example output: myApp(cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#Deployment_1)
· Retrieve the applicaton deployment and assign it to the appDeploy variable:set appDeploy [$AdminConfig showAttribute $deployment deployedObject]
Example output: (cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#ApplicationDeployment_1)
· To obtain a list of attributes you can set for session manager, use the attributes command:$AdminConfig attributes SessionManager
Example output: "accessSessionOnTimeout Boolean""allowSerializedSessionAccess Boolean""context ServiceContext@""defaultCookieSettings Cookie""enable Boolean""enableCookies Boolean""enableProtocolSwitchRewriting Boolean""enableSSLTracking Boolean""enableSecurityIntegration Boolean""enableUrlRewriting Boolean""maxWaitTime Integer""properties Property(TypedProperty)*""sessionDRSPersistence DRSSettings""sessionDatabasePersistence SessionDatabasePersistence""sessionPersistenceMode ENUM(DATABASE, DATA_REPLICATION, NONE)""tuningParams TuningParams"
· Set up the attributes for the session manager:· set attr1 [list enableSecurityIntegration true]· set attr2 [list maxWaitTime 30]· set attr3 [list sessionPersistenceMode NONE]· set attrs [list $attr1 $attr2 $attr3]· set sessionMgr [list sessionManagement $attrs]
This example sets three top level attributes in the session manager. You can modify the example to set other attributes of session manager including the nested attributes in Cookie, DRSSettings, SessionDataPersistence, and TuningParms object types. To list the attributes for those object types, use the attribute command in AdminConfig object.
Example output: sessionManagement {{enableSecurityIntegration true} {maxWaitTime 30} {sessionPersistenceMode NONE}}
· Create the session manager for the application:$AdminConfig create ApplicationConfig $appDeploy [list $sessionMgr]
Example output: (cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#ApplicationConfig_1)
· Save the changes with the following command:$AdminConfig save

Example: Configuring applications for session management in Web modules using the wsadmin tool
You can use the AdminApp object to set configurations in an application. Some configuration settings are not available through the AdminApp object. This example uses the AdminConfig object to configure session manager for Web module in the application.
· Identify the deployment configuration object for the application and assign it to the deployment variable:set deployment [$AdminConfig getid /Deployment:myApp/]
Example output: myApp(cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#Deployment_1)
· Get all the modules in the application and assign it to the modules variable:· set appDeploy [$AdminConfig showAttribute $deployments deployedObject]set modules [lindex [$AdminConfig showAttribute $appDeploy modules] 0]
Example output: (cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#WebModuleDeployment_1)(cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#EJBModuleDeployment_1)(cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#WebModuleDeployment_2)
· To obtain a list of attributes you can set for session manager, use the attributes command.:$AdminConfig attributes SessionManager
Example output: "accessSessionOnTimeout Boolean""allowSerializedSessionAccess Boolean""context ServiceContext@""defaultCookieSettings Cookie""enable Boolean""enableCookies Boolean""enableProtocolSwitchRewriting Boolean""enableSSLTracking Boolean""enableSecurityIntegration Boolean""enableUrlRewriting Boolean""maxWaitTime Integer""properties Property(TypedProperty)*""sessionDRSPersistence DRSSettings""sessionDatabasePersistence SessionDatabasePersistence""sessionPersistenceMode ENUM(DATABASE, DATA_REPLICATION, NONE)""tuningParams TuningParams"
· Set up the attributes for session manager:· set attr1 [list enableSecurityIntegration true]· set attr2 [list maxWaitTime 30]· set attr3 [list sessionPersistenceMode NONE]· set attr4 [list enabled true]· set attrs [list $attr1 $attr2 $attr3 $attr4]set sessionMgr [list sessionManagement $attrs]
This example sets four top level attributes in the session manager. You can modify the example to set other attributes in the seesion manager including the nested attributes in Cookie, DRSSettings, SessionDataPersistence, and TuningParms object types. To list the attributes for those object types, use the attribute command in AdminConfig object.
Example output: sessionManagement {{enableSecurityIntegration true} {maxWaitTime 30} {sessionPersistenceMode NONE} {enabled true}}
· Set up the attributes for Web module:· set nameAttr [list name myWebModuleConfig]· set descAttr [list description "Web Module config post create"]set webAttrs [list $nameAttr $descAttr $sessionMgr]
Example output: {name myWebModuleConfig} {description {Web Module config post create}} {sessionManagement {{enableSecurityIntegration true} {maxWaitTime 30} {sessionPersistenceMode NONE} {enabled true}}}
· Create the session manager for each Web module in the application:· foreach module $modules {· if ([regexp WebModuleDeployment $module] == 1} {· $AdminConfig create WebModuleConfig $module $webAttrs· }· }
You can modify this example to set other attributes of session manager in Web module configuration.
Example output: myWebModuleConfig(cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#WebModuleConfiguration_1)
· Save the changes with the following command:$AdminConfig save

Example: Exporting applications using the wsadmin tool
Exporting applications enables you to back them up and preserve their binding information. You can export your applications before you update installed applications or before you migrate to a different version of the WebSphere Application Server product.
· Export an enterprise application to a location of your choice, for example: $AdminApp export app1 C:/mystuff/exported.ear
where app1 is the name of the application that will be exported and C:/mystuff/exported.ear is the name of the file where the exported application will be stored.
· Export Data Definition Language (DDL) files in the enterprise bean module of an application to a destination directory, for example:$AdminApp exportDDL app1 C:/mystuffwhere app1 is the name of the application whose DDL files will be exported and C:/mystuff is the name of the directory where the DDL files export from the application.

Example: Configuring a shared library for an application
You can use the AdminApp object to set certain configurations in the application. This example uses the AdminConfig object to configure a shared library for an application.
· Identify the shared library and assign it to the library variable.
· To create a new shared library, perform the following steps:
1. Idenitfy the node and assign it to a variable, for example:set node [$AdminConfig getid /Cell:mycell/Node:mynode/]

Example output:mynode(cells/mycell/nodes/mynode:node.xml#Node_1)
2. Create the shared library in the node, for example:set library [$AdminConfig create Library $node {{name mySharedLibrary} {classPath c:/mySharedLibraryClasspath}}]
Example output:MySharedLibrary(cells/mycell/nodes/mynode:libraries.xml#Library_1)
This example creates a new shared library in the node scope. You can modify it to use the cell or server scope.
· To use an existing shared library, issue the following command:set library [$AdminConfig getid /Library:mySharedLibrary/]
Example output:MySharedLibrary(cells/mycell/nodes/mynode:libraries.xml#Library_1)
· Identify the deployment configuration object for the application and assign it to the deployment variable:set deployment [$AdminConfig getid /Deployment:myApp/]

Example output: myApp(cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#Deployment_1)
· Retrieve the applicaton deployment and assign it to the appDeploy variable:set appDeploy [$AdminConfig showAttribute $deployment deployedObject]
Example output: (cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#ApplicationDeployment_1)
· Idenitfy the class loader in the application deployment and assign it to the classLoader variable:set classLoader [$AdminConfig showAttribute $appDeploy classloader]
Example output: (cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#Classloader_1)
· Associate the shared library in the application through the class loader:$AdminConfig create LibraryRef $classLoader {{libraryName MyshareLibrary} {sharedClassloader true}}

Example output: (cells/mycell/applications/myApp.ear/deployments/myApp:deployment.xml#LibraryRef_1)
· Save the changes:$AdminConfig save

Service Integration Bus

2009-02-01T22:33:00.000-08:00

· JMS clients are the programs or components, written in the JavaTM programming language,
that produce and consume messages.
· Messages are the objects that communicate information between JMS clients.
· Administered objects are preconfigured JMS objects created by an administrator for the use of
· Administrative tools allow you to bind destinations and connection factories into a Java
Naming and Directory InterfaceTM (JNDI) API namespace. A JMS client can then look up the
administered objects in the namespace and then establish a logical connection to the same
objects through the JMS provider. clients. The two kinds of administered objects are
destinations and connection factories

Point-to-Point Messaging Domain:

A point-to-point (PTP) product or application is built around the concept of message queues, senders, and receivers. Each message is addressed to a specific queue, and receiving clients extract messages from the queue(s) established to hold their messages. Queues retain all messages sent to them until the messages are consumed or until the messages expire

Publish/Subscribe Messaging Domain:

In a publish/subscribe (pub/sub) product or application, clients address messages to a topic. Publishers and subscribers are generally anonymous and may dynamically publish or subscribe to the content hierarchy. The system takes care of distributing the messages arriving from a topic's multiple publishers to its multiple subscribers. Topics retain messages only as long as it takes to distribute them to current subscribers.

connection factory:

A connection factory is the object a client uses to create a connection with a provider.

Destination:
A destination is the object a client uses to specify the target of messages it produces and the source of messages it consumes. In the PTP messaging domain, destinations are called queues,

Session:
A session is a single-threaded context for producing and consuming messages. You use sessions to create message producers, message consumers, and messages. Sessions serialize the execution of message listeners;

Message producer
A message producer is an object created by a session and is used for sending messages to a destination. The PTP form of a message producer implements the QueueSender interface. The pub/sub form implements the TopicPublisher interface.

Message consumer:

A message consumer is an object created by a session and is used for receiving messages sent to a destination. A message consumer allows a JMS client to register interest in a destination with a JMS provider. The JMS provider manages the delivery of messages from a destination to the registered consumers of the destination.
The PTP form of message consumer implements the QueueReceiver interface. The pub/sub form implements the TopicSubscriber interface.

Message listener:

A message listener is an object that acts as an asynchronous event handler for messages. This object implements the MessageListener interface, which contains one method, onMessage. In the onMessage method, you define the actions to be taken when a message arrives.
You register the message listener with a specific QueueReceiver or TopicSubscriber by using the setMessageListener method. For example, if you define a class named TopicListener that implements the MessageListener interface,

Messages:
The ultimate purpose of a JMS application is to produce and to consume messages that can then be used by other software applications. JMS messages have a basic format that is simple but highly flexible, allowing you to create messages that match formats used by non-JMS applications on heterogeneous platforms.

A JMS message has three parts:
· A header
· Properties (optional)
· A body (optional)

Message Headers:
A JMS message header contains a number of predefined fields that contain values that both clients and providers use to identify and to route messages. (Table: lists the JMS message header fields and indicates how their values are set.) For example, every message has a unique identifier, represented in the header field JMSMessageID. The value of another header field, JMSDestination, represents the queue or the topic to which the message is sent. Other fields include a timestamp and a priority level.

Message Bodies:
The JMS API defines five message body formats, also called message types, which allow you to send and to receive data in many different forms and provide compatibility with existing messaging formats.

How to Create Cluster

2009-01-31T22:55:00.000-08:00

Configure Logs(Video)

2009-01-28T06:22:00.000-08:00

change log detail levels(Video)

2009-01-28T06:05:00.000-08:00

Http Error and NCSE(Video)

2009-01-28T05:56:00.000-08:00

IBM Threads(Video)

2009-01-28T05:26:00.000-08:00

Federation

2009-01-27T02:22:00.000-08:00

Dmgr:

Application Server Profile:

After Federating………………..
First: Dmgr

localhostCellManager01

C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\localhostCell01\nodes

localhostNode01

Appsrv01

localhostCellManager01

localhostNode01

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\localhostCell01\nodes

Architecture

2009-01-26T02:49:00.000-08:00