Posts

Installation procedure for WebSphere Liberty Profile.

Topic : Installation procedure for WebSphere Liberty Profile. Procedure: Install a Java SDK. If you already have a Java 6 or Java 7 SDK then you can skip this step.   To install a Java 7 SDK ,simply unzip the file   ibm-java-sdk-70-win-i386.zip . Install the WebSphere Application Server Developer Tools for Eclipse V8.5.5. From the command prompt type   java -jar WDT-8.5.5-win.jar   and follow the prompts to install Eclipse 4.2.2 and the developer tools to the directory of your choice. Install the IBM WebSphere Application Server V8.5.5 Liberty Profile. From the   command prompt   type   java -jar wlp-developers-runtime-8.5.5.0.jar and follow the prompts to install the Liberty profile to a directory of your choice. If you want to use JMS, Web services or MongoDB you should also install the extended programming models. This can be done by running   java -jar wlp-developers-extended-8.5.5.0.jar   and following the prompts. Optional: ...

Programming Models Supported in Liberty Profile

Topic:  Programming Models Supported: Java Servlet 3.0 JavaServer Faces (JSF) 2.0 JavaServer Pages (JSP) 2.2 Java Expression Language 2.2 Standard Tag Library for JavaServer Pages (JSTL) 1.2 Bean Validation 1.0 Java Persistence API (JPA) 2.0 Java Transaction API (JTA) 1.1 Java Database Connectivity (JDBC) 4.0 Java API for RESTful Web Services (JAX-RS) 1.1 In WAS 8.5.5 version  it supports the below Contexts and Dependency Injection for Java (Web Beans 1.0) Dependency Injection for Java 1.0 Enterprise JavaBeans 3.1 (includes Interceptors 1.1) - EJB Lite subset In other editions, such as WebSphere Application Server and WebSphere Application Server Network Deployment, the Liberty profile supports the following technologies in addition to those contained in Liberty Core: Java API for XML-Based Web Services (JAX-WS) 2.2 Java Architecture for XML Binding (JAXB) 2.2 SOAP with Attachments API for Java (SAAJ) 1.3 Java Message Service...

WAS Liberty Profile

Topic : What is liberty Profile in WAS? and its features Explanation: The Liberty profile is a lightweight, simple to use, yet powerful, application server for lightweight web production server , OSGi, and mobile applications. Extremely fast restart times coupled with its small size and ease of use make the Liberty profile a great option for building web apps that do not require the full Java EE environment of traditional enterprise application server profiles. Features: 1.Simple Configuration (only one simple config file server.xml for all configurations) 2. Rapid Server Restart (less then 5 seconds) 3. It supports integrated  tools like(Maven/Eclipse). 4. dynamically extendible. 5. Supports light weight Cluster Management. 6. Fidelity to traditional WAS.  7. Web Profile Certified. 8. Memory foot print is < 60 MB 9. Profile is dynamic (switch parts of the server on and off with out restart) 10. Be installed and managed separately from a...

MQ: QMGR is not started due to Circular log deletion

Issue: Circular Log is deleted by the user by mistake which causes the queue manager not able to start Solution: Restore the log file from back up and start the qmgr. it should work WorkAround: If there is no backup the workaround to get the queue manager running is 1. backup /var/mqm/log/<ORI_QMGR> 2. create the dummy qmgr with the similar log description as in the <ORI_QMGR>for this refer the /var/mqm/qmgrs/<ORI_QMGR>/qm.ini 3. crtmqm <DUMMY_QMGR> -lp 3 -ls 2 -lp 1024 -lc 4. copy /var/mqm/log/<DUMMY_QMGR>/active and amqhlct.ifh to /var/mqm/log/<ORI_QMGR>        cp  /var/mqm/log/<DUMMY_QMGR>/* /var/mqm/log/<ORI_QMGR>/ 5. ensure all semphores for <ORI_DMGR> are cleared 6.strmqm <ORI_QMGR> 7. you can remove <DUMMY_QMGR> if not required.

MQ: AMQ8041 Error Unable to restart the QueueManager

Issue: AMQ8041 Error Unable to restart the QueueManager Solution :  Remove the MQ semaphores by using this command /usr/mqm/bin/amqiclen -m <QM_NAME> -v -h -x -F

WebSphere: A composition unit with name already exists.

Issue:   A composition unit with name <APP_NAME> already exists.Select a different application Name Solution: Sometimes this error will come even after deleting the application from WAS. Remove the application references from the below paths. <WAS_INSTALLATION_PATH>/Dmgr01/config/cells/<CELL_NAME>/blas/ <WAS_INSTALLATION_PATH>/Dmgr01/config/cells/<CELL_NAME>/cus/ removing the application references from the above paths will resolve the problem

WebSphere : Set the default Profile in WAS

Topic : Set the default profile when multiple dmgr profiles are there. Go to <WAS_INSTALLATION_PATH>/properties/fsdb/_was_profile_default modify the default.sh file to point to the required profile. This default profile setting can be useful when you have multiple number of profiles and want to deploy the application in particular profile through scripts.  <WAS_INSTALLATION_PATH> can be like /opt/ibm/WebSphere/AppServer

WebSphere MQ: JNDI Error in EAI JMS Tranport:'Exception:javax.naming.NameNotFoundException

Issue :  JNDI Error in EAI JMS Tranport:'Exception:javax.naming.NameNotFoundException:ReceiveGMSReferral;Message:ReceiveGMSReferral' Version :  WebSphere MQ 530.10 Solution :  Go to <MQ-INSTALL-DIRECTORY>/java/bin ./JMSAdmin InitCtx>define q(ReceiveGMSReferral) QUEUE(<QUEUE-NAME>) QMANAGER(<QMGR-NAME>) dis q(*) End to test the JMS connection with queue manager: ./IVTRun -nojndi -client -m <QMGR-NAME> -host <HOST-NAME> -port <LISTENER-PORT> -channel <CHANNEL-NAME> This confirms the connection works fine

Solaris Volume Manager(SVM): Setup with an example

Note: Procedure explained here based on one example. Do not execute exact commands File System layout before do any change: Filesystem             size   used  avail capacity  Mounted on /dev/dsk/c1t0d0s0      2.0G   104M   1.8G     6%    / /dev/dsk/c1t0d0s5      5.9G   1.8G   4.0G    32%    /usr /proc                    0K     0K     0K     0%    /proc mnttab                   0K     0K     0K     0%    /etc/m...

Kernel upgrade for Linux(OEL/RHEL) using up2date

Given procedure helpful to upgrade the Linux(OEL/RHEL) kernel using up2date command Required Backups: 1.       Ensure full system backup 2.       Take the backup of the /etc/grub.conf file.     #cp /etc/grub.conf /etc/grub.conf.bak Procedure to upgrade kernel: 1. register the system to the ULN(Unbreakable Linux Network) with you Linux support CSI      #Up2date –register 2.       Go to linux.oracle.com and subscribe the server to the RHEL/OEL 5.x/6.x patch channel which ever is required Eg: - go to the "Systems" tab and click on your server - Click on "Manage Supscriptions" and select "Enteprise Linux 5 Update 4 Patch ( ARCH, eg: i386 )" and "Enteprise Linux 5 Update 4 installation media copy ( ARCH )", remove "Enterprise Linux 5 Latest ( ARCH )" - click on "Save Subscriptions" 3.       Get the kernel package; you can dow...