Skip to main content

How to restore your WSO2 server in to a previous state

WSO2 Carbon based servers comes with a rich set of features which can be installed on top of any WSO2 products. This feature makes it easy for the users to install different features on the same WSO2 server and use that server for all your enterprise SOA requirements. As an example, a user can install WSO2 DSS features on top of WSO2 ESB to enable distributed transactions inside the WSO2 ESB itself.

 You can find more information about provisioning and feature installation from the below link.
http://wso2.com/projects/carbon/provisioning-wso2-carbon-with-equinox-p2/

 This blog post describes about how to restore your WSO2 server in to a previous state once you have installed a lot of features in your system. Sometimes installing different features with incompatible versions (This happens if you install features manually by copying jar files) may corrupt your WSO2 server and it will fail to start. In this kind of scenario you may need to restore your server in to a previous state in which you have been working successfully.

If you cannot start the server after an unsuccessful feature installation, use the following steps to revert to a previous installation:
  1. Start your product with the -DosgiConsole system property.
  2. Once the server is started, type the following command:
    osgi> getInstallationHistory
    You will get the following list of states:
    1376883697814 August 19, 2013 at 09:11:37 IST
    1376883697957 August 19, 2013 at 09:11:37 IST
    1376883700725 August 19, 2013 at 09:11:40 IST
    1376883701385 August 19, 2013 at 09:11:41 IST
    1376883704884 August 19, 2013 at 09:11:44 IST
    1376883712770 August 19, 2013 at 09:11:52 IST
    1376883715952 August 19, 2013 at 09:11:55 IST
    1376883743493 August 19, 2013 at 09:12:23 IST
    1376933879416 August 19, 2013 at 23:07:59 IST
    1376940017503 August 20, 2013 at 00:50:17 IST
  3. Check what features are installed and uninstalled in a given state, by entering the following command:
    osgi> getInstallationHistory <timestamp> 
    For example:
    osgi> getInstallationHistory 1376933879416    The output will be as follows:
    -- Installed features in this configuration
    -- Uninstalled features in this configuration
    WSO2 Carbon - Service Management Feature 4.2.0
    WSO2 Stratos - Deployment Features 2.2.0
    WSO2 Stratos - Common Composite Feature 2.2.0
    WSO2 Stratos - Usage Agent Feature 2.2.0
    WSO2 Stratos - Throttling Agent Feature 2.2.0
    WSO2 Stratos AppServer - Dashboard UI Features 2.2.0
    WSO2 Stratos AppServer - Dashboard UI Features 2.2.0
  4. Decide to which state you need to revert the system to, and thereafter use the following command:
    osgi> revert <timestamp>

    For example:
    osgi> revert 1376933879416
    The output will be as follows:
    Successfully reverted to 1376933879416
    Changes will get applied once you restart the server.
Labels:

Comments

Post a Comment

Popular posts from this blog

WSO2 ESB tuning performance with threads

I have written several blog posts explaining the internal behavior of the ESB and the threads created inside ESB. With this post, I am talking about the effect of threads in the WSO2 ESB and how to tune up threads for optimal performance. You can refer [1] and [2] to understand the threads created within the ESB. [1] http://soatutorials.blogspot.com/2015/05/understanding-threads-created-in-wso2.html [2] http://wso2.com/library/articles/2012/03/importance-performance-wso2-esb-handles-nonobvious/ Within this blog post, I am discussing about the "worker threads" which are used for processing the data within the WSO2 ESB. There are 2 types of worker threads created when you start sending the requests to the server 1) Server Worker/Client Worker Threads 2) Mediator Worker (Synapse-Worker) Threads Server Worker/Client Worker Threads These set of threads will be used to process all the requests/responses coming to the ESB server. ServerWorker Threads will be used to pr
4 comments
Read more

How puppet works in your IT infrstructure

What is Puppet? Puppet is IT automation software that helps system administrators manage infrastructure throughout its lifecycle, from provisioning and configuration to orchestration and reporting. Using Puppet, you can easily automate repetitive tasks, quickly deploy critical applications, and proactively manage change, scaling from 10s of servers to 1000s, on-premise or in the cloud. How the puppet works? It works like this..Puppet agent is a daemon that runs on all the client servers(the servers where you require some configuration, or the servers which are going to be managed using puppet.) All the clients which are to be managed will have puppet agent installed on them, and are called nodes in puppet. Puppet Master: This machine contains all the configuration for different hosts. Puppet master will run as a daemon on this master server. Puppet Agent: This is the daemon that will run on all the servers, which are to be managed using p
7 comments
Read more

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte
3 comments
Read more