Installation Prerequisites

Prior to installing any WSO2 Carbon based product, it is necessary to have the appropriate prerequisite software installed on your system. Verify that the computer has the supported operating system and development platforms before starting the installation.

System requirements

Memory	~ 8 GB minimum is recommended. In a stand-alone deployment, about 6GB of memory is allocated to the Carbon JVM and Spark. The balance is used by the operating system. In a distributed deployment, Spark is run in a seperate JVM. It is recommended to allocate 4GB of memory for Carbon JVM and 2GB for Spark. ~ 4 GB heap size.
Disk	~ 10 GB minimum (excluding space allocated for log files and databases.) The disk space required depends on the amount of index data that needs to be stored.
Cores	A minimum of 4 CPU cores are recommended. A lower number may affect performance.

Environment compatibility

Operating Systems / Databases

All WSO2 Carbon-based products are Java applications that can be run on any platform that is Oracle JDK 1.8* compliant. Also, we do not recommend OpenJDK as we do not support it or test our products with it.
All WSO2 products are generally compatible with most common DBMSs. For more information, see Working with Databases.
It is not recommended to use Apache DS in a production environment due to issues with scalability. Instead, it is recommended to use an LDAP like OpenLDAP for user management.
For environments that WSO2 products are tested with, see Compatibility of WSO2 Products.
If you have difficulty in setting up any WSO2 product in a specific platform or database, please contact us.

Required applications

The following applications are required for running the Data Analytics Server and its samples, or for building from the source code. Mandatory installs are marked with *.

Application	Purpose	Version	Download Links
Oracle Java SE Development Kit (JDK)*	To launch the product as each product is a Java application. To build the product from the source distribution (both JDK and Apache Maven are required). To run Apache Ant. Note To launch WSO2 DAS, you need to have Oracle 1.8.. You cannot launch WSO2 DAS with Oracle JDK 1.7. or lower.	1.8.* Important! Some updates of JDK 1.8 (for example, JDK1.8.0_151) are affected by a known issue related to GZIP decoding. Until this issue is fixed, we recommend one of the following approaches: Use either JDK1.8.0_144 or JDK1.8.0_077 updates. We have verified that these versions are not affected by the known issue. Alternatively, you can disable GZIP decoding for your product by following the steps given below. This will ensure that your product is not affected by the known issue. Open the `catalina-server.xml` file from the `<DAS_HOME>/repository/conf/tomcat/` directory. Set the `compression` parameter (under each of the connector configurations) to false as shown below: compression="off" Restart the server. We do not recommend OpenJDK as we do not support it or test our products with it.	http://java.sun.com/javase/downloads/index.jsp
JDBC-compliant Connector for Java	Required as a standardized database driver for Java platforms and development.	1.7.0 or later	http://dev.mysql.com/downloads/connector/
Apache Ant	To compile and run the /wiki/spaces/PS/pages/10519862.	1.7.0 or later	http://ant.apache.org
Git	Required to check out the source from the Git repository.	1.9.0 or later	http://git-scm.com/downloads/
Apache Maven	To build the product from the source distribution (both JDK and Apache Maven are required). If you are installing by downloading and extracting the binary distribution instead of building from the source code, you do not need to install Maven.	3.0.*	http://maven.apache.org
Web Browser	To access each product's Management Console . The Web Browser must be JavaScript enabled to take full advantage of the Management console. WSO2 DAS does not support Internet Explorer 10 and older versions.

In order to avoid the NoClassDefFoundError exception when running the C++ code embedded in WSO2 DAS and other WSO2 DAS-based products, install glibc package in the operating system. For detailed installation guidelines, see alpine-pkg-glibc.

Then download snappy-java from here and copy it to the <PRODUCT_HOME>/repository/components/lib directory.

The path specified above changes depending on the Analytics profile for which you are doing this installation.

e.g., For EI Analytics, the directory in which you need to place the snappy-java package is <EI_HOME>/wso2/analytics <EI_HOME>/wso2/analytics/repository/components/lib directory.

Click here to view the exception that may occur if glib is not installed...

2018-08-03 06:21:01,687] INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL : https://localhost:9443/carbon/

[2018-08-03 06:21:01,701] INFO {org.wso2.carbon.event.stream.core.internal.EventJunction} - WSO2EventConsumer added to the junction. Stream:org.wso2.is.analytics.stream.LoginSuccessAfterMultipleFailures:1.0.0

[2018-08-03 06:21:01,701] INFO {org.wso2.carbon.analytics.eventsink.AnalyticsEventStoreDeployer} - Deployed successfully analytics event store: org_wso2_is_analytics_stream_LoginSuccessAfterMultipleFailures.xml

[2018-08-03 06:21:01,994] INFO {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task scheduled: [-1234][ANALYTICS_SPARK][ISAnalytics-ConfigureAlertLongSessions-ConfigureAlertLongSessions-batch1]

[2018-08-03 06:21:27,664] INFO {org.wso2.carbon.event.processor.manager.core.internal.CarbonEventManagementService} - Starting polling event receivers

Exception in thread "dag-scheduler-event-loop" java.lang.NoClassDefFoundError: org/xerial/snappy/SnappyInputStream

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:348)

at org.apache.spark.util.Utils$.classForName(Utils.scala:175)

at org.apache.spark.io.CompressionCodec$.createCodec(CompressionCodec.scala:71)

at org.apache.spark.io.CompressionCodec$.createCodec(CompressionCodec.scala:65)

at org.apache.spark.broadcast.TorrentBroadcast.org$apache$spark$broadcast$TorrentBroadcast$$setConf(TorrentBroadcast.scala:73)

at org.apache.spark.broadcast.TorrentBroadcast.<init>(TorrentBroadcast.scala:80)

at org.apache.spark.broadcast.TorrentBroadcastFactory.newBroadcast(TorrentBroadcastFactory.scala:34)

at org.apache.spark.broadcast.BroadcastManager.newBroadcast(BroadcastManager.scala:63)

at org.apache.spark.SparkContext.broadcast(SparkContext.scala:1326)

at org.apache.spark.scheduler.DAGScheduler.submitMissingTasks(DAGScheduler.scala:1006)

at org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$submitStage(DAGScheduler.scala:921)

at org.apache.spark.scheduler.DAGScheduler.handleJobSubmitted(DAGScheduler.scala:861)

at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1607)

at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1599)

at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1588)

at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48)

Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.xerial.snappy.snappy-java (469).

at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:124)

at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:469)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)

at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)

at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)

at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:452)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)

at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

... 17 more

Caused by: org.osgi.framework.BundleException: Exception in org.xerial.snappy.SnappyBundleActivator.start() of bundle org.xerial.snappy.snappy-java.

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)

at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)

at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:478)

at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:263)

at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:109)

... 26 more

Caused by: java.lang.UnsatisfiedLinkError: /home/wso2carbon/wso2is-analytics-5.5.0/repository/components/default/configuration/org.eclipse.osgi/bundles/469/1/.cp/org/xerial/snappy/native/Linux/x86_64/libsnappyjava.so: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /home/wso2carbon/wso2is-analytics-5.5.0/repository/components/default/configuration/org.eclipse.osgi/bundles/469/1/.cp/org/xerial/snappy/native/Linux/x86_64/libsnappyjava.so)

at java.lang.ClassLoader$NativeLibrary.load(Native Method)

at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)

at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1837)

at java.lang.Runtime.loadLibrary0(Runtime.java:870)

at java.lang.System.loadLibrary(System.java:1122)

at org.xerial.snappy.SnappyBundleActivator.start(SnappyBundleActivator.java:58)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)

at java.security.AccessController.doPrivileged(Native Method)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)

... 32 more

You are now ready to install. Click one of the following links for instructions: