WSO2 just released a newer version of the popular web services framework for php (WSF/PHP). It has lot of bug fixes + performance improvement. And it now support PHP 5.3. So you can use wsf/php with the latest php version.
You can download the new release from http://wso2.org/downloads/wsf/php.
WSO2 announced that the SOA stack that they provided as downloadable packages are now available in the cloud as hosted instances with the code name WSO2 Stratos. You can try them out for free from https://cloud.wso2.com. You can register your organization for an account in the WSO2 Stratos by clicking the ‘Register’ button in the home page. You can find a detail guide on ‘How to register for WSO2 Stratos’ from Charitha’s blog, http://charithaka.blogspot.com/2010/06/wso2-stratos-introducing-wso2.html.
At the registration, you will be asked to provide a username and password for the admin account. Use this credential to login as admin for the Stratos services and surf through the products. Here is a brief introduction on all the products currently available.
With this release WSO2 bring complete SOA stack to the cloud, Now your enterprise can enjoy the power of SOA without the hassle of maintaining your own SOA infrastructure.
WSO2 and Zend jointly present a webinar titling “PHP Web Services: Why You Should Care” on 26th of May, 2010. The webinar will mainly focus on the following aspects,
• Understand Web services development best practices
• Discuss Web service myths and pitfalls
• Learn about prominent PHP Web services extensions
• Watch a demo of building Web Services with both the Zend Framework and WSO2 Web Services Framework for PHP.
You can find more information about the webinar and the link to registration here, http://wso2.org/library/webinars/2010/05/webinar-php-web-services-you-should-care.
WSO2 has released new versions of their SOA platform products including WSO2 Governance Registry, WSO2 Identity Server, WSO2 ESB, WSO2 Web Service Application Server. This is a major version upgrade of these products introducing many features.
ESB:
Web Service Application Server (WSO2 WSAS):
Samisa Abeysinghe, the directory of engineering at WSO2 will present a webinar on Building an Agile Enterprise With Business Activity Monitoring today (3rd February 2010).
There he will provide an overview of WSO2 Business Activity Monitor (WSO2 BAM), the latest product from the WSO2 Carbon platform, including its built-in dashboard to view analytics , reports of past and present activities of the enterprise SOA infrastructure and how these information can be used in tactical and strategic decision making.
WSO2 Governance as a Service is a hosted instance of WSO2 Governance Registry with multi-tenant support. WSO2 Governance as a Service provide you almost all the functionalities provided with the Governance Registry targeting the enterprise SOA governance, same time it provides all the advantages inherent with the Software as a Service model.
Here I’m talking about how to use a popular feature available in Governance Registry, inside WSO2 Governance as a Service. i.e. Remote Registry Client. With Remote Registry Client, you can access the resources in registry programatically. It uses atom/pub protocol to communicate with the registry server.
Here is an example of using Remote Registry Client. I assumed I have an account with domain name ‘example.com’ with a user name ‘example_user’ (‘example_password’). You have to change this to valid values before running this code, You can create an account in Governance as a Service freely for a limited use.
import java.net.URL; import org.wso2.carbon.registry.core.Registry; import org.wso2.carbon.registry.core.Resource; import org.wso2.carbon.registry.app.RemoteRegistry; class RegistryDemo { public static void main(String[] args) throws Exception { // calls the registry with the authentication information callRemoteRegistry("http://governance.cloud.wso2.com/registry", "example_username@example.com", "example_password"); } public static void callRemoteRegistry(String url, String username, String password) throws Exception { Registry myRegistry = new RemoteRegistry(new URL(url), username, password); if (!myRegistry.resourceExists("/demoResource")) { Resource r = myRegistry.newResource(); r.setContent("demo content"); myRegistry.put("/demoResource", r); } Resource r = myRegistry.get("/demoResource"); byte[] contentBytes = (byte[])r.getContent(); String content = new String(contentBytes); System.out.println("Content: " + content); } }
Here is a problem that many people have asked me how to do it. “Returning an array of string” with the code first approach. The API or WSDL generation annotation guide, http://wso2.org/project/wsf/php/2.0.0/docs/wsdl_generation_api.html contain all the things required in details. Here is an example of a service that return an array of string.
<?php /** splitMe function * @param string $string_to_split string to split * (maps to the xs:string XML schema type ) * @return array of string $result split to array *(maps to the xs:double XML schema type ) */ function splitMe($string_to_split) { return array("result" => split(":", $string_to_split)); } $operations = array("splitMe"=>"splitMe"); $opParams = array("splitMe"=>"MIXED"); $svr = new WSService(array("operations"=>$operations, "bindingStyle"=>"doclit", "opParams"=>$opParams)); $svr->reply(); ?>
Note that the annotation corresponding to the return value.
* @return array of spring $result split to array
This will generate an schema with an element of maxOccurs=’unbounded’. Note that you can get the wsdl from the ‘serviceurl?wsdl’.
<xsd:element name="splitMeResponse"> <xsd:complexType> <xsd:sequence> <xsd:element name="result" maxOccurs="unbounded" type="xsd:string"/> </xsd:sequence> </xsd:complexType> </xsd:element>
Now just generate a client for this service using wsdl2php and try invoke it. You will get an array of string as the response.
$input = new splitMe(); $input->string_to_split = "a:b:c:d"; // call the operation $response = $proxy->splitMe($input); print_r($response);
If you want to write rules in a Java program you have lot of choices. You can use a third party library like Drools or use the JAVA built-in JSR-94 reference implementation. In WSO2 Carbon, there is a component that abstract the behaviour of different rule engine and give you a unified API. Currently it has plugged into Drools and JAVA built-in JSR-94 implementation.
The rule component in WSO2 Carbon platform mainly used by WSO2 ESB product to mediate messages according to the given business rules. But the component is written to facilitate any requirement of using business rules in WSO2 Carbon platform. I had such a requirement in past few days and manage to use the rule component easily with the help of the component author, indika@wso2.com. So I thought it is worth sharing my experience in here.
Here You will be preparing the following stuff.
1. Rule configuration -
We can use this to provide the information about the rule implementation we are going to use, the rules (You can write rules inline or provide a reference to an external file) and the input and output adapter information.
<configuration xmlns="http://www.wso2.org/products/rule/drools"> <executionSet uri="simpleItemRuleXML"> <source key="file:src/test/resources/rules/simple-rules.drl"/> <!-- <source> <x><![CDATA[ rule InvokeABC // rules inbuilt to the rule conf end ]]> </x> </source> --> <creation> <property name="source" value="drl"/> </creation> </executionSet> <session type="stateless"/> <input name="facts" type="itemData" key="dataContext"></input> <output name="results" type="itemData" key="dataContext"></output> </configuration>
2. The Rules -
You can write rules inline in the above configuration or put it in a file and refer it from a key which can be refered from the ResourceHelper (described below).
import java.util.Calendar; rule YearEndDiscount when $item : org.test.pojo.SimpleItem(price > 100 ) then Calendar calendar = Calendar.getInstance(); if (calendar.get(Calendar.MONTH) == Calendar.JANUARY) { $item.setPrice($item.getPrice() * 80/100); } end
3. Data Context -
The context object that can be used to feed and retrieve data from and to rule engine. Here is the data context for my application.
public class SimpleDataContext { public List<NameValuePair> getInput() { // in reality the data will be retrieve from a database or some datasource List<NameValuePair> itemPairList = new ArrayList<NameValuePair>(); SimpleItem item1 = new SimpleItem(); item1.setName("item1"); item1.setPrice(50); itemPairList.add(new NameValuePair(item1.getName(), item1)); SimpleItem item2 = new SimpleItem(); item2.setName("item2"); item2.setPrice(120); itemPairList.add(new NameValuePair(item2.getName(), item2)); SimpleItem item3 = new SimpleItem(); item3.setName("item3"); item3.setPrice(130); itemPairList.add(new NameValuePair(item3.getName(), item3)); return itemPairList; } public void setResult(Object result) { if (!(result instanceof SimpleItem)) { System.out.println("it is not a SimpleItem"); } SimpleItem item = (SimpleItem)result; System.out.println("Item: " + item.getName() + ", Price: " + item.getPrice()); } }
And the Item I’m going to manipulate using rule is a simple bean like this,
public class SimpleItem { String name; int price; public String getName() { return name; } public void setName(String name) { this.name = name; } public int getPrice() { return price; } public void setPrice(int price) { this.price = price; } }
4. Data Adapter
You have to adapt the input and output with the rule engine. Mostly here you only have to wrap the data context. The advantage of having the data adapter is, a data adapter always associated with a input/output type. So in the rule configuration I can provide the type for the input and output. If you see my rule configuration above, you see the input/output type is marked as “ItemData”. Here is my custom data adapter that is associated with the “itemData” type.
public class SimpleDataAdapter implements ResourceAdapter, InputAdaptable, OutputAdaptable { // the type associated with the adapter private final static String TYPE = "itemData"; public String getType() { return TYPE; } public Object adaptInput(ResourceDescription resourceDescription, Object tobeadapted) { if (!(tobeadapted instanceof SimpleDataContext)) { return null; } SimpleDataContext dataContext = (SimpleDataContext)tobeadapted; return dataContext.getInput(); } public boolean adaptOutput(ResourceDescription description, Object value, Object context, ResourceHelper resourceHelper) { if (!(context instanceof SimpleDataContext)) { return false; } ((SimpleDataContext)context).setResult(value); return true; } public boolean canAdapt(ResourceDescription description, Object ouptput) { String key = description.getKey(); return key != null && !"".equals(key); } }
5. Resource Helper
Resource Helper will map the keys refered from the configuration to JAVA objects. This is mostly used in mediation rule configurations which can extract the message data using a key or an xpath. In this example, we don’t have much keys refering from the configuration only the rule file and the data context.
public class SimpleResourceHelper extends ResourceHelper { public ReturnValue findByKey(String key, Object source, Object defaultValue) { if (!(source instanceof SimpleDataContext)) { return new ReturnValue(defaultValue); } SimpleDataContext dataContext = (SimpleDataContext)source; if (key.startsWith("file:")) { String filename = key.substring("file:".length()); try { BufferedInputStream in = new BufferedInputStream(new FileInputStream(filename)); return new ReturnValue(in); } catch (Exception e) { return new ReturnValue(defaultValue); } } if (key.startsWith("dataContext")) { return new ReturnValue(dataContext); } return new ReturnValue(defaultValue); } // there are few more methods to be implemented, which can just leave not implemented for this example } }
That is all the accessories. Now you will be able to write the rule engine execution code.
File ruleConfigFile = new File(ruleConfigFilename); XMLStreamReader parser = XMLInputFactory.newInstance().createXMLStreamReader(new FileInputStream(ruleConfigFile)); //create the builder StAXOMBuilder builder = new StAXOMBuilder(parser); //get the root element (in this case the envelope) OMElement ruleConfig = builder.getDocumentElement(); EngineConfiguration configuration = new EngineConfigurationFactory().create(ruleConfig, new AXIOMXPathFactory()); EngineController engineController = new EngineController(configuration, new SimpleResourceHelper()); final ResourceAdapterFactory factory = ResourceAdapterFactory.getInstance(); ResourceAdapter adapter = new SimpleDataAdapter(); String adapterType = adapter.getType(); if (!factory.containsResourceAdapter(adapterType)) { factory.addResourceAdapter(adapter); } SimpleDataContext simpleContext = new SimpleDataContext(); if (!engineController.isInitialized()) { engineController.init(simpleContext); } if (engineController.isInitialized()) { engineController.execute(simpleContext, simpleContext); }
WSO2 Governance as a Service is an online multi-tenant supported instance of WSO2 Governance Registry which is the solution for SOA Governance from the WSO2 SOA stack. You can start trying out WSO2 Governance as a Service by accessing the http://governance.cloud.wso2.com and creating an account for your organization (free for limited use).
In order to identify your account, you have to provide the domain name of your organization. I will demonstrate how to create an account using the “ws.dimuthu.org” as my domain name.
1. First go to http://governance.cloud.wso2.com from a web browser and click the ‘Register’ button. You will be asked to enter the domain name as the first step.
Enter the domain
After that, you have the option of validating the ownership of the domain right at the registration process, or you can skip the validation and continue to the next step in which case your domain will be appended ‘-trial’ suffix. You can validate the ownership of the domain later at any stage.
Here I want to validate the domain right now, so I click ‘Take me to the domain ownership confirmation page straight-away’ and click the ‘Submit’ button.
2. This will redirect you to the domain ownership validation page. You can validate the ownership of your domain in one of two ways.
Method i). Just create a text file named ‘wso2gaas.txt’ in the web root of your domain and enter the given text. This is the most simplest method of two.
Validate domain name using Textfile
Method ii). You can put a DNS entry according to the given instructions. This is a little tedious approch to validate the domain. In fact it may take a while to propagate the new DNS information, so you may have to wait hours without refreshing the page until you finally validate the domain ownership.
Click the continue button after the domain validation done. Then you will be redirected to a page requesting more information.
3. Tenant Registration Page
Tenant Registration
4) After this step, you will be notified to check for your email which will contain a mail with a link to proceed with the registration. There you will be able to select a theme for your organization and finalize creating your account. Login to the admin account for your tenant with the credential you provided a the time of the registration.
The domain ownership validation was introduced to WSO2 Governance as a Service account registration only now. So for organizations who have already have account will have a message similar to this when they are trying to login to their account.
Info box at login
So the account I have registered using the domain name ‘example.com’ has been renamed to ‘example.com-trial’. As the instruction of the message says you can go to the account management page after the login and validate the domain ownership.
Account Management Page