The AOLA World of e-Activity: Mathematics Education

Mon, 24 Mar 2008 11:03:00 GMT

AOLA World reappears after almost a year of behind-the-scene activities...

Return of the A2ABlog

Mon, 24 Mar 2008 08:38:00 GMT

It has been more than one year since this blog was started. Other than upgrading this Pebble-enabled blog from version 1.9 to now 2.3, the underlying system has also been slowly evolving...

Anyhow, I am back and there are many things to talk about.

Linking ActivityML to Mathematical Web Services

Sat, 25 Aug 2007 03:48:16 GMT

Go directly to the AXIS2_HOME/samples/quickstart according to the 'Deploying POJOs' section, 'ant' was built (mainly un-zip/un-tar the downloaded package - version 1.7.0 and set the paths accordingly) and the build was successful.

The WSDL file was built and so is the StockQuoteService.aar. References to 'localhost:8080' in the WSDL file were modified to point to the real domainname. I don't think it has any effect with respect to using the StockQuote service.

Service saas001, based on the StockQuote Service, was deployed successfully after fixing some typos in the WSDL file. The service provides a conversion from an IpAddress to the Country of which this IpAddress is assigned by ICANN as update to a certain date when the database is created. Of course, there is no database associated at this time.

Next step is to deploy the other samples in the distribution, and then slowly pick up the finer details of axis2 (e.g., how to add the XSL for the responses)

Linking ActivityML to Mathematical Web Services

Thu, 23 Aug 2007 12:39:17 GMT

So many technology items to piece together before a service can be designed and 'made'. I am following the Quick Start Guide here:

A 4G IBM Blade Center Unit with dual processors (Xeon's)
RedHat
Tomcat 5.5.17
JDK 1.5.0_07
axis2-1.3
environment variable AXIS2_HOME points to /opt/axis2
compile the simple saas001.java based on the StockQuoteService at /opt/src
at /opt/src, do this

/opt/axis2/bin/java2wsdl.sh -cp . -cn A2A.computeEngine.services.algebra.saas001 -of saas001.wsdl
the saas001.wsdl is generated at /opt/src. Not sure where this WSDL file should go. In principle, this WSDL exposes the service for the broker to locate the service on behalf of a client.

And part of the WSDL file (raw; we need to modify some areas to reflect the true environment, e.g., domainname vs localhost):

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
  xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
  xmlns:ns0="http://algebra.services.computeEngine.A2A" 
  xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" 
  xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" 
  xmlns:ns1="http://org.apache.axis2/xsd" 
  xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" 
  xmlns:xs="http://www.w3.org/2001/XMLSchema" 
  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" 
  targetNamespace="http://algebra.services.computeEngine.A2A">
    <wsdl:types>
        <xs:schema xmlns:ns="http://algebra.services.computeEngine.A2A" 
  attributeFormDefault="qualified" 
  elementFormDefault="qualified" 
  targetNamespace="http://algebra.services.computeEngine.A2A">
            <xs:element name="getCountry">
                <xs:complexType>
                    <xs:sequence>
                        <xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
                    </xs:sequence>
                </xs:complexType>
            </xs:element>
            <xs:element name="getCountryResponse">
                <xs:complexType>
                    <xs:sequence>
                        <xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
                    </xs:sequence>
                </xs:complexType>
            </xs:element>
            <xs:element name="update">
                <xs:complexType>
                    <xs:sequence>
                        <xs:element minOccurs="0" name="param0" nillable="true" type="xs:string"/>
                        <xs:element minOccurs="0" name="param1" nillable="true" type="xs:string"/>
                    </xs:sequence>
                </xs:complexType>
            </xs:element>
        </xs:schema>
    </wsdl:types>
    <wsdl:message name="updateRequest">
        <wsdl:part name="parameters" element="ns0:update"/>
    </wsdl:message>
    <wsdl:message name="getCountryRequest">
        <wsdl:part name="parameters" element="ns0:getCountry"/>
    </wsdl:message>
    <wsdl:message name="getCountryResponse">
        <wsdl:part name="parameters" element="ns0:getCountryResponse"/>
    </wsdl:message>
    <wsdl:portType name="saas001PortType">
        <wsdl:operation name="update">
            <wsdl:input message="ns0:updateRequest" wsaw:Action="urn:update"/>
        </wsdl:operation>
        <wsdl:operation name="getCountry">
            <wsdl:input message="ns0:getCountryRequest" wsaw:Action="urn:getCountry"/>
            <wsdl:output message="ns0:getCountryResponse" wsaw:Action="urn:getCountryResponse"/>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="saas001SOAP11Binding" type="ns0:saas001PortType">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
        <wsdl:operation name="update">
            <soap:operation soapAction="urn:update" style="document"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
        </wsdl:operation>
        <wsdl:operation name="getCountry">
            <soap:operation soapAction="urn:getCountry" style="document"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="saas001SOAP12Binding" type="ns0:saas001PortType">
        <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
        <wsdl:operation name="update">
            <soap12:operation soapAction="urn:update" style="document"/>
            <wsdl:input>
                <soap12:body use="literal"/>
            </wsdl:input>
        </wsdl:operation>
        <wsdl:operation name="getCountry">
            <soap12:operation soapAction="urn:getCountry" style="document"/>
            <wsdl:input>
                <soap12:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap12:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="saas001HttpBinding" type="ns0:saas001PortType">
        <http:binding verb="POST"/>
        <wsdl:operation name="update">
            <http:operation location="saas001/update"/>
            <wsdl:input>
                <mime:content type="text/xml" part="update"/>
            </wsdl:input>
        </wsdl:operation>
        <wsdl:operation name="getCountry">
            <http:operation location="saas001/getCountry"/>
            <wsdl:input>
                <mime:content type="text/xml" part="getCountry"/>
            </wsdl:input>
            <wsdl:output>
                <mime:content type="text/xml" part="getCountry"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="saas001">
        <wsdl:port name="saas001SOAP11port_http" binding="ns0:saas001SOAP11Binding">
            <soap:address location="http://localhost:8080/axis2/services/saas001"/>
        </wsdl:port>
        <wsdl:port name="saas001SOAP12port_http" binding="ns0:saas001SOAP12Binding">
            <soap12:address location="http://localhost:8080/axis2/services/saas001"/>
        </wsdl:port>
        <wsdl:port name="saas001Httpport" binding="ns0:saas001HttpBinding">
            <http:address location="http://localhost:8080/axis2/services/saas001"/>
        </wsdl:port>
    </wsdl:service>
</wsdl:definitions>

Ok, for each service, axis2 imposes a structure to be followed packaged in a 'aar' file. In our case, we have:


- saas001
   - META-INF
     - services.xml
   - lib
   - A2A
     - computerEngine
       - services
         - algebra
           - saas001.class

The services.xml file should contain the following information:

<service name="saas001" scope="application">
    <description>
        Conversion of IP to Country Service
    </description>
    <messageReceivers>
        <messageReceiver
            mep="http://www.w3.org/2004/08/wsdl/in-only"
    class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>
        <messageReceiver
            mep="http://www.w3.org/2004/08/wsdl/in-out"
    class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
    </messageReceivers>
    <parameter name="ServiceClass">
        A2A.computerEngine.services.algebra.saas001
    </parameter>
</service>

The file at /opt/jakarta/webapps/axis2/WEB-INF/conf/axis2.xml is modified with the following specific (to my environment) information and other changes as a result:

I changed the password to username 'admin' for the admin page to that the same as for 'aola'.
No change to /opt/jakarta/webapps/axis2/WEB-INF/web.xml for now. Axis2 repository path can be defined here.
saas001.wsdl has been modified by replacing the 'localhost:8080' references with 'blueberry.ccl.baf.cuhk.edu.hk'; there is a reference to Namespace of 'http://algebra.services.computeEngine.A2A' that should be defined or changed.
Create the /opt/WebLOGs/ directory to hold the log4j logs (e.g., in /opt/jakarta/webapps/axis2/WEB-INF/classes/log4j.properties now points to /opt/WebLOGs/axis2.log)

I think I know what needs to be done, but let me try the basic setup first.

STOP, let me try the samples that come with the release...

Linking ActivityML to Mathematical Web Services

Wed, 22 Aug 2007 12:20:51 GMT

Taking a lesson plan and realize it as a portable XML-based document can now be done with the activityEditor. With an activityML lesson, the AOLA environment now brings the lesson live in the ePlatform. The next missing step is the discoverable mathematical services to render on-demand graphical mathematics (some form of dynamic mathematics) and to provide the computational engine for dynamic mathematics in real-time.

In this posting, we learn how to use axis2 to create an online environment to create a proof-of-concept Saas (software as a service) for AOLA mathematics learning.

The next few postings will be the deployment of a simple computational engine that provides Saas to an activityML lesson.

Sung-Chi's Blog - AOLA category

The AOLA World of e-Activity: Mathematics Education

Return of the A2ABlog

Linking ActivityML to Mathematical Web Services

Linking ActivityML to Mathematical Web Services

Linking ActivityML to Mathematical Web Services