Skip to main content

Deploy war on weblogic server by weblogic console

In this post we will see how to deploy a war on weblogic by using weblogic console.

1)First start the admin server of your weblogic server  for this browse to the path of domain of your weblogic server .it will be some what like


here you will get all the domains created
so in


you will get  startWebLogic.cmd or
depending on your OS Just run it and you will see a cmd console

2)Now If your weblogic server is started succssfully it will display running in console

3) After starting weblogic server succssfully . Open the weblogic console from the below linkhttp://localhost:7001/console

where localhost is the machine address on which weblogic server is running.And 7001 is the port on which weblogic admin server is running.
4)Now it will ask for username or password just enter your domain username and password
and it will redirect to a screen.

5) Now click on deployment on the left side pannel and you will se a screen asking to browse
the war file.

6)Just browse to the war file want to deploy on weblogic server.

7) Now click next and it will ask to chose the server on which you want to deploy the war from
here you can select Admin server or any other managed server(If you chose other managed server
then you have to start it seprately from nodemanager or manully)

8) Now click next and select radio button which says copy the war on every target to uplaod
war on weblogic server

9) Now if deployment is completed then it will display that sataus of deployment as Active.

Popular posts from this blog

What are Java heap Young, Old and Permanent Generations?

The Java heap is dived into two parts i.e. Young generation and old generation. Young generationYoung generation  memory is 40% of Maximum Java Heap. It consists of two parts, Eden space and Survivor Space. Eden SpaceInitially objects are created in this  Part of Java Heap , here most objects die and quickly are cleaned up by the minor Garbage Collectors (It only runs in young generation and its frequency is high in compared to major garbage collector). Usually any new objects created inside a Java Method go into Eden space and the objects space is reclaimed once the method execution completes. Whereas the Instance Variables of a Class usually lives longer until the Object based on that class gets destroyed. When Eden fills up it causes a minor collection, in which some surviving objects are moved to Survivor Space or an older generation. Survivor Space  The pool containing objects that have survived the garbage collection of the Eden space The parameter Survivor Ratio can be used to tune…

Compression of HttpServletRequest and HttpServletResponse by gzip encoding

This filter is on HTTP headers in a HttpServletRequest, compress data written to the HttpServletResponse, or decompress data read from the request. When supported by the client browser, this can potentially greatly reduce the number of bytes written across the network from and to the client. As a Filter, this class can also be easily added to any J2EE 1.3+ web application.


1).Add the pjl-comp-filter-XX.jar file containing CompressingFilter to your web application's WEB-INF/lib directory.

2).Add the following entries to your web.xml deployment descriptor:



The below data is of my application where i tested this compression technique…

4 mains causes of Long Garbage Collection Pause?

So a long GC Pause can have a direct impact on response time and throughput. But there are some causes for long GC pause which you can check and avoid to increase performance. They are as follows:-

1)Insufficient heap size:- If heap size is small then the size required then the allocation requests for new objects  fail and the JVM needs to invoke garbage collections in an attempt to reclaim space for the allocations. So these frequent Full GCs cause long pauses in the application run. To avoid long GC pause by this identify the average footprint of the application and then specify the heap size accordingly.
2)Fragmentation in the heap:-GCs can occur more frequently due to fragmentation in the Java Heap  and also sometimes causing long pauses in the GCs. This is more probable in the case of Concurrent Mark Sweep collector, also known as CMS, where the tenured generation space is not compacted with the concurrent collections. For more please go through the previous post about heap  compact…