Changing the console session expiration WebSphere Application Server 8.5.5

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test1was855Cell01/applications/isclite.ear/deployments/isclite

In above directory , modify deployment.xml by setting  invalidationTimeout parameter to the value you want and  restart the Deployment Manager

Or  use scripts  below :

http://lnubla.wordpress.com/2014/03/12/changing-the-console-session-expiration/

http://www-01.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.multiplatform.doc/info/ae/isc/cons_sessionto.html?lang=en

Sharing files and folders with NFS between Linux machines RHEL 6

10.150.3.70 ve 10.150.3.71 WAS test sunucuları



Her iki sunucuda da :

Yazılım kullanıcılarını tanımlamak için wasusers grubu oluşturuldu. groupadd wasusers
WAS yöneticisi için wasadmin kullanıcısı ve grubu zaten oluşturulmuştu.
/home dizininin altına wasadmin kullanıcısına ve grubuna bütün yetkiler verildi.
setfacl -R -m u:wasadmin:rwx /home
setfacl -R -m g:wasadmin:rwx /home
mkdir /home/nfsshare
chown -R wasadmin:wasadmin nfsshare/
setfacl -R -m g:wasusers:rwx nfsshare





http://www.tecmint.com/how-to-setup-nfs-server-in-linux/

NFS Server : 10.150.3.70
NFS Client : 10.150.3.71

Setting Up the NFS Server:

nfs paylaşımı için NFS server olarak kullanılacak makine de (10.150.3.70):
service nfs start
chkconfig nfs on

For sharing a directory with NFS, we need to make an entry in “/etc/exports” configuration file.
Here I’ll be creating a new directory named “nfsshare” in “/home” partition to share with client server, you can also share an already existing directory with NFS.

vi /etc/exports
/home/nfsshare   10.150.3.71(rw,sync,no_root_squash)

there is a directory in /home partition named “nfsshare” is being shared with client IP “10.150.3.71” with read and write (rw) privilege

service nfs stop
service nfs start



Setting Up the NFS Client :

After configuring the NFS server, we need to mount that shared directory or partition in the client server.
Now at the NFS client end, we need to mount that directory in our server to access it locally.
To do so, first we need to find out that shares available on the remote server or NFS Server.

[root@test2was855 /]# showmount -e 10.150.3.70
Export list for 10.150.3.70:
/home/nfsshare 10.150.3.71
[root@test2was855 /]#


To mount nfsshare ;

[root@test2was855 home]# mount -t nfs 10.150.3.70:/home/nfsshare /home/nfsshare
[root@test2was855 home]#

Verify nfsshare directory is mounted ;

[root@test2was855 nfsshare]# mount | grep nfs
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
10.150.3.70:/home/nfsshare on /home/nfsshare type nfs (rw,vers=4,addr=10.150.3.70,clientaddr=10.150.3.71)


The above mount command mounted the nfs shared directory on to nfs client temporarily,
to mount an NFS directory permanently on your system across the reboots, we need to make an entry in “/etc/fstab“.

vi /etc/fstab

Add the following new line as shown below.

10.150.3.70:/home/nfsshare /home/nfsshare  nfs defaults 0 0

If you want to unmount that shared directory from your server after you are done with the file sharing,
you can simply unmount that particular directory with “umount” command. See this example below.

[root@test2was855 nfsshare]# df -h -F nfs
Filesystem                  Size  Used Avail Use% Mounted on
10.150.3.70:/home/nfsshare   24G   14G  8.4G  63% /home/nfsshare
[root@test2was855 nfsshare]#

root@nfsclient ~]# umount /home/nfsshare

After umount check again :
[root@test2was855 nfsshare]# df -h -F nfs

Cloning Websphere Application Server ND Environment v8.5.5

http://www.experts-exchange.com/Software/Server_Software/Application_Servers/Java/Q_26252134.html

I have another simple way to clone the websphere env if you want to use same cellname and nodename.

1) installed same websphere version includin fixpack on new machine 

Note you have to  make sure to use same install path for example

if you have old machine install path c:/webspherev6.1/appserver

Then you need give same install path on new machine c:/webspherev6.1/appserver

2) create dmgr and nodeprofile on new machine

3) you need to stop the dmgr, nodeagent and all application server on old machine

4) You can tar/zip up the complete dmgr profile dir and node profile from old machine and untar/unzip on new machine under c:/webspherev6.1/appserver/profiles  and change the hostname entries in the websphere configuration and 

Use follow link for changing hostname ( chaper 2)  WebSphere Application Server V6.0 best practices for configuration changes

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

5) one new dmgr is up and manually sync the node with dmgr using syncnode command.

from node bin syncnode newdmgrhostname dmgrsoapport -username user -password password


6)  once sync went fine start the nodeagent and make sure sync status shows correctly on dmgr console and then start all application server from dmgrconsole

Start components as needed Websphere Application Server ND 8.5.5

Select this property if you want the server components started as they are needed by an application that is running on this server.When this property is selected, server components are dynamically started as they are needed. When this property is not selected, all of the server components are started during the server startup process. Therefore, selecting this option can improve startup time, and reduce the memory footprint of the server, because fewer components are started during the startup process.Starting components as they are needed is most effective if all of the applications, that are deployed on the server, are of the same type. For example, using this option works better if all of your applications are Web applications that use servlets, and JavaServer Pages (JSP). This option works less effectively if your applications use servlets, JSPs and Enterprise JavaBeans (EJB).


You can improve system performance if you configure some of your application servers, such that each of their components are dynamically started as they are needed, instead of letting all of these components automatically start when the server starts. Selecting this option can improve server startup time, and reduce the memory footprint. Starting components as they are needed is most effective if all of the applications that are deployed on the application server are of the same type. For example, using this option works better if all of your applications are web applications that use servlets, and JavaServer Pages (JSP). This option works less effectively if your applications use servlets, JSPs and Enterprise JavaBeans (EJB)

EJB , Servlets , JSF and JSP

A typical enterprise Java application may contain several Java classes of different types, such as EJBs, servlets, JavaServer Faces (JSF) classes, as well as static files such as JSPs and HTML files. EJBs run in the EJB container whereas web applications such as servlets and JSF managed beans run in the web container.

Parallel Start in Websphere Application Server ND 7/8/8.5

Select this field to start the server on multiple threads. This might shorten the startup time.
Specifies that you want the server components, services, and applications to start in parallel rather than sequentially.The default setting for this option is true, which indicates that when the server starts, the server components, services, and applications start on multiple threads. Setting this option to false specifies that when the server starts, the server components, services, and applications start on a single thread, which might lengthen start-up time.

The order in which the applications start depends on the weights that you assign to them. Applications that have the same weight start in parallel.To set the weight of an application, in the administrative console, click Applications > Application Types > WebSphere enterprise applications > application_name > Startup behavior, and then specify an appropriate value in the Startup order field. The more important an application is, the lower the startup order value should be. For example, you might specify a startup order value of 1 for your most important application, and a value of 2 for the next most important application. You might then specify a startup order of 3 for the next four applications because you want all four of those applications to start in parallel.

Start components as needed ;

Select this property if you want the server components started as they are needed by an application that is running on this server.
When this property is selected, server components are dynamically started as they are needed. When this property is not selected, all of the server components are started during the server startup process. Therefore, selecting this option can improve startup time, and reduce the memory footprint of the server, because fewer components are started during the startup process.
Starting components as they are needed is most effective if all of the applications, that are deployed on the server, are of the same type. For example, using this option works better if all of your applications are Web applications that use servlets, and JavaServer Pages (JSP). This option works less effectively if your applications use servlets, JSPs and Enterprise JavaBeans (EJB).