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

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...
1 comment
Read more

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...
Post a Comment
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...
6 comments
Read more