Author: dumindu
Date: Mon Apr 30 05:50:29 2007
New Revision: 533730
URL: http://svn.apache.org/viewvc?view=rev&rev=533730
Log:
updated the win32 build.
added win32 installation instructions.
Modified:
webservices/rampart/trunk/c/INSTALL
webservices/rampart/trunk/c/build/win32/makefile
webservices/rampart/trunk/c/samples/client/sec_echo/deploy_client_repo.bat
Modified: webservices/rampart/trunk/c/INSTALL
URL:
http://svn.apache.org/viewvc/webservices/rampart/trunk/c/INSTALL?view=diff&rev=533730&r1=533729&r2=533730
==============================================================================
--- webservices/rampart/trunk/c/INSTALL (original)
+++ webservices/rampart/trunk/c/INSTALL Mon Apr 30 05:50:29 2007
@@ -1,66 +1,114 @@
-Table of contents
-============================================
- |_ Getting Rampart/C source working on Linux
- |_ Getting Rampart/C binary distribution working on Linux
- |_ Engage Rampart/C with axis2/C
-
-
-Getting Rampart/C source working on Linux
-============================================
-Build the source
-
-This can be done using the following command sequence:
- ./configure --prefix=${AXIS2C_HOME} --enable-static=no
--with-axis2=${AXIS2C_HOME}/include/axis2-1.0
- make
- make install
-
-If you need to try samples, you need to build them.
- -Go to samples and run the script build.sh
- -Then go to samples/secpolicy and try a scenario
- %sh test_scen.sh scenarioX server-port
-
-Getting Rampart/C binary distribution working on Linux
-============================================
-1. Copy modules/rampart to $AXIS2C_HOME/modules
-2. Copy samples/server/sec_echo to $AXIS2C_HOME/services/
-3. Engage rampart as described in section "Engage Rampart/C with axis2/C"
-4. Go to samples/client/sec_echo/ and deploy the client repo
- %sh deploy_client_repo.sh
-5. Go to samples/secpolicy/ and try a scenario
- %sh test_scen.sh scenarioX server-port
-
-
-Engage Rampart/C with axis2/C
-============================================
-Prerequisites:
-You must have openssl installed in you system.
-
-Configuring:
-You can angage Rampart/C in global level or in service level.
-Just add following entry either to axis2.xml(gloabl level) or in
services.xml(service level).
- <module ref="rampart"/>
-
-Apart from that you must define security policies for outgoing messages and
incoming messages.
-This can be done adding parameters as follows in the same descriptor file that
you engaged rampart.
- <parameter
name="OutflowSecurityPolicy">/your/path/to/outgoing-secpolicy.xml</parameter>
- <parameter
name="InflowSecurityPolicy">/your/path/to/incoming-secpolicy.xml</parameter>
-
-NOTE: There are several samples security policy xml files for different
scenarios under samples/secpolicy/
- Please refer the README file for more information
-
-The final configuration setup should be as follows
-CLIENT SIDE:
-axis2.xml
- |-------------------> <module ref="rampart"/>
- |-------------------> <parameter
name="OutflowSecurityPolicy">/../../outgoing-secpolicy.xml</parameter>
- |-------------------> <parameter
name="InflowSecurityPolicy">/../../incoming-secpolicy.xml</parameter>
-
-SERVER SIDE:
-services.xml(or axis2.xml)
- |-------------------> <module ref="rampart"/>
- |-------------------> <parameter
name="OutflowSecurityPolicy">/../../outgoing-secpolicy.xml</parameter>
- |-------------------> <parameter
name="InflowSecurityPolicy">/../../incoming-secpolicy.xml</parameter>
-
-
-
-Thank you for using Rampart/C
+Table of contents
+=================
+ |_ Getting Rampart/C source working on Linux
+ |_ Getting Rampart/C binary distribution working on Linux
+ |_ Getting Rampart/C source working on Win32
+ |_ Getting Rampart/C binary working on Win32
+ |_ Engage Rampart/C with axis2/C
+ |_ Trying out the samples in Win32
+
+
+Getting Rampart/C source working on Linux
+=========================================
+Build the source
+
+This can be done using the following command sequence:
+ ./configure --prefix=${AXIS2C_HOME} --enable-static=no
--with-axis2=${AXIS2C_HOME}/include/axis2-1.0
+ make
+ make install
+
+If you need to try samples, you need to build them.
+ -Go to samples and run the script build.sh
+ -Then go to samples/secpolicy and try a scenario
+ %sh test_scen.sh scenarioX server-port
+
+Getting Rampart/C binary distribution working on Linux
+======================================================
+1. Copy modules/rampart to $AXIS2C_HOME/modules
+2. Copy samples/server/sec_echo to $AXIS2C_HOME/services/
+3. Engage rampart as described in section "Engage Rampart/C with axis2/C"
+4. Go to samples/client/sec_echo/ and deploy the client repo
+ %sh deploy_client_repo.sh
+5. Go to samples/secpolicy/ and try a scenario
+ %sh test_scen.sh scenarioX server-port
+
+Getting Rampart/C source working on Win32
+=========================================
+
+1. Set the AXIS2C_HOME envirionment variable to direct to your Axis2/C
Installation.
+ SET AXIS2C_HOME=[your-path-to-axis2c]
+
+2. Extract the source package and build the source.
+ Unzip the source package.
+ Go to the root of the distribution.
+ Run "nmake install"
+
+3. Engage Rampart/C with Axis2/C as described in the "Engaging Rampart/C with
axis2/C" section.
+
+
+Getting Rampart/C binary distribution working on Win32
+======================================================
+
+1. Set the AXIS2C_HOME envirionment variable to direct to your Axis2/C
Installation.
+ SET AXIS2C_HOME=[your-path-to-axis2c]
+
+2. Run the deploy_rampart.bat that could be found in the root of the rampart
binary distribution.
+ deploy_rampart.bat
+
+3. Engage Rampart/C with Axis2/C as described in the "Engaging Rampart/C with
axis2/C" section.
+
+Engaging Rampart/C with axis2/C
+===============================
+Prerequisites:
+You must have openssl installed in you system.
+
+Configuring:
+You can engage Rampart/C in global level or in service level.
+Just add following entry either to axis2.xml(gloabl level) or in
services.xml(service level).
+ <module ref="rampart"/>
+
+Apart from that you must define security policies for outgoing messages and
incoming messages.
+This can be done adding parameters as follows in the same descriptor file that
you engaged rampart.
+ <parameter
name="OutflowSecurityPolicy">/your/path/to/outgoing-secpolicy.xml</parameter>
+ <parameter
name="InflowSecurityPolicy">/your/path/to/incoming-secpolicy.xml</parameter>
+
+NOTE: There are several samples security policy xml files for different
scenarios under samples/secpolicy/
+ Please refer the README file for more information
+
+The final configuration setup should be as follows
+CLIENT SIDE:
+axis2.xml
+ |-------------------> <module ref="rampart"/>
+ |-------------------> <parameter
name="OutflowSecurityPolicy">/../../outgoing-secpolicy.xml</parameter>
+ |-------------------> <parameter
name="InflowSecurityPolicy">/../../incoming-secpolicy.xml</parameter>
+
+SERVER SIDE:
+services.xml(or axis2.xml)
+ |-------------------> <module ref="rampart"/>
+ |-------------------> <parameter
name="OutflowSecurityPolicy">/../../outgoing-secpolicy.xml</parameter>
+ |-------------------> <parameter
name="InflowSecurityPolicy">/../../incoming-secpolicy.xml</parameter>
+
+
+Trying out the samples on Win32
+===============================
+
+There are 9 scenarios that you can try out with the sec_echo sample of the
Rampart/C distribution.
+You can find more about it from the README.TXT file inside samples\secpolicy
folder.
+
+1. Set the AXIS2C_HOME envirionment variable to direct to your Axis2/C
Installation.
+ SET AXIS2C_HOME=[your-path-to-axis2c]
+
+2. Run the deploy_client_repo.bat file found in the samples\client\sec_echo
folder.
+ This will create an axis2 client repository for the samples in the
AXIS2C_HOME\clientrepo directory.
+
+3. Set the outflow and inflow secpolicy parameters in axis2.xml of the client
repo, according to the scenario that you are running.
+ <parameter
name="OutflowSecurityPolicy">D:\rampart-bin-0.90-win32\samples\secpolicy\scenario1\client-outgoing-secpolicy.xml</parameter>
+ <parameter
name="InflowSecurityPolicy">D:\rampart-bin-0.90-win32\samples\secpolicy\scenario1\client-incoming-secpolicy.xml</parameter>
+
+4. Set the outflow and inflow secpolicy parameters in services.xml of the
sec_echo service in the axis2 server repo.
+ <parameter
name="OutflowSecurityPolicy">D:\rampart-bin-0.90-win32\samples\secpolicy\scenario1\service-outgoing-secpolicy.xml</parameter>
+ <parameter
name="InflowSecurityPolicy">D:\rampart-bin-0.90-win32\samples\secpolicy\scenario1\service-incoming-secpolicy.xml</parameter>
+
+NOTE: In steps 3 & 4 you have to use the corresponding scenario files in each
parameter. For example if you are running the sample scenario 3, all the files
should be from scenario 3.
+
+Thank you for using Rampart/C
Modified: webservices/rampart/trunk/c/build/win32/makefile
URL:
http://svn.apache.org/viewvc/webservices/rampart/trunk/c/build/win32/makefile?view=diff&rev=533730&r1=533729&r2=533730
==============================================================================
--- webservices/rampart/trunk/c/build/win32/makefile (original)
+++ webservices/rampart/trunk/c/build/win32/makefile Mon Apr 30 05:50:29 2007
@@ -6,8 +6,9 @@
RAMPART_SOURCE_DIR = ..\..\
RAMPART_INTDIR = .\int.msvc
-RAMPART_DISTDIR = .\..\rampart
RAMPART_DIST_NAME = .\..\rampart-$(MAJOR_VER).$(MINOR_VER)
+#RAMPART_DISTDIR = .\..\rampart
+RAMPART_DISTDIR = $(RAMPART_DIST_NAME)
#rampart module
@@ -71,6 +72,7 @@
mkdir $(RAMPART_DISTDIR)\bin\samples\authn_provider
mkdir $(RAMPART_DISTDIR)\bin\samples\services\sec_echo
mkdir $(RAMPART_DISTDIR)\bin\samples\client\sec_echo
+ mkdir $(RAMPART_DISTDIR)\bin\samples\client\sec_echo\data
mkdir $(RAMPART_DISTDIR)\bin\samples\credential_provider
mkdir $(RAMPART_DISTDIR)\modules\rampart
mkdir $(RAMPART_DISTDIR)\include
@@ -126,7 +128,11 @@
/Fo$(RAMPART_INTDIR)\samples\client\sec_echo\ /c
$(LD) $(LDFLAGS) $(RAMPART_INTDIR)\samples\client\sec_echo\echo.obj
axutil.lib axiom.lib \
axis2_parser.lib axis2_engine.lib
/OUT:$(RAMPART_DISTDIR)\bin\samples\client\sec_echo\echo.exe
-
+
+ copy
$(RAMPART_SOURCE_DIR)\samples\client\sec_echo\deploy_client_repo.bat
$(RAMPART_DISTDIR)\bin\samples\client\sec_echo\
+
+ copy
$(RAMPART_SOURCE_DIR)\samples\client\sec_echo\data\client.axis2.xml
$(RAMPART_DISTDIR)\bin\samples\client\sec_echo\data\
+
mod_rampart_samples_credential_provider:
$(CC) $(CFLAGS) $(MOD_RAMPART_INCLUDE_PATH) \
$(RAMPART_SOURCE_DIR)\samples\credential_provider\*.c \
@@ -149,6 +155,9 @@
mod_rampart_copy_deploy:
copy deploy_rampart.bat $(RAMPART_DISTDIR)
+copy_sec_policy:
+ xcopy /E /I /Y $(RAMPART_SOURCE_DIR)\samples\secpolicy
$(RAMPART_DISTDIR)\bin\samples\sec_policy
+
#copy make_bin_dist.bat $(RAMPART_DISTDIR)
mod_rampart_all: mod_rampart mod_rampart_authn mod_rampart_pwcb
mod_rampart_htpwcb mod_rampart_samples mod_rampart_copy_include
@@ -157,14 +166,14 @@
move $(RAMPART_DISTDIR) $(RAMPART_DIST_NAME)
del_am:
- chdir .\..\rampart
+ chdir $(RAMPART_DISTDIR)
del /s *.am
chdir .\..\win32
-dist: clean distdir intdirs mod_rampart mod_rampart_pwcb mod_rampart_authn
mod_rampart_services_sec_echo mod_rampart_samples_sec_echo
mod_rampart_samples_credential_provider mod_rampart_copy_deploy
mod_rampart_copy_include mod_rampart_copy_keys del_am mv_dist
+dist: clean distdir intdirs mod_rampart mod_rampart_pwcb mod_rampart_authn
mod_rampart_services_sec_echo mod_rampart_samples_sec_echo
mod_rampart_samples_credential_provider mod_rampart_copy_deploy copy_sec_policy
mod_rampart_copy_include mod_rampart_copy_keys del_am
deploy:
- chdir $(RAMPART_DIST_NAME)
+ chdir $(RAMPART_DISTDIR)
deploy_rampart.bat
chdir .\..\win32
Modified:
webservices/rampart/trunk/c/samples/client/sec_echo/deploy_client_repo.bat
URL:
http://svn.apache.org/viewvc/webservices/rampart/trunk/c/samples/client/sec_echo/deploy_client_repo.bat?view=diff&rev=533730&r1=533729&r2=533730
==============================================================================
--- webservices/rampart/trunk/c/samples/client/sec_echo/deploy_client_repo.bat
(original)
+++ webservices/rampart/trunk/c/samples/client/sec_echo/deploy_client_repo.bat
Mon Apr 30 05:50:29 2007
@@ -16,9 +16,6 @@
@echo Copying axis2.xml to client_repo
copy /Y ".\data\client.enc.axis2.xml" "%CLIENT_REPO%\axis2.xml"
-rem @echo Copying axis2.xml to AXIS2C_HOME
-rem copy /Y ".\data\server.enc.axis2.xml" "%AXIS2C_HOME%\axis2.xml"
-
@echo Copying libraries to client_repo
xcopy /S/I/Q/Y "%AXIS2C_HOME%\lib" "%CLIENT_REPO%\lib"
