
|
WSO2 Carbon is the award-winning base platform for WSO2’s enterprise-grade middleware stack. The OSGi-based component framework allows the complete set of products to leverage shared components, ensuring a consistent set of features between products, a consistent user experience, and reusing of identical components. This framework not only enhances the productivity of developing and delivering new products, but also allows advanced customers to package a customized set of features into lean, customized middleware runtimes. Get Involved Today! This page is the home for the development and user community of WSO2 Carbon. From here, you can contribute to the source code, report issues, participate in discussions in the community forums or access downloads, documentation and tutorials. For more information on the capabilities, features, usage scenarios, case studies and white papers, cloud hosted versions, and commercial support offerings, please visit WSO2 Carbon Product page. WSO2 Carbon P2 Repository can be downloaded as a zip file:Download P2 (ZIP) Articles
[Yenlo] Rollback a WSO2 FeatureWhen an administrator installs new features through the admin console it is not very difficult to make a mistake. For instance selecting an incorrect P2 repository and installing a feature which is not meant to be installed on the current version of the WSO2 product.
Read the full article on Yenlo website
[WSO2Con2013] WSO2 Carbon 4.0.0 Kernel Design and ArchitectureWSO2 Carbon is an innovative enterprise middleware platform, which allows you to transform your development and operational processes. The latest Carbon platform release (4.0.0) introduces revolutionary kernel architecture modifications. The modifications improve Tomcat 7.0 compatibility, enhance Cloud efficiency, introduce DevOps best practices, and reduce application deployment footprint.
Sameera Jayasoma
Senior Technical Lead, WSO2 Inc.
Sameera Jayasoma joined WSO2 in May 2008. He is a technical lead and a member of the platform technologies management committee, focusing on the WSO2 Carbon and WSO2 Web Services Application Server. As a WSO2 intern in 2007, Sameera developed an Axiom version of Rhino’s E4X implementation, which is used in the WSO2 Mashup Server. He also has provided technology consulting on customer engagements, including Quick Start Program, Business Process Execution Language (BPEL), and cloud projects.
Sameera has contributed to a number of Apache Software Foundation (ASF) projects, including Apache Axis2 and Axiom. He also was a co-developer of Apache Rampart2. During the 2007 Google Summer of Code, Sameera also contributed to the development of JAX-WS templates for the Apache Axis2/Java Codegen tool.
[WSO2Con2013] WSO2 Carbon Product Performance and Deployment Topology SizingPerformance is a key constraint limiting business transaction processing volume, transaction responsiveness, and an application solution’s ability to fulfill SLAs (Service Level Agreements). Both consumer and partner facing applications often must process large transaction volumes with high throughput and low latency. Architecture and deployment topology significantly impacts whether an application or service solution will meet business transaction processing goals.
Asanka Abeysinghe
Director of Solutions Architecture, WSO2 Inc.
Asanka is WSO2 director of solutions architecture, and he focuses on the company’s vertical market capabilities, including financial services. Additionally, he provides consulting and conducts regular training sessions and workshops for enterprise IT architects and developers.
Asanka has more than 10 years industry experience implementing projects that range from desktop and Web applications through to highly scalable distributed systems and SOAs in the financial domain, mobile platforms, and business integration solutions.
[WSO2Con2013] Running Operations for Carbon and StratosApplication and service users expect reliable access and fast response times. When building operational infrastructure supporting high availability, scalability, and robust monitoring, outdated tooling and architecture often reduce DevOps team effectiveness.
Chamith Kumarage
Associate Technical Lead, WSO2 Inc.
Chamith joined WSO2 in November 2007 and is an Associate Technical Lead and Manager of Infrastructure.
He has over 5 years of experience in systems and network administration and currently oversees WSO2′s overall system and network operations. He was an original author of the Texplorer Project http://texplorer.sourceforge.net and is interested in platform and infrastructure virtualization, distributed computing, IT security, load balancing, cloud monitoring and backup systems.
WSO2 Customer Stories: WSO2 middleware at Two Degrees MobileWe caught up with Neeraj Satija of Two Degrees Mobile (2degrees) after his presentation at WSO2Con 2011. There we talked about the mobile services provider’s use of WSO2 Carbon middleware. Here is an edited version of our discussion. See video for full interview.
Tutorials
Sharing Registry Space across Multiple Product InstancesWSO2 Carbon Registry Kernel contains three main partitions of the Registry space. Those are namely Local Data Repository, Configuration Registry and Governance Registry. These three partitions are available on all the products based on WSO2 Carbon Platform, which allows to share resources and configuration replication.
Deploying WSO2 Carbon 2.0.x in IBM WebSphere Application Server 6.1Yumani Ranawera, Senior Software Engineer at WSO2 takes a step-by-step approach in deploying WSO2 Carbon 2.0.x in IBM WebSphere Application Server 6.1. WSO2 Carbon is a component based SOA platform which is based on Equinox and OSGi. It is the base platform for all Java products of WSO2. Built on OSGi, Carbon encapsulates major SOA functionality such as data services, business process management, ESB routing/transformation, rules, security, throttling, caching, logging and monitoring. All these major features can be plugged to the WSO2 Carbon based products, as components.
Operating WSO2 Amazon EC2 Cloud instances from command lineThis tutorial will guide you on how you can work with Amazon AMI instances from command line instead of using any GUI interfaces like Elasticfox. Cloud computing is relatively a new technology that gives small to mid-size companies the computing power needed to compete in the market place without having to burden themselves with the high cost of purchasing additional computers, storage and all the extra equipment that is usually needed.
Creating Secure JMS Connections with Apache ActiveMQThis brief tutorial outlines the basic steps that need to be followed to configure a WSO2 Carbon Framework based product and establish a secure JMS connection with Apache ActiveMQ. In here, we use the WSO2 Enterprise Service Bus (ESB) as an example. The same procedure can be followed to configure any other product based on the WSO2 Carbon Framework.
|
Webinars
PastEnterprise Use Case Webinar - WSO2 DepSync for Data Synchronization between the Nodes of a Cluster - Tuesday, October 30th, 2012Tuesday, 30th October 2012 9:00 AM (PDT)
Tuesday, 30th October 2012 10:00 AM (GMT)
Setting up a cluster is an important aspect when developing enterprise software and deploying them in mission critical environments. WSO2 Carbon-based products can be easily clustered to have scalability, high availability, and higher performance. This brings challenges of keeping the cluster nodes synchronized to ensure a consistent, and reliable cluster setup.
Knowledge Base Items
Playing Around With Carbon Product ThemesCarbon products has it’s own unique look and feeling. The headers, footers, menus, links look consistent among every product. While keeping this consistant look and feel, each product has it’s own theme. Sometimes it’s interesting to play around with these themes to see what we can achieve.
Binding the same ports for different IPs on the same machine for multiple Carbon Server instancesp { margin-bottom: 0.08in; }td p { margin-bottom: 0in; }a:link { }
This post discusses how to set multiple instances of WSO2 Carbon in a multiple-IP machine, binding to the same ports, with different IP addresses. Multiple instances of WSO2 Carbon can be configured to run on a single machine, to fit the requirements. The configuration often involves changing the ports of the instances, such that there won't be any conflict in the ports used. However, given a multiple-IP machine, multiple Carbon instances can be bound to the same ports, with the different instances listening over the available IPs.
Adding CA (Certificate Authority) Signed Certificate to WSO2 ProductsBy default all WSO2 products shipped with a self signed certificate. In-order to make products more secure, many users prefer to install a CA signed certificate into the product. This KB describes steps to install a CA signed certificate into WSO2 products.
Crypto Caching for Web Services hosted in WSO2 Carbon PlatformAll products of WSO2 platform uses the Apache Rampart to provide security for Web Services. As a result, all features of Apache Rampart are inherited by the WSO2 products. Crypto objects are used to store properties that required to perform signature/encryption. Crypto objects have information such as as crypto provider, keystore and its password. Until now, Crypto objects were initialized on per call basis.
How to customize the UI Theming in WSO2 Carbon based productsMy assumption is that you want to change the WSO2 Governance Registry User Interface theme. You can apply the same steps described below to modify any of the WSO2 Carbon based product's UI themes (But name of the .jar files are different from product to product, Eg: for G-Reg, org.wso2.governance.styles-3.6.0.jar, etc). There are some other bundles which contains UI theming and you will be able to modify them in the same way like styles bundle. This guide is applicable for all the WSO2 Products based on Carbon 3.0.* or above.
Forums
Can not publish because module
|