I've been continuing along the path of determining
which infrastructure bits are required to begin ALF work. My starting
point was to attempt to compile the ALF Event manager. Here are the pieces
that I installed in order to accomplish this:
0. Using Eclipse 3.1.1 on
Windows.
1. Obtained the ALF-EM code (cvs -d
:pserver:anonymous@xxxxxxxxxxxxxxx:/home/technology checkout
org.eclipse.alf/eventmgr)
2. Downloaded and installed the
following:
apache_2.0.55-win32-x86-no_ssl.msi The windows installer for
Apache
jdk-1_5_0_06-windows-i586-p.exe JDK
1.5.0 R6 for Windows
jwsdp-2_0-windows-i586.exe
The Java Web Services Developer's kit from Sun
apache-tomcat-5.5.15.zip Apache
Tomcat servlet container (not needed to compile,
but needed to run the EM)
axis-bin-1_3.zip The
Apache Axis Web services kit
3. Set up an Eclipse project called AlfuRev (a not-so-clever
smashing together of 'AccuRev and ALF' that contains the source downloaded
in step one. Note, I had to manually create the
org/eclipse/alf/eventManager directory hierarchy and place the downloaded code
in the 'eventManager' directory in order to satisfy the Java compiler.
Minor point.
4. Add several external libraries (obtained by
downloading the bits listed above in step 2) to the Eclipse
project. Specifically added:
JRE System Library (jdk1.5.0_06)
servlet-api.jar (from
apache-tomcat-5.5.15\common\lib)
saaj-api.jar (from
jwsdp-2.0\saaj\lib)
activation.jar (from
jwsdp-2.0\jwsdp-shared\lib)
axis.jar (from axis-1_3\lib)
log4j-1.2.8.jar (from axis-1_3\lib)
jaxrpc.jar (from axis-1_3\lib)
The code successfully compiled after
this.
I would still appreciate guidance on the other infrastructure
bits that are required, including:
- BPEL Engine
- WDSL and webservices tools
- UDDI implementation for
discovery.
My goal is to take what I've learned and create an ALF HOW-TO,
or a 'Getting Started with ALF' that, with agreement from the community, might
utimately get posted on the ALF web page. Theory being that if we make it
easy to get started, we will better our chances of ALF reaching a critical mass
and really taking off.
Regards,
- matt
Due to various licensing issues, the VMware image of the
ALF POC will only be available to the direct POC participants. We plan
to build a "working stub" sample following the design of the POC that anyone
can download. I will start work on documenting the platform more
formerly this week
Tim
I would propose that we send Serena a USB or Firewire external hard
drives.
They cost < $150 and have plenty of room.
At 6:50 PM -0500 2/20/06, Matthew Laudato wrote:
Team
ALF:
There was some
discussion in late January about the POC being available as a VMWare
image. I have a few questions.
1. Where can that
image be found, and has it been trimmed down from 20G? What specific
version of VMWare is required in order to use it?
2. Is there a
definitive list of infrastructure pieces (software product names, versions,
URLs for download)?
AccuRev is working
on our ALF strategy, and we'd like to secure the proper bits. I think
there is (probably) a minimal set of opensource products that one needs to
get started:
- Apache
Tomcat
- A BPEL engine
(Oracle's is being used I believe)
- a WSDL
tool
- a UDDI
implementation
- The ALF Event
manager servlet code (have this already).
Note, I am
specifically excluding the partner products from the minimal
set.
If someone could
either post this list to alf-dev, or point me privately towards an existing
post or location, that would be greatly appreciated.
Regards,
-matt
--
Matt
Laudato
AccuRev, Inc
mlaudato@xxxxxxxxxxx
+1 617 957 8085
(cell)
+1 781 325 0656 (office)
matt_laudato
(skype)
_______________________________________________
alf-dev
mailing
list
alf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/alf-dev
--
Catalyst Systems Corporation
Ph: 800-359-8049
x114
505-424-6439
Fax:
505-424-6438
**********************************************************************
This
email and any files transmitted with it are confidential and
intended
solely for the use of the individual or entity to whom they
are addressed.
Any unauthorized review, use, disclosure or distribution is prohibited. If you
are not the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original
message.
