[Download] | [Documentation Home] | [Release Note]
This installation guide provides information on,
This document explains how Task Server should be installed & run in standalone mode
WSO2 Task Server in Standalone Mode
WSO2 Task Server is a lightweight server to schedule remotely triggered web tasks
WSO2 Task Server is distributed in several convenient distribution packages, and can be installed either as a standalone server or as part of a J2EE compliant servlet container. WSO2 Task Server is distributed under the Apache License, version 2.0.
Java Runtime Environment | 1.5 or higher (For instructions on setting up the JRE in different operating systems, visithttp://java.sun.com) |
Memory | 256MB |
Disk |
Approximately 100 MB will be used for the .zip distribution |
Operating System | Tested on Windows XP, Linux, Mac OS X, Fedora core, Ubuntu, Gentoo |
The Management Console requires full Javascript enablement of the Web browser NOTE: On Windows Server 2003, it is not allowed to go below the medium security level in Internet Explorer 6.x. For more details see http://wso2.org/wiki/display/carbon/System+Requirements |
You can use the install.bat file in the Task Server distribution to install Data Services Server as a Windows NT service. This installation script is available at CARBON_HOME/bin.
Here are the steps:
Once you add WSO2 Task Server as an NT service to Windows services, you can start this service from Services in Administrative tools of the Control Panel.
Check your WSO2 Task Server instance using the URL https://localhost:9443/carbon/
On MS Windows systems, to remove the Task Server Windows NT service;
Once WSO2 Task Server has been successfully installed, in order to access the Management Console, first start the server, launch a web browser instance, and then point it to the URL https://localhost:9443/carbon/ (if you are using the default settings). This will take you to the "Sign In" page of the Management Console.
Note: By default, WSO2 Task Server has two listeners, HTTP and HTTPS. The HTTP listener opens on port 9763, while the HTTPS listener opens on port 9443. The administrator functions are exposed only via the HTTPS port.
For details on WSO2 Task Server Management Console see the User Guide