This is the latest release in the 6.x.x family. For EI 7.0.0, click here.

All docs This doc

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Apply the following updates to your EI 6.6.0 server.

Connect the ESB profile of EI 6.6.0 to your existing databases (which are used for registry data and user management data):

Panel
borderColor#542989
bgColor#ffffff
borderWidth1
Expand
titleConnecting to the database
  1. Open the master-datasources.xml file (stored in the <EI_6.6.0_HOME>/conf/datasources/ directory) and update the parameters given below.

    Tip

    By default, registry and user management data are stored in one database and is configured in the master-datasources.xml file. If you have separate databases for registry and user management data, you may need separate datasource configurations.

    ElementDescription
    urlThe URL of the database.
    username and passwordThe name and password of the database user.
    driverClassNameThe class name of the database driver.
  2. Open the registry.xml file (stored in the <EI_6.6.0_HOME>/conf directory) and specify the datasource name (as defined in step 'a').

    Code Block
    <dbConfig name="wso2registry">    
        <dataSource>jdbc/MY_DATASOURCE_NAME</dataSource>
    </dbConfig>
  3. If a JDBC user store is used, open the user-mgt.xml file (stored in the <EI_6.6.0_HOME>/conf/ directory), and update the following database connection parameters under the <UserStoreManager class="org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager"> section.

    ElementDescription
    urlThe URL of the database.
    username and passwordThe name and password of the database user.
    driverClassNameThe class name of the database driver.
  4. Further, update the system administrator configurations and the datasource name in the user-mgt.xml file. See Configuring a JDBC user store for instructions.

...

Tip

These keystores are required when you perform data re-encryption later in this guide. 

  1. Move the keystore and truststore files by copying the <EI_6.5.0_HOME>/repository/resources/security directory to the same directory in EI 6.6.0.
  2. Open the carbon.xml file (stored in the <EI_6.6.0_HOME>/conf/ directory) and update the details of the keystore used for data encryption.

    Panel
    borderColor#542989
    bgColor#ffffff
    borderWidth1
    Expand
    titleUsing a common keystore for data encryption and SSL signing?

    Update the following configuration element:

    Code Block
    <KeyStore>    
        <Location>${carbon.home}/resources/security/wso2carbon.jks</Location>
        <Type>JKS</Type>
        <Password>wso2carbon</Password>
        <KeyAlias>wso2carbon</KeyAlias>
        <KeyPassword>wso2carbon</KeyPassword>
    </KeyStore>
      
    <TrustStore>
        <!-- trust-store file location -->
        <Location>${carbon.home}/repository/resources/security/client-truststore.jks</Location>
        <!-- trust-store type (JKS/PKCS12 etc.) -->
        <Type>JKS</Type> 
        <!-- trust-store password -->
        <Password>wso2carbon</Password>
    </TrustStore>
    Expand
    titleUsing a separate keystore exclusively for data encryption?

    Add the following configuration element under <Security> in the carbon.xml file, and update the values:

    Code Block
    <CryptoService>
      <Enabled>true</Enabled>
      <InternalCryptoProviderClassName>org.wso2.carbon.crypto.provider.KeyStoreBasedInternalCryptoProvider</InternalCryptoProviderClassName>
      <ExternalCryptoProviderClassName>org.wso2.carbon.core.encryption.KeyStoreBasedExternalCryptoProvider</ExternalCryptoProviderClassName>
      <KeyResolvers>
        <KeyResolver className="org.wso2.carbon.crypto.defaultProvider.resolver.ContextIndependentKeyResolver" priority="-1"/>
      </KeyResolvers>
    </CryptoService>
    
    <InternalKeyStore>  <Location>${carbon.home}/repository/resources/security/internal.jks</Location>
      <Type>JKS</Type>
      <Password>wso2carbon</Password>
      <KeyAlias>wso2carbon</KeyAlias>
      <KeyPassword>wso2carbon</KeyPassword>
    </InternalKeyStore>

    See Configuring Keystores in WSO2 Products for more information.


Step 3Step 2: Run the migration client

...

  1. Create a folder named 'migration' inside  <EI_6.6.0_HOME> .

  2. Copy the  migration-conf.properties  file to the <EI_6.6.0_HOME>/migration folder and update the following properties:

    The key password of the default keystore. By default, this is wso2carbon.
    admin.user.name keystore.identity.key.passwordThe user name of the system administrator.
    keystore.identity.locationThe location of the keystore that is used for data encryption in the EI 6.6.0. By default, this is <EI_6.6.0_HOME>/repository/resources/security/wso2carbon.jks.
    administrator.

    Note that you do not need to update the keystore-related properties given in the file.


  3. Download the migration JAR file and copy it to the <EI_6.6.0_HOME>/dropins/ directory
  4. Open a terminal and navigate to the <EI_6.6.0_HOME>/bin/ directory.

  5. Execute the product startup script with the '-Dmigrate.from.product.version=ei611ei650' command as shown below.

    Panel
    borderColor#542989
    bgColor#ffffff
    borderWidth1
    Localtab Group
    Localtab
    titleOn MacOS/Linux/CentOS

    Open a terminal and execute the following command:

    Code Block
    sh integrator.sh -Dmigrate.from.product.version=ei650
    Localtab
    titleOn Windows

    Open a terminal and execute the following command:

    Code Block
    integrator.bat -Dmigrate.from.product.version=ei650
  6. Once the migration is successful, stop the server and delete the migration JAR (org.wso2.carbon.ei.migration-6.6.0.jar) from the <EI_6.6.0_HOME>/dropins/ directory.

...

To migrate all the required folders, files, libraries, etc. from WSO2 EI 6.5.0 to to WSO2 EI 6.6.0:

  1. Copy the database connector JAR files stored in the <EI_6.5.0_HOME>/lib directory to the same directory in WSO2 EI 6.6.0

...

  1. .
  2. Copy the database connector JAR files stored in keystores and truststores used in the ESB profile of WSO2 EI 6.5.0 from the <EI_6.5.0_HOME>/lib directory repository/resources/security directory to the same directory in WSO2 EI 6.6.0.Verify that the keystores are migrated.  See Configuring Keystores in WSO2 products. TipIf you successfully followed the instructions on upgrading the databases, the keystore configurations should already be migrated by now.
  3. If you have secondary user stores created for the ESB profile of WSO2 EI 6.5.0, you need to copy the 'userstore' folder in the <EI_6.5.0_HOME>/repository/deployment/server/ directory to the same directory in WSO2 EI 6.6.0.
  4. If there are any third-party libraries used with WSO2 EI 6.5.0 that you want to migrate, copy the relevant libraries from WSO2 EI 6.5.0 to WSO2 EI 6.6.0: 
    • If you have used JMS libraries, JDBC libraries, etc., copy the contents from the <EI_6.5.0_HOME>/lib directory to the same directory in WSO2 EI 6.6.0.
    • If you have used OSGi bundles such as SVN kit etc., copy the contents from the <EI_6.5.0_HOME>/dropins directory to the same directory in WSO2 EI 6.6.0.

...