http://www-01.ibm.com/support/docview.wss?uid=swg21283554
http://www.ibm.com/developerworks/aix/library/au-analyze_aix/
The nmon tool is designed for AIX and Linux performance specialists to use for monitoring and analyzing performance data, including:
Also included is a new tool to generate graphs from the nmon output and create .gif files that can be displayed on a Web site.
1. Use scripts in websphere or process server scriptLibraries folder
/opt/ibm/WebSphere/ProcServer/scriptLibraries
2. Use the wsadmin script with jython (python running on java) or jacl option
The following steps are for using jacl option and above link will show the syntax for using jython instead (for jython you have to use wsadmin.sh –lang jython and issue AdminApp.install command):
Steps:
- copy the ear file to some staging directory ex: /home/wpsadmin
- cd to profile root bin. ex: /opt/ibm/WebSphere/ProcServer/profiles/
DEV01/bin
- run wsadmin as below
./wsadmin.sh (or wsadmin.sh –lang jython or wsadmin.sh -lang jython -user wsadmin -password wsadmin)
- use the jacle script to install the app using default values (when
there is only one cell/node/server)
$AdminApp install "/home/wpsadmin/HelloWorldProcessApp.ear" or AdminApp.install('/home/wpsadmin/HelloWorldProcessApp.ear') for jython.
for a specific server use the following
$AdminApp install "/home/wpsadmin/HelloWorldProcessApp.ear" {-node
dvlpsij01Node01 -cell dvlpsij01Node01Cell -server server1} or
AdminApp.install("/home/wpsadmin/HelloWorldProcessApp.ear" {-node
dvlpsij01Node01 -cell dvlpsij01Node01Cell -server server1}
for a specific cluster use the following
$AdminApp install "/home/wpsadmin/HelloWorldProcessApp.ear" {-cluster
clustername}
- uninstall the app from default server (assuming there is only one
server). pl note there is no .ear at the end of the app name, just the
name.
$AdminApp uninstall HelloWorldProcessApp
for a specific server use the following
$AdminApp uninstall HelloWorldProcessApp {-node dvlpsij01Node01 -cell
dvlpsij01Node01Cell -server server1}
for a specific cluster use the following
$AdminApp uninstall HelloWorldProcessApp {-cluster clustername}
1. Use scripts in websphere or process server scriptLibraries folder
/opt/ibm/WebSphere/ProcServer/scriptLibraries
2. Use the wsadmin script with jython (python running on java) or jacl option
the following steps are for using jacl option and above link will show the syntax for using jython instead:
Steps:
- copy the ear file to some staging directory ex: /home/wpsadmin
- cd to profile root bin. ex: /opt/ibm/WebSphere/ProcServer/profiles/
DEV01/bin
- run wsadmin as below
./wsadmin.sh
- use the jacle script to install the app using default values (when
there is only one cell/node/server)
$AdminApp install "/home/wpsadmin/HelloWorldProcessApp.ear"
for a specific server use the following
$AdminApp install "/home/wpsadmin/HelloWorldProcessApp.ear" {-node
dvlpsij01Node01 -cell dvlpsij01Node01Cell -server server1}
for a specific cluster use the following
$AdminApp install "/home/wpsadmin/HelloWorldProcessApp.ear" {-cluster
clustername}
- uninstall the app from default server (assuming there is only one
server). pl note there is no .ear at the end of the app name, just the
name.
$AdminApp uninstall HelloWorldProcessApp
for a specific server use the following
$AdminApp uninstall HelloWorldProcessApp {-node dvlpsij01Node01 -cell
dvlpsij01Node01Cell -server server1}
for a specific cluster use the following
$AdminApp uninstall HelloWorldProcessApp {-cluster clustername}
These sample jacl and Jython scripts let you automate common administation tasks and configure security in WebSphere Application Server Versions 5, 6 and 6.1. Download them and run them as is, or modify them to suit your environment.
http://www.ibm.com/developerworks/websphere/library/samples/SampleScripts.html
#!/bin/ksh or #!/usr/bin/ksh is added as the first line for any unix or linux scripts. Why?
Originally, we only had one shell on unix. When you asked to run a command, the shell would attempt to invoke one of the exec() system calls on it. It the command was an executable, the exec would succeed and the command would run. If the exec() failed, the shell would not give up, instead it would try to interpet the command file as if it were a shell script.
Then unix got more shells and the situation became confused. Most folks would write scripts in one shell and type commands in another. And each shell had differing rules for feeding scripts to an interpreter. This is when the "#! /" trick was invented. The idea was to let the kernel's exec() system calls succeed with shell scripts. When the kernel tries to exec() a file, it looks at the first 4 bytes which represent an integer called a magic number. This tells the kernel if it should try to run the file or not. So "#! /" was added to magic numbers that the kernel knows and it was extended to actually be able to run shell scripts by itself. But some people could not type "#! /", they kept leaving the space out. So the kernel was exended a bit again to allow "#!/" to work as a special 3 byte magic number.| Question |
| How can I share my assets (Java™ binaries, XML schemas, and WSDL definitions) by-reference between Service Component Architecture (SCA) modules in the WebSphere Process Server run-time environment? |
|
|
Cause In WebSphere Integration Developer, the default sharing behavior for assets is share-by-copy. That is, at build time, SCA library projects, containing shared SCA module assets become .jar files that are included in each SCA module application enterprise archive (.ear) file. Shared Java library artifacts are also included in each SCA module application .ear file.
Depending on the size of the libraries, number of assets, and number of deployed modules, the share-by-copy module can result in a large memory footprint. Sharing these assets by-reference can reduce this memory footprint.
Answer
http://www-01.ibm.com/support/docview.wss?rs=2307&uid=swg21322617
Reference Link:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/txml_deployapp.html
Steps:
- copy the ear file to some staging directory ex: /home/wpsadmin
- cd to profile root bin. ex: /opt/ibm/WebSphere/ProcServer/profiles/DEV01/bin
- run wsadmin as below
./wsadmin.sh
- use the jacle script to install the app using default values (when there is only one cell/node/server)
$AdminApp install "/home/wpsadmin/HelloWorldProcessApp.ear"
for a specific server use the following
$AdminApp install "/home/wpsadmin/HelloWorldProcessApp.ear" {-node dvlpsij01Node01 -cell dvlpsij01Node01Cell -server server1}
for a specific cluster use the following
$AdminApp install "/home/wpsadmin/HelloWorldProcessApp.ear" {-cluster clustername}
- uninstall the app from default server (assuming there is only one server). pl note there is no .ear at the end of the app name, just the name.
$AdminApp uninstall HelloWorldProcessApp
for a specific server use the following
$AdminApp uninstall HelloWorldProcessApp {-node dvlpsij01Node01 -cell dvlpsij01Node01Cell -server server1}
for a specific cluster use the following
$AdminApp uninstall HelloWorldProcessApp {-cluster clustername}
Because the integrity of your processing environment is at stake, questions about security must be answered as quickly as possible. To that end, this article provides quick, direct answers to some of the most frequently asked questions about IBM® WebSphere® Application Server security.
http://www.ibm.com/developerworks/websphere/techjournal/1003_botzum/1003_botz...
http://www-01.ibm.com/support/docview.wss?uid=swg21140014
http://www.ardenagopyan.com/downloads/tutorials/WPS-SPNEGO-TAI.pdf
http://www.ibm.com/developerworks/web/library/wa-singlesign/
http://www.ibm.com/developerworks/websphere/library/techarticles/0211_konduru/konduru.html
http://www.mainsoft.com/static/solutions/pdfs/FederatingSharepointSites_WP.pdf
http://www-01.ibm.com/support/docview.wss?uid=swg21198736
http://www16.boulder.ibm.com/pseries/en_US/aixbman/security/kerberos_intro.htm
http://www.ibm.com/developerworks/java/library/j-gss-sso/
http://www.ibm.com/developerworks/ibm/library/it-0101art2/
http://www.ibm.com/developerworks/websphere/zones/portal/proddoc.html
http://www.ibm.com/developerworks/websphere/library/techarticles/0604_lamb/0604_lamb.html
