WSO2 App Factory M7 is released

We finally got M7 out!

You can download the VM from here

Here are the new features of M7.

• Integrating with Redmine
• CIO/CEO dashbords
• BPEL Security
• Role based security
• Change the username to email address
• Dependency Management - API sandboxing
• Build Status Recording and Gadget
• Login to Controller to get Logs
• G-Reg check list items

From this point onwards we are going to try continuous development and deployment of App Factory - at least internally and see how it goes.

The making of WSO2 App Factory - Storing Artifacts

These days I am thinking a lot about scalability of our deployment setup. Our pre-alpha milestone behavior is to store everything in the file system. So there are two things that should change in the future.

1. What artifact should we store? How do we identify which artifacts to be stored?
2. How and where we should we store the artifacts

The ideal answer to the second question is we should store them in the Continuous Integration system itself. Now that is easy!

Now answer to the first question. How to identify which artifacts to store. We are considering many apps with several versions being build many times a day. Simple answer this should be configurable. Some possibilities,

1. Store the latest build
2. Store a fixed number of builds 
3. Store builds for a fixed period
4. Store the latest builds and the ones that are marked explicitly by the devops/develoeprs

Well ...... there are many many options. But a combination of the 4th and 2nd option would be really interesting.

App Factory M2 Released!

We've been working hard on M2 release. It can be downloaded from here. These are the main features about this App Factory release.

1. Using App Factory M2, it is possible to develop an application with a data-source and move it across different life-cycle stages seamlessly
2. We have defined a set of interfaces that would enable us to plug different SDLC tooling and it has a better modular architecture that leverage the power of OSGi
3. Our VM packs a dehydrated version of WSO2 carbon servers with a P2 repo. And the setup script hydrates the servers using the P2 repo during the startup
4. M2 has a generic BPEL process that would deploy to different stages. This would enable us to have the power of configurable set of stages

The modular architecture introduced into App Factory M2 can be shown as below. 

The interfaces defined for SDLC tools are as follows.

• BuildDriver Interface - Enables to plugin different build mechanism. Talks to the build farm
• BuildDriverListener Interface - Listens to the events of the BuildDriver. This enables asynchronous architecture
• RevisionControlDriver Interface - Implementations of this interface are responsible to talk to different source code management systems.
• RevisionControlListener Interface - Listens to the events of the RevisionControlDriver
• ArtifactStorage Interface - This is where the built artifacts are stored. M2 ships with FileArtifactStorage
• ContinuousIntegrationSystemDriver - Implementations of these will talk to Jenkins and Bamboo

The services

• ArtifactCreator - This service is responsible for taking the source code check out and creating the artifact and once done it will call the BPEL back
• ApplicationDeployer - This service will deploy the artifact to the configured servers

That is all folks for M2. We'll do  more wonderful things for M3 !

App Factory

Recently I've been working on this new product called App Factory. This is how we envision it.

http://wso2.com/solutions/app-factory/

Creating roles inside Carbon for External LDAP Users

Step 1 : Configure the External LDAP



Step 2 : Click on "Test Connection" on the main User Management page. If connecting is not successful please reconfigure until successful connection is made.

Step 3 : Click on external roles. You will see "everyone" role. If you want to manage all users (external/internal), then everyone role contains all the users and their permissions. If you want to manage subset of users from the LDAP then go to next step to add a new external role.



Step 4 : Click on "Add New Internal Roles". Now we are going to create a new role in Carbon for external users. Give the new role a name, click next and select permissions. Finally search users from the external user store and add them to the role and click finish.



Now we are done! We have created role inside Carbon to manage users from external LDAP.

WSO2 Cloud Identity

WSO2 launched http://identity.cloud.wso2.com/

Here is my article on user management in the cloud
http://wso2.org/library/articles/idaas-managing-users

Enabling LDAP users to login to WSO2 Carbon

Applies to Products : WSAS, ESB, Identity Server, Greg, and other Carbon based products

Step 1 : Configure the external LDAP Server.



Step 2 : Click on "Test Connection" on the main User Management page. If connecting is not successful please reconfigure until successful connection is made.

Step 3 : If you want to authorize everyone in the LDAP to login click on "Edit Permissions" in the everyone role and assign desired permissions. Otherwise go to step 4.




Step 4 : You can manage authorization for a selected set of LDAP users by defining your own roles. Go to "External Roles">"Add new Internal Role" and add a new role as follows. Give "Login" permissions and other relevant permissions as follows.