Installing new features to WSO2 EI

In WSO2 Enterprise Integrator, you cannot install new features via management console. That option has been removed. So in order to install a feature, we must use the POM based feature installation. This is explained in WSO2 docs [1]. There few changes you need to made in order to this POM.xml to work.

• The "destination" element value should be changed to, "wso2ei-6.0.0/wso2/components".
• Value of the "dir" attribute in "replace" element should be, "wso2ei-6.0.0/wso2/components/default/configuration/org.eclipse.equinox.simpleconfigurator".

Optionally, Other than downloading p2 repo (which is over 2GB), the URL to P2 repo "http://product-dist.wso2.com/p2/carbon/releases/wilkes/" can be set as "metadataRepository" and "artifactRepository".

Following is a sample pom.xml that is used to install HL7 feature in EI.

	<?xml version="1.0" encoding="UTF-8"?>
	<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>org.wso2.sample</groupId>
	<artifactId>sample-feature-installation</artifactId>
	<version>1.0.0</version>
	<packaging>pom</packaging>
	<name>New feature</name>
	<url>http://wso2.org</url>
	<build>
	<plugins>
	<plugin>
	<groupId>org.wso2.maven</groupId>
	<artifactId>carbon-p2-plugin</artifactId>
	<version>1.5.4</version>
	<executions>
	<execution>
	<id>feature-install</id>
	<phase>package</phase>
	<goals>
	<goal>p2-profile-gen</goal>
	</goals>
	<configuration>
	<profile>default</profile>
	<metadataRepository>http://product-dist.wso2.com/p2/carbon/releases/wilkes/</metadataRepository>
	<artifactRepository>http://product-dist.wso2.com/p2/carbon/releases/wilkes/</artifactRepository>
	<destination>wso2ei-6.0.0/wso2/components</destination>
	<deleteOldProfileFiles>false</deleteOldProfileFiles>
	<features>
	<feature>
	<id>org.wso2.carbon.hl7.feature.group</id>
	<version>4.6.6</version>
	</feature>
	</features>
	</configuration>
	</execution>
	</executions>
	</plugin>
	<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-antrun-plugin</artifactId>
	<version>1.1</version>
	<executions>
	<execution>
	<phase>package</phase>
	<configuration>
	<tasks>
	<replace token="false" value="true" dir="wso2ei-6.0.0/wso2/components/default/configuration/org.eclipse.equinox.simpleconfigurator">
	<include name="**/bundles.info"/>
	</replace>
	</tasks>
	</configuration>
	<goals>
	<goal>run</goal>
	</goals>
	</execution>
	</executions>
	</plugin>
	</plugins>
	</build>
	<repositories>
	<repository>
	<id>wso2-nexus</id>
	<name>WSO2 internal Repository</name>
	<url>http://maven.wso2.org/nexus/content/groups/wso2-public/</url>
	<releases>
	<enabled>true</enabled>
	<updatePolicy>daily</updatePolicy>
	<checksumPolicy>ignore</checksumPolicy>
	</releases>
	</repository>
	</repositories>
	<pluginRepositories>
	<pluginRepository>
	<id>wso2-maven-releases-repository</id>
	<url>http://maven.wso2.org/nexus/content/repositories/releases/</url>
	</pluginRepository>
	<pluginRepository>
	<id>wso2-maven-snapshots-repository</id>
	<url>http://maven.wso2.org/nexus/content/repositories/snapshots/</url>
	</pluginRepository>
	</pluginRepositories>
	</project>

view raw pom.xml hosted with ❤ by GitHub

[1] - https://docs.wso2.com/display/Carbon440/Installing+Features+using+pom+Files

Resolving SSL related issue in WSO2 products for MySql 5.7 upward

If you try to start aWSO2 product with Mysql 5.7 it will give the following warning and the product will not work.

Wed Dec 09 22:46:52 CET 2015 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.

This can be avoided for development purposes by not using SSL. For this the JDBC url for the database should be appended with "useSSL=false". But it cannot be appended with a & sign like in a normal URL. Use the following format. If not it may give xml parsing errors.

jdbc:mysql://localhost:3306/<DB_NAME>?autoReconnect=true&amp;useSSL=false

view raw jdbcurl hosted with ❤ by GitHub

Then it will work as usual.