Day: April 1, 2018

While given a common name, not all integration platforms as a service (iPaaS) are built the same, in fact far from it. Much like purchasing a car, the destination of adding integrations to your product may look the same, but getting there (and how fast) can be wildly different. While there are many resources that help you ask the right questions when car shopping, there is relatively little when it comes to evaluating an integration platform. These eight questions will help guide you when kicking the tires on an iPaaS.
1. Who will handle the updates?

The structure of APIs are fluid. Application providers continually enhance their endpoints for consumers, but who will make the updates in your integration? Is maintenance and versioning included in the integration platform or does the burden of upkeep fall to you?

2. Are integration patterns point-to-point or one-to-many? https://goo.gl/qBxK6x #DataIntegration #ML

ICYMI: Tip number one will be about data existence check. There are often situations that nearly the same conditions need to be checked in every line. I have seen many transformations that were really long and complex. Reading them was not only difficult but a lot of repeatable conditional checks were made. Here I will show you an example that will evolve to a point where we can reuse everything that was possible. As a result, we should achieve more concise and readable transformations. MuleSoft is about to release new DataWeave, which is why my examples are both in 1.0 and 2.0.

Contract

Here is the input in XML format and the expected JSON result: https://goo.gl/XqZYBS #DataIntegration #ML

Welcome back! If you missed Part 1, you can check it out here!

Designing the Deployment Architecture

WSO2 has defined five deployment patterns for WSO2 API Manager based on the following four aspects of the deployment: https://goo.gl/XSLwkj #DataIntegration #ML

Hi Everyone,

Am very new to SAP Hybris.

While am taking the initial step to extract the hybris commerce suite 6.1 and  setup the environment, I faced the unsupported version error.

While setting up the hybris suite from console, you may face the following error.

Error:

java.lang.UnsupportedClassVersionError: de/hybris/ant/taskdefs/DbDriverValidator : Unsupported major.minor version 52.0

Reason:

This will happen because of Java version Compatibility, which means in your system if your using more than one jdk. This error will occur.

Solution:

Go to your

ControlPanel->Advanced system settings->Environment variables

In the Edit system variable, if your find the text as  path, then click on edit and check if you have more than one jdk exists.

If you found any, then remove those jdks and put only one jdk which is used for building Hybris suite.
Then click on ok.

And Restart your system once.

After completion of Restart, Follow the below steps.

1.Run your hybris suite from console.

2.By setting ant environment by the command in the below path

hybrissuitefolder/hybris/bin/platform: setantenv.bat

3.Now, check the javaversion by giving a command like java -version

4.Once check if the java version is related to your hybris suite for running.

5.If not change your jdk version.

6.If you found that java version is related to run your hybris suite then, do an ant all.

7.And start the hybris server by giving the command as hybrisserver.bat http://bit.ly/2IjILEn #SAP #SAPCloud #AI