Page Comparison

This page takes you through the general steps for upgrading product versions based on Carbon 4.3.0 to Carbon 4.4.0.

...

Copy the data from the old database to the staging database you created. This becomes the new database for your new version of Carbon.
Download Carbon 4.4.0 and connect it to your staging database.

Update the configuration files in Carbon 4.4.0 according to the requirements.

Expand

title	Note these configurations that were introduced in Carbon 4.3.0:

Given below is a list of configurations that were are new from Carbon 4.3.0 onwards. Therefore, if you are in the process of upgrading to Carbon 4.4.0 from Carbon 4.2.0, be mindful of these configuration changes:

Configuration File

The axis2.xml file stored in the <PRODUCT_HOME>/repository/conf/axis2 /directory. The following new parameter is added: <parameter name="httpContentNegotiation">true</parameter>. When this is set to 'true', the server will determine the contentType of responses to requestscontent type used for responses, by using the 'Accept header' of the request.

The tenant-axis2.xml file stored in the <PRODUCT_HOME>/repository/conf/tomcat/ directory. The default value for the "httpContentNegotiation" parameter is set to 'true': <parameter name="httpContentNegotiation">true</parameter>.

The catalina-server.xml file stored in the <PRODUCT_HOME>/repository/conf/tomcat/ directory.

Keystore parameters are added under the <Connector> element as shown below. This setting allows you to use a separate keystore and security certificates to certify for certifying SSL connections. Note that the location and password of the default "wso2carbon.jks" keystore is given for these parameters by default.

Code Block
keystoreFile=location of the keystore file keystorePass=password for the keystore

The master-datasources.xml file stored in the <PRODUCT_HOME>/repository/conf/datasources/ directory. Default The default auto-commit setting for a data source datasource is set to false: <defaultAutoCommit>false</defaultAutoCommit>.

The carbon.xml file stored in the <PRODUCT_HOME>/repository/conf/ directory.

New parameters are added to define the proxy context path as shown below;.
Code Block
<MgtProxyContextPath></MgtProxyContextPath> <ProxyContextPath></ProxyContextPath>
Proxy The proxy context path is a useful parameter that allows you to add a proxy path when a Carbon server is fronted by a reverse proxy. In addition to the proxy host and proxy port, this parameter allows you to add a path component to external URLs. See Adding a Custom Proxy Path for details.

The following port configurations have been removed:

Code Block
<!-- Embedded Qpid broker ports → <EmbeddedQpid> <!-- Broker TCP Port → <BrokerPort>5672</BrokerPort> <!-- SSL Port → <BrokerSSLPort>8672</BrokerSSLPort> </EmbeddedQpid>

In Carbon 4.2.0, the following registry keystore configuration was required for configuring the keystore keys that certify encrypting/decrypting meta data to the registry as shown below. From Carbon 4.3.0 onwards the primary keystore configuration shown below will be used for this purpose as well. Therefore, it is not necessary to use a separate registry keystore configuration for encrypting/decrypting meta data to the registry. Read more about keystore configurations in Carbon 4.4.0.

Code Block

<RegistryKeyStore>
            <!-- Keystore file location-->
            <Location>${carbon.home}/repository/resources/security/wso2carbon.jks</Location>
            <!-- Keystore type (JKS/PKCS12 etc.)-->
            <Type>JKS</Type>
            <!-- Keystore password-->
            <Password>wso2carbon</Password>
            <!-- Private Key alias-->
            <KeyAlias>wso2carbon</KeyAlias>
            <!-- Private Key password-->
            <KeyPassword>wso2carbon</KeyPassword>
</RegistryKeyStore>

The registry.xml file stored in the <PRODUCT_HOME>/repository/conf/ directory. The default value is changed to 'false' for the following setting: <versionResourcesOnChange>false</versionResourcesOnChange>.

Copy the following directories from the old database to the staging database.
1. To migrate the super tenant settings, copy the <PRODUCT_HOME>/repository/deployment/server directory.
2. If multitenancy is used, copy the <PRODUCT_HOME>/repository/tenants directory.
Note
Note that configurations should not be copied directly between servers.
Start the server.

...

Versions Compared

Old Version 8

New Version Current

Key