First of all we have to stop all processes that are running in your environment.
We can see with this command all processes stopped or not
#ps -ef | grep java
#ps -ef | grep http

Here below I explained in the pdf document

Usually we confuse to make rollback or uninstall  Websphere Interim fixes , and searching on the internet finding  document, therefore I have prepared a pdf document how to uninstall WAS Interim fixes.

 

I don’t post long time any article, but during the this time I have lived a lot of things, Perhaps one day, I can share  what happened during this time, usually we want to use graphic screen but everytime we can not find possibility, Now  I will share with you how to using  imcl command  to rollback  WebSphere  fix pack. I have prepared a document below, I hope it may be usefull for you.

 

WebSphere Application Server is available in multiple packaging options. Each
packaging option includes the application server component and an appropriate combination
of complementary products, for example, IBM HTTP Server, IBM Assembly and Deploy Tools
for WebSphere Administration, Edge components, and other products. Although these
options share a common foundation, each provides unique benefits to meet the needs of
applications and the infrastructure that supports them.

Below images shows  Websphere packaging options.

 

 

Source:WebSphere Application Server V8.5 Administration and Configuration Guide for Liberty Profile P.4 sg248170

Each Liberty profile is configured using a server.xml configuration  file.   You can edit this file in text editor. in this file we will add  location of ojdbc6.jar and properties of datasource.

Location of server.xml file in my example  D:\IBM\WebSphere\Liberty\usr\servers\libserver

Here below my sample configuration.

<dataSource id=”TEST” jndiName=”jdbc/MyDataSource”>
<jdbcDriver libraryRef=”OracleLib”/>
<properties.oracle URL=”jdbc:oracle:thin:@dbhostname:1521:SID” password=”” user=”testuser”/>
</dataSource>

<library id=”OracleLib”>
<fileset dir=”D:\IBM\WebSphere\Liberty\lib” includes=”ojdbc6.jar”/>
</library>

The Liberty profile configuration , including   any password , is kept in text files.  To improve security, consider encoding the password using  securityUtility script  supplied  with the Liberty Profile.
You can use  this utility at any time to encodes to passwords. For example to encode the password “Passw0rd” in xor format, run the following command :

D:\IBM\WebSphere\Liberty\bin\securityUtility.bat  encode Passw0rd

Output : {xor}Dz4sLChvLTs=

The web server plug-in uses an XML configuration file to determine whether a request is for the web server or the application server. When a request reaches the web server, the URL is compared to the URLs managed by the plug-in. If a match is found, the plug-in configuration file contains the information needed to forward that request to the web container using the web container inbound transport chain.

The plug-in configuration file is generated using the WebSphere administrative tools. Each time you make a change to the WebSphere Application Server configuration that affects how requests are routed from a web server to the application server, you need to regenerate and  propagate the plug-in configuration file to the web server. You can propagate the file manually  or configure the propagation to be done  automatically

Reference :  WebSphere Application Server V8.5 Administration and Configuration Guide

IBM released new Websphere 8.5.5. I don’t think big difference between Websphere 8.5 and Websphere 8.5.5. Only has a little enhancement.

WebSphere Application Server Network Deployment V8.5.5 offer :

• World-class clustering and high-availability management to help eliminate the cost of system downtime
• Intelligent Management capabilities that deliver breakthrough levels of resiliency and reliability, including capabilities formerly available from WebSphere Virtual Enterprise
• Enterprise-level Java batch capabilities, such as parallel job processing, job checkpoints and restart, workload management, and shared OLTP and batch processing
• Edge components, which offer sophisticated load balancing, caching, and centralized security for enhanced performance at the edge of the network
• Advanced centralized management and administration to make management of more complex environments less time-consuming and resource-consuming
• Enterprise-proven, leading security capabilities to safeguard your business
• Industry-leading performance that maximizes business competitiveness while minimizing total cost of ownership (TCO)
• Liberty profile collective cluster admin
• Distributed caching through WebSphere eXtreme Scale

More information about to other editons (Express,developer etc.)

http://www-01.ibm.com/common/ssi/rep_ca/7/897/ENUS213-137/index.html

If you’re trying to delete a very large number of files at one time (for example 100.000+), you will probably run into this error:

#/bin/rm: Argument list too long.

Because There is a relatively small buffer of memory allocated to storing this list of arguments. if it is filled up, the shell will not execute the program.

Deleting files created before  15 days ago

for i in `find /home/log -type f -name “*.txt” -mtime +15 -exec ls -l {} \; | awk ‘$5 > 0 {print $9}’`; do rm -rf   $i ; done

Moving file created vefore 15 days ago

for i in `find /home/log -type f -name “*.txt” -mtime +15 -exec ls -l {} \; | awk ‘$5 > 0 {print $9}’`; do mv  $i /home/backup/log/; done

The default execution stops we stop the server process. While it is a good idea stop the server process to prevent changes from being made while the backup is running, this action is not necessary. If you run the backupConfig script using the -nostop option, the server process will not be stopped, in which case you’d want to be sure that no configuration changes were being made while the backup was running.

./backupConfig.sh -nostop

Firtly we have start wsadmin

#/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/wsadmin.sh -lang jython -username wasadmin -password xxxxxx

wsadmin>AdminTask.binaryAuditLogReader(‘-interactive’)

wsadmin>AdminTask.binaryAuditLogReader(‘-interactive’) Binary Audit Log Reader

Binary Audit Log Reader Command

*File name of the Binary Audit log (fileName): /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/BinaryAudit_

was85test1Cell01_was85test1CellManager01_dmgr.log

Report mode selection (reportMode): basic

Event(s) filter (eventFilter): (blank)

Outcome(s) filter (outcomeFilter): (blank)

Sequence filter (sequenceFilter): (blank)

Timestamp filter (timeStampFilter): (blank)

Key Store Password (keyStorePassword): (blank)

Output HTML file location  (outputLocation): /home/wasadmin/sampleAuditReport.html

Data points to report (dataPoints): (blank)

Binary Audit Log Reader

F (Finish) C (Cancel)

Select [F, C]: [F]  F

WASX7278I: Generated command line: AdminTask.binaryAuditLogReader(‘[-fileName /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/BinaryAudit_

was85test1Cell01_was85test1CellManager01_dmgr.log -reportMode basic -outputLocation /home/wasadmin/sampleAuditReport.html ]’) ‘true’

wsadmin>