The Middleware as Platform for IT Application Services
In order to use OpenSOAP, make the appropriate selections depending on your objectives.
To run any applications built using OpenSOAP, shared libraries(lib*.so) or
When developing applications using the OpenSOAP middleware header files(OpenSOAP/*.h) and static libraries(lib*.a or *.LIB) (ie. OpenSOAP API), or when using OpenSOAP applications created by third parties, it may be necessary to compile source code.
Web Service applications implemented using OpenSOAP. Sample programs for the basic Transaction Service and Soaping Client/Service tools are included in the package.
This is the server that implements the special features available using OpenSOAP.
The server implements request reception from client, transfer to Web Service program, message management,
asynchronous processing, message routing, etc.
OpenSOAP includes Security module using an SSL library, but this is NOT required for the execution or development environments. If the security features or the SSL library are not required, it is not necessary to include them. However, the Server requires the Security module.
For installation, a pre-compiled ready to run binary package, or a source code package requiring compilation are available.
If the binary package for your environment is not available, compilation will be necessary. Please make sure that you have the
appropriate compilation tools available.
Source Code Package
In UNIX type systems (including Cygwin) make is possible by using the configure script.
For Windows systems, project files for Visual C++ 6.0 are included. Please see the documentation for more details.
Currently the following binary packages are available
RPM (RedHat Package Manager) Source/Binary Package
The package is divided into the following sub-packages. To install 2, 3, 4 the sub-package 1 is required.
To install, first download the required packages, and then execute the following commands as root.
# rpm -ivh opensoap-1.0_20030228-2.i386.rpm # rpm -ivh opensoap-*1.0_20030228-2.i386.rpm (To install multiple packages at once) # rpm -Uvh opensoap-*1.0_20030228-2.i386.rpm (Use this command to update existing packages)
The binary packages presented here are for RedHat7.3 and 8.0 for the Intel386 architecture. These may not run under other distributions, and if so, rebuild the package using the separate source RPM. In this case, to compile the samples, the opensoap-devel package must be installed, and to do this, first comment the samples section in the opensoap-spec file, then build and install the binary packages (opensoap, opensoap-devel). To build the opensoap-samples packages, uncomment the samples section in the spec file and build the package. The execution procedure is as follows:
$ rpm -vih opensoap-1.0_20030228-2.src.rpm $ cd ~/src/rpm (current user's %_topdir) $ cp SPECS/opensoap.spec SPECS/opensoap-nosamples.spec $ vi SPECS/opensoap-nosamples.spec (Comment out the section enclosed by "#### samples") $ rpmbuild -ba SPECS/opensoap-nosamples.spec (Build with samples excluded) $ sudo rpm -vih RPM/i386/opensoap-*1.0_20030228-2.i386.rpm (As root install opensoap, -devel, -server except samples) $ rpmbuild -ba SPECS/opensoap.spec (With opensoap-devel installed, rebuild all)
Vine Plus Package
Linux (i386) tgz package
This requires the installation of libxml2 and openssl. Unpacking the tar+gz compressed file in the root directory will create the directories /usr/local/opensoap and /home/httpd/cgi-bin, and will copy the appropriate files to these directories. As the cgi-based services require the existence of a HTTP server supporting CGI, the CGI directory can be set to /home/httpd/cgi-bin or the files should be copied to an already existing CGI directory.
# tar zxvf opensoap-1.0-20030201.linux.i386.bin.tar.gz -C / (....Unpack the files) # /usr/local/opensoap/sbin/opensoap-server-ctl start (....OpenSOAP start up) # /usr/local/opensoap/bin/Soaping localhost (Soaping Service call verification) # /usr/local/opensoap/bin/Soaping -o localhost (Soaping Service called through the OpenSOAP Server)
A sample package containing the excution environment,development environment and OpenSOAP Server is available and also contains some sample programs ready to run.
The security libraries(libOpenSOAPSecurity.*) are dynamically linked to libcrypto.so.2, but in Debian and other systems, this library name may not be recognised. Using openssl-0.9.6 execution is possible, so by creating a symbolic link, operation should be possible.
# ldd /usr/local/opensoap/lib/libOpenSOAPSecurity.so libcrypto.so.2 => not found libpthread.so.0 => /lib/libpthread.so.0 (0x40014000) libc.so.6 => /lib/libc.so.6 (0x40029000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) # cd /usr/lib # ls -l libcrypto.so* lrwxrwxrwx 1 root ..... libcrypto.so -> libcrypto.so.0.9.6 -rw-r--r-- 1 root ..... libcrypto.so.0.9.6 # ln -s libcrypto.so.0.9.6 libcrypto.so.2 # ldd /usr/local/opensoap/lib/libOpenSOAPSecurity.so libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x40014000) libpthread.so.0 => /lib/libpthread.so.0 (0x400d5000) libc.so.6 => /lib/libc.so.6 (0x400ea000) libdl.so.2 => /lib/libdl.so.2 (0x40207000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
It is hoped that RedHat rpm and Debian deb packages can also be made available in the future.
For Windows installations, the seperately available pre-compiled libxml2 libraries are required. Also, in order to use the security features the OpenSSL libraries are required. Both these libraries have been compiled and verified under MS Windows2000.
Copyright (C) 2001-2004 Webmasters of www.opensoap.jp. All Rights Reserved.