I'm in the process of trying to check out the EJB co-server 
component, and have downloaded the version for use with 
WebSphere.  However, I don't find a deploy.properties file, 
deployment descriptors, or any file that tells the sample 
what host to talk to.

Is it just me (entirely possible), or is something missing?

thanks

Pete, we received your request and will get back with you 
as soon as possible.  Thanks!

I have someone looking at the deploy.properties, but am 
still curious about how the default/test application gets 
pointed to your Screensurfer server.  Don't we need to know 
that in order to use it locally?

thanks
Pete

Pete

I will have Jeff get back to you regarding the ejb issue 
shortly.

thanks

Pete, your change the location of the Screensurfer server 
in the SSrequest.properties file contained in the 
SurferEJB.jar file in the "Jars" subdirectory after 
installing the appropriate EJB.

I was afraid you might say something like that.  Perhaps 
someone could take a look at the WebSphere deployment - 
there is no properties file in that jar.  Not sure what 
else might be missing.

thanks
Pete

Yes, we will get someone to look at this.  We apologize for 
the incomplete EJB.  Do you have a deadline by which you 
need a resolution to the WebSphere EJB?  Thanks!

as is quite typical around here, it's asap - these projects 
come off the shelf and need "yesterday" turnaround.  There 
is a project in need of a development time estimate by 
tomorrow, so they need to understand what the development 
effort is, so they need to understand the development 
environment, and so on , and so on ....

I'm thinking that if the EJB is getting properties from 
that file, it should be the same regardless of platform - 
is any of the deployments fully tested and functional?  
Maybe I should just download the JRun or BEA version?

We totally understand the "asap" timeframe...I would try 
the JRun deployment.  Please let us know if this provides 
you what you need.  Thanks for your flexibility...

as it turns out, it seems as though the WebSphere 
deployment is OK.  Not quite sure why, but for WebSphere, 
the settings are put in the deployment descriptor as 
environment variables instead of externally in a properties 
file.  We did find some doc that referenced it, but I think 
there's another piece of doc that hasn't been updated yet.  
If I come back across them, I'll let you know what I find.  
For now, all seems to be well.

I think I found it - the ejbsurfer.html that is bundled 
with the v3 doc has not been updated with the WebSphere-
specific install section that is contained in the same file 
that is downloaded with the EJB component.

Thanks so much Pete for helping us straighten out the EJB 
stuff.  We'll look at the docs that you mentioned and 
update the V3 doc with the correct information.  Thanks 
again!!!

no problem - btw, if it wasn't mentioned before, we do have 
things working in a WebSphere environment - we had some 
issues getting it imported and setup in VAJ, but after 
that, smooth sailing.

Awesome!  We are glad that you got everything working.  So 
we can "tidy up" our Websphere EJB install a bit, we have a 
few questions for you:

- Were there any changes you needed to make to the 
deploy.properties file that we sent you for Websphere
- Were there any other changes to any part of the Websphere 
EJB that you had to make so we can include in the EJB?

Again, we are going to upgrade the V3 EJB documentation per 
your findings....

Thanks so much for your assistance! 

The WebSphere deployment doesn't actually use the 
properties file.  The settings that are contained in that 
file are instead set as environment variables in the 
deployment descriptor.

I'll get details about what else was done and forward on to 
you as an update to this record.

Pete

further doc sent via email re: import of the WebSphere EJB 
component into Visual Age for Java