April 30th, 2008, 12:55 pm
Portus - Installation and Deployment
Firstly, to draw the lines between the Eclipse installation, and the server
installation. The Eclipse Control Centre is used to deploy server installation
files to the server machine. This is the same process for all users, whether
they are installing on Windows, Linux, z/OS HP-UX. etc. Once the server has
been deployed, no matter what platform the server runs on, we still use the
Eclipse Control Centre to configure and administrator the server.
The Eclipse installation is pretty straightforward,
just extract and run. The server deployment is a 2 step process. First step, you
must choose & deploy the server installation you want. In the case of HPUX, we
simply FTP the required server files, and the chosen
license to the server machine. The 2nd step of this process is to logon to the
server machine and run the scripts or JCL (for z/OS) to install the server. As part of this
installation process, we install our own version of an apache webserver, running
on a HTTP port you choose at deployment. Everything lives under the directory / dataset
you specify, so absolutely no changes are made to existing Apaches.
Once the server is up and running, the deployment wizard will then take you to
the next step, which will configure the Portus drivers based on your
license. Our software is designed around a central engine, which then loads
specific drivers based on your licensing model. These drivers are the mapping
between the engine and the datasource you want to access, for example, COBOL,
MySQL, DB2, Natural, etc.
Once Portus has been deployed and configured, the next step is to begin
creating web services. Again, the Eclipse Control Centre is central to this
process. We provide a "Discovery Wizard" which will allow you to browse for the
required programs / databases, and create web services from these. To enable all sorts of different clients to access this web service, we provide a WSDL describing how this service is to be accessed. This WDSL is conforms to the WS-I Profile 1.0, and is in a completely standard, non-proprietary format.
Once the web service is up and running - it is time start using it ... gentlemen ... choose your web service client .... C#, Java, PHP, Ruby, MS Excel, MS Word, MS Infopath, Firefox, Internet explorer, soapUI, JSP, ADO. NET ... and many more!!
installation. The Eclipse Control Centre is used to deploy server installation
files to the server machine. This is the same process for all users, whether
they are installing on Windows, Linux, z/OS HP-UX. etc. Once the server has
been deployed, no matter what platform the server runs on, we still use the
Eclipse Control Centre to configure and administrator the server.
The Eclipse installation is pretty straightforward,
just extract and run. The server deployment is a 2 step process. First step, you
must choose & deploy the server installation you want. In the case of HPUX, we
simply FTP the required server files, and the chosen
license to the server machine. The 2nd step of this process is to logon to the
server machine and run the scripts or JCL (for z/OS) to install the server. As part of this
installation process, we install our own version of an apache webserver, running
on a HTTP port you choose at deployment. Everything lives under the directory / dataset
you specify, so absolutely no changes are made to existing Apaches.
Once the server is up and running, the deployment wizard will then take you to
the next step, which will configure the Portus drivers based on your
license. Our software is designed around a central engine, which then loads
specific drivers based on your licensing model. These drivers are the mapping
between the engine and the datasource you want to access, for example, COBOL,
MySQL, DB2, Natural, etc.
Once Portus has been deployed and configured, the next step is to begin
creating web services. Again, the Eclipse Control Centre is central to this
process. We provide a "Discovery Wizard" which will allow you to browse for the
required programs / databases, and create web services from these. To enable all sorts of different clients to access this web service, we provide a WSDL describing how this service is to be accessed. This WDSL is conforms to the WS-I Profile 1.0, and is in a completely standard, non-proprietary format.
Once the web service is up and running - it is time start using it ... gentlemen ... choose your web service client .... C#, Java, PHP, Ruby, MS Excel, MS Word, MS Infopath, Firefox, Internet explorer, soapUI, JSP, ADO. NET ... and many more!!