You projects that are running in WSO2 Integration Cloud can have multiple versions. You can select which of the versions own the default URL and work on the versions in parallel. This means that your version 1.0 may be retired, 2.0 may be in production, 3.0 may be going through QA, and 4.0 may be in early development.
In addition, our newly released feature allows you to update your projects within the same version without changing the numbering. This is great for small incremental improvements and has built-in rolling update and roll-back functionality.
- How do you update a version?
In the home page of your application, choose the correct version where the update is needed as shown in the figure 1 below. In this example it is version 2.0. Then click Update.
You can update the version via a local file system, URL or a Github repository.
Then you need to upload your artifact along with the update comment. This update comment helps you to track your updates per version.The update option enables you to update multiple times per version and it gives you the opportunity to revert the artifact to the previous state if you want.
- How can you revert the version to its previous state?
Once you update an artifact you can see the Update or Rollback option in the homepage. Clicking on that button gives you access to page shown as below.
Choose the correct artifact that you want to revert to and click the Apply button. This will revert your current version to the previous artifact. Now you don’t have to worry about maintaining a large number of versions when fixing urgent issues in your production deployment. With WSO2 Integration Cloud, it’s just a small update to your existing version!
Read our documentation for more information on WSO2 Integration Cloud.
WSO2 provides Connectors dedicated for the most popular business critical services that you will need such as SalesForce, Amazon, Twitter, Google, SAP & Microsoft Dynamics. You can simply download the required connector from the WSO2 Connector Store and plug it into your integration flow with just a few clicks.
One such simple solution is exporting Salesforce leads to Google sheets. This lets you create your own Customer relationship management (CRM) system and a sales pipeline based on your email data. You can even use this information to send customized mailers to selected target groups.
Lets take a look at how you can use the Salesforce SOAP connector to get details of new leads use the Google Spreadsheet connector to add that information to a spreadsheet.
This is a pre-built solution. The required artifacts can be downloaded via the WSO2 Store. *You can even take a look at the source code here.
- To customize this solution for your own salesforce account, google docs, you have to configure the salesforce and google docs accordingly and obtain the required credentials.
- You can download the sample json file with default values. Update the json file with the credentials extracted in above step.
- You can deploy the solution in Integration Cloud using the artifacts downloaded in step1 and the environment variable json file modified in step3.
- Finally, to test this scenario create a new lead in Salesforce.
Your spreadsheet gets updated with the information you provided when creating the new lead and an email notification will be generated.
You can extend this solution by using the WSO2 Developer Studio . The graphical interface of the Developer Studio makes it easier and faster for you to modify existing templates and customize to your specific requirements.
For a detailed step by step guide on how to integrate Salesforce leads to Google sheets visit the WSO2 Store!
We know that support experience can be frustrating when the engineer on the other side does not fully understand the exact issue that you are facing and you get into the long back and forth with questions, answers, and screenshots.
There is now a better way! When creating a support ticket, you can now simply select the Allow Access to WSO2 Support checkbox and the engineer that gets your ticket assigned will be able to securely access your WSO2 deployment and troubleshoot the issue:
This new feature radically shortens the resolution time and gets your going with your project faster. And once the ticket is resolved, you can simply go to the Organization screen (in the 9-dot menu) and revoke the access.
We have extended our public uptime dashboard to go beyond just API Cloud and its default gateway. From now, on API Cloud’s indicators include:
- Web interfaces (Publisher, Admin Dashboard, Developer Portal),
- Key Manager,
- Developer Portal (aka API Store),
- Regional Gateways.
Even more importantly, we now have public dashboard indicators for the other WSO2 Cloud services:
- WSO2 Integration Cloud,
- WSO2 Identity Cloud,
- WSO2 Device Cloud.
For all of these, you can see whether the service is up or down at the moment, how well it performed lately, and can even drill down into uptime and performance over the last few months and get a list of all disruptions we had during the selected period:
In addition to the uptime dashboard, all paying customers get incident notification and post-mortem emails as well as maintenance announcements.
WSO2 Cloud comes with financially backed uptime SLA and our public availability dashboards and incident notification processes help ensure transparency of our quality of service and processes.
November 6-8 in London we will be holding our biggest European event of the year – WSO2Con Europe 2017. I will personally be there as well as our other key leaders, architects, and engineers, and many of our customers.
My personal request to all our cloud customers is to go ahead and submit a session proposal!
Conference talks are a great way to increase your own visibility and boost your career. And you also get perks including free airfare, hotel, and conference pass! There is a deadline of July 28 – so please try to meet it. If you cannot – please let me know so I can apply some lobbying for you. 🙂
If submitting your talks is not your thing (yet) go ahead and buy your conference pass today while the early bird discount is still in place.
Plus, the website also has lots of great recordings from earlier conferences.
I hope to see you in London in November!
We have made it easier to pay for WSO2 Cloud services (API, Integration, Device, and Identity). When we launched initially, monthly credit card payments were the only option we provided. Now we changed two things:
1. You can pay for a year ahead and save 10% of your subscription price:
2. And, if credit card is not something that your purchasing department likes, you can get a regular invoice and pay via a wire transfer instead:
Whatever is the WSO2 Cloud service of your choice, we would like you to be able to pay for it conveniently (and save money on the way!)
We have added the ability to host Ballerina-based services in WSO2 Integration Cloud.
Ballerina is a general purpose, concurrent and strongly typed programming language with both textual and graphical syntaxes, optimized for integration.
Ballerina has been designed for integration scenarios and the world of web services and containers – which makes it a perfect development technology for the cloud.
To host a Ballerina service, simply take the project file and upload it to the cloud as a new application:
See our tutorial on Creating a Ballerina Service.
At the moment, Integration Cloud only supports Ballerina services (not main-based programs yet). We are working on adding Main() support as well as integrating the tooling into the cloud. Stay tuned!
WSO2 Integration Cloud comes with a wide range of available runtimes including WSO2 ESB, Data Services, Ballerina, Java, JAX-RS, JAX-WS, Jaggery, and PHP.
However, we understand that all scenarios are different and yours might need a runtime that is custom to you. To address this need, we have implemented support for custom Docker images.
Your images can be added and instantiated using the Custom section in the Create Application wizard:
When you add your image, we import it and perform various security scans. Once the scans are successful, you can start the image as your new application, choose the number of instances you need, and so on.
See Integration Cloud’s custom Docker image documentation for details.
Integration projects can be complex and include multiple services.
In the world of WSO2 ESB, these services are created and uploaded as CAR files.
We have rolled out a nice little Integration Cloud improvement that makes hosting such projects easier. Any ESB app in Integration Cloud can now have multiple CAR files uploaded and running.
When you create a new ESB app or a new version of an existing app in Integration Cloud and you have multiple CAR files, simply browse to each of them one at a time, and the system will get all of them uploaded and added to the runtime:
When you scale this application to multiple instances, each new instance automatically gets all the CAR files that you uploaded.
And you also save money and compute resources because the same ESB instances are reused across the projects.
I am happy to announce that we have just commercially launched WSO2 Integration Cloud: our platform for hosting your integration projects and API backends.
There are 5 easy monthly tiers to pick from depending on the required scale and functionality:
- Starter is the smallest tier that can be used to host simple microservice-based project as well as Java (including JAX-RS and JAX-WS) and PHP implementations.
- Getting Traction adds support for WSO2 Enterprise Service Bus (ESB) and Data Services, and increases the amount of resources available.
- Medium tier lets you select your hosting region (from 12 locations around the globe), ability to scale up your applications, and gives custom docker image support,
- Large gives multi-region support, 5 GB databases, and 48 GB of RAM for up to 16 applications.
- Extra-Large is the enterprise package that lets you scale up to 32 applications, 192 GB of RAM, and 10 databases 10 GB each.
With all plans you can set up a VPN connection for $498 / month.
Get started with WSO2 Integration Cloud today!