GlassFish ESB components information requested

[Eric Tiong]

Some parts of this message have been removed. Learn more about Nabble's security policy.

We are currently evaluating GlassFish ESB and we like the comprehensive features it provides so far. There are a few questions necessitated from implementing our use.  The questions are related to XSLT SE, file compression capability, HL7 encoder for various versions, and NMR message routing options as shown below.

 

1-       Is it possible to do XSL transformation with XSLT SE WITHOUT providing input and output XML schema?

2-       Is it possible to bypass NMR with attachment before routing it to an output binding (for example send to destination in ZIP)

3-       Does it have a file compression feature to compress data content to a compressed and password protected file?

4-       Is there any documentation about the encoder (actually I just know there is hl7encoder-1.0)

5-       Why HL7 Component's protocolproperties.version ID has the choice of 3.0 and does it imply that HL7 version 3.0 is supported somewhere in the product?

 

Thank you.

 

Eric Tiong

 

[mwhite]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Eric Tiong wrote:

We are currently evaluating GlassFish ESB and we like the comprehensive features it provides so far. There are a few questions necessitated from implementing our use.  The questions are related to XSLT SE, file compression capability, HL7 encoder for various versions, and NMR message routing options as shown below.

 

1-       Is it possible to do XSL transformation with XSLT SE WITHOUT providing input and output XML schema?

2-       Is it possible to bypass NMR with attachment before routing it to an output binding (for example send to destination in ZIP)

The NMR never touches attachments - they are passed through as-is, so you should be able to do this without any
problem.

3-       Does it have a file compression feature to compress data content to a compressed and password protected file?

4-       Is there any documentation about the encoder (actually I just know there is hl7encoder-1.0)

5-       Why HL7 Component's protocolproperties.version ID has the choice of 3.0 and does it imply that HL7 version 3.0 is supported somewhere in the product?

 

Thank you.

 

Eric Tiong

 

--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...

[Kevan Simpson]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi Eric,

It is possible to do an XSL transformation in XsltSE without the schemas.  The schemas are only used at design-time to assist in the generation of XPath queries in the stylesheet editor; they are not required at runtime.

Regards,
Kevan

Eric Tiong wrote:

We are currently evaluating GlassFish ESB and we like the comprehensive features it provides so far. There are a few questions necessitated from implementing our use.  The questions are related to XSLT SE, file compression capability, HL7 encoder for various versions, and NMR message routing options as shown below.

 

1-       Is it possible to do XSL transformation with XSLT SE WITHOUT providing input and output XML schema?

2-       Is it possible to bypass NMR with attachment before routing it to an output binding (for example send to destination in ZIP)

3-       Does it have a file compression feature to compress data content to a compressed and password protected file?

4-       Is there any documentation about the encoder (actually I just know there is hl7encoder-1.0)

5-       Why HL7 Component's protocolproperties.version ID has the choice of 3.0 and does it imply that HL7 version 3.0 is supported somewhere in the product?

 

Thank you.

 

Eric Tiong

 

[Lixin Tang]

Some parts of this message have been removed. Learn more about Nabble's security policy.

4-       Is there any documentation about the encoder (actually I just know there is hl7encoder-1.0)

 

There is currently no official document about the encoder yet. 

Please check out the following wiki site which should contain enough information about the encoder to get you started:

http://wiki.open-esb.java.net/Wiki.jsp?page=Encoder 

We have started working on the documentation for the encoders. Hopefully the document for custom encoder will be available soon after the Glassfish ESB release.

 

Thanks!

Lixin

---------

Open ESB Community
http://open-esb.org

 

 

[Eric Tiong]

Some parts of this message have been removed. Learn more about Nabble's security policy.

We are planning to implement SOAP over SSL (https connection) Open ESB.  We have a few questions related to SSL server and client side certificates, Open ESB runtime only deployment, XSLT SE, file compression capability, and NMR message routing options as shown below.

 

1-       Do you have standard components for publishing and consuming web servers over https connections using both SSL server and client certificates?

2-       Do you have an option to only install the runtime portion of the Open ESB for production environment that has a good admin and monitoring console to deploy and undeploy web services, and to manage lice cycle of the web services?

3-       Is it possible to do XSL transformation with XSLT SE WITHOUT providing input and output XML schema?

4-       Is it possible to bypass NMR with attachment before routing it to an output binding (for example send to destination in ZIP)

5-       Does it have a file compression feature to compress data content to a compressed and password protected file?

 

 

Thank you.

 

Eric Tiong

 

[Kevan Simpson]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi Eric,

Re: #4...  Yes, it's possible to run XSL transformations with XsltSE without the input and output schemas.  Schemas are never required at runtime and are optional at design-time, where they're used to augment the XSL Editor's code completion functionality.

Regards,
Kevan


Eric Tiong wrote:

We are planning to implement SOAP over SSL (https connection) Open ESB.  We have a few questions related to SSL server and client side certificates, Open ESB runtime only deployment, XSLT SE, file compression capability, and NMR message routing options as shown below.

 

1-       Do you have standard components for publishing and consuming web servers over https connections using both SSL server and client certificates?

2-       Do you have an option to only install the runtime portion of the Open ESB for production environment that has a good admin and monitoring console to deploy and undeploy web services, and to manage lice cycle of the web services?

3-       Is it possible to do XSL transformation with XSLT SE WITHOUT providing input and output XML schema?

4-       Is it possible to bypass NMR with attachment before routing it to an output binding (for example send to destination in ZIP)

5-       Does it have a file compression feature to compress data content to a compressed and password protected file?

 

 

Thank you.

 

Eric Tiong

 

[sherry_weng]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Eric Tiong wrote:

We are planning to implement SOAP over SSL (https connection) Open ESB.  We have a few questions related to SSL server and client side certificates, Open ESB runtime only deployment, XSLT SE, file compression capability, and NMR message routing options as shown below.

 

1-       Do you have standard components for publishing and consuming web servers over https connections using both SSL server and client certificates?

We do have support for SOAP over https connections in HTTP BC. The configuration is actually very straight forward: you can simply change the url scheme to 'https' in the soap:address (and if you are using the SOAP WSDL wizard in NB, please also make sure that you replace ${HttpDefaultPort} with ${HttpsDefaultPort}. The SSL handshake/authentication is actually done in the appserver (GlassFish) itself, and there are the default keystore/truststore config files in <GF_HOME>/domains/<domain_name>/config folder, which you could add your own certificates, aliases etc.
Currently, default is server side authentication only, but we are adding the capability to allow mutual (2-way) authentication right now...

2-       Do you have an option to only install the runtime portion of the Open ESB for production environment that has a good admin and monitoring console to deploy and undeploy web services, and to manage lice cycle of the web services?

3-       Is it possible to do XSL transformation with XSLT SE WITHOUT providing input and output XML schema?

4-       Is it possible to bypass NMR with attachment before routing it to an output binding (for example send to destination in ZIP)

5-       Does it have a file compression feature to compress data content to a compressed and password protected file?

No, we don't have this capability built-in in our file binding component right now, but this could be added to the to-do list...

Regards
--Sherry

 

 

Thank you.

 

Eric Tiong

 

[mwhite]

Eric,
2 - Yes, you can use the jbi-core-installer to install the runtime into
an existing GlassFish installation, and along
      with that runtime the GlassFish admin console extensions for Open
ESB are included.
4 - NMR does not look at message content, attachments can be any format
you want.
mark

Eric Tiong wrote:

>
> We are planning to implement SOAP over SSL (https connection) Open
> ESB.  We have a few questions related to SSL server and client side
> certificates, Open ESB runtime only deployment, XSLT SE, file
> compression capability, and NMR message routing options as shown below.
>
>  
>
> 1-       Do you have standard components for publishing and consuming
> web servers over https connections using both SSL server and client
> certificates?
>
> 2-       Do you have an option to only install the runtime portion of
> the Open ESB for production environment that has a good admin and
> monitoring console to deploy and undeploy web services, and to manage
> lice cycle of the web services?
>
> 3-       Is it possible to do XSL transformation with XSLT SE WITHOUT
> providing input and output XML schema?
>
> 4-       Is it possible to bypass NMR with attachment before routing
> it to an output binding (for example send to destination in ZIP)
>
> 5-       Does it have a file compression feature to compress data
> content to a compressed and password protected file?
>
>  
>
>  
>
> Thank you.
>
>  
>
> Eric Tiong
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Eric Tiong]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Thanks Sherry! I must have missed this one.

 

Eric Tiong

Senior Integration Engineer

MDI Achieve

7690 Golden Triangle Drive

Minneapolis, MN 55344

Toll:     [phone] ext 9759

Direct:  [phone]

Fax:     [phone]

Email:   eric.tiong@...

www.MDIAchieve.com

 

PHI HIPAA Compliance Statement
This communication may contain confidential Protected Health Information. This information including any attachment is intended only for the use of the individual or entity to which it is addressed. The authorized recipient of this information is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of these documents is STRICTLY PROHIBITED by federal law. If you have received this information in error, please notify the sender immediately and delete this transmission.

---

From: Sherry Weng [mailto:Sherry.Weng@...]
Sent: Wednesday, September 10, 2008 2:54 PM
To: dev@...
Cc: Stephane Ah-Ki
Subject: Re: GlassFish ESB components information requested

 

Eric Tiong wrote:

We are planning to implement SOAP over SSL (https connection) Open ESB.  We have a few questions related to SSL server and client side certificates, Open ESB runtime only deployment, XSLT SE, file compression capability, and NMR message routing options as shown below.

 

Do you have standard components for publishing and consuming web servers over https connections using both SSL server and client certificates?

We do have support for SOAP over https connections in HTTP BC. The configuration is actually very straight forward: you can simply change the url scheme to 'https' in the soap:address (and if you are using the SOAP WSDL wizard in NB, please also make sure that you replace ${HttpDefaultPort} with ${HttpsDefaultPort}. The SSL handshake/authentication is actually done in the appserver (GlassFish) itself, and there are the default keystore/truststore config files in <GF_HOME>/domains/<domain_name>/config folder, which you could add your own certificates, aliases etc.
Currently, default is server side authentication only, but we are adding the capability to allow mutual (2-way) authentication right now...

Do you have an option to only install the runtime portion of the Open ESB for production environment that has a good admin and monitoring console to deploy and undeploy web services, and to manage lice cycle of the web services?

Is it possible to do XSL transformation with XSLT SE WITHOUT providing input and output XML schema?

Is it possible to bypass NMR with attachment before routing it to an output binding (for example send to destination in ZIP)

Does it have a file compression feature to compress data content to a compressed and password protected file?

No, we don't have this capability built-in in our file binding component right now, but this could be added to the to-do list...

Regards
--Sherry

 

 

Thank you.

 

Eric Tiong

 

[Jason Weinstein]

I have tried all sorts of ways to checkout open-jbi-components. What cvs
do i need to do a successful checkout. I remember having this issue some
time back.

Working around this issue should be front and center on the
open-jbi-component cvs page.

Below i fail with two versions of cvs

Concurrent Versions System (CVSNT) 2.0.51d (client/server)
Concurrent Versions System (CVS) 1.11.21 (client)



cvs update: Updating
driver-tests/httpsoapbc/HttpWSITTests/WebHttpbcWsitClient/src/conf/xml-resources/web
nces/echoRELM/wsdl/nang-tecra.stc.com_18181/AppReliableMessaging-sun-http-binding
cvs.exe update: warning: cannot make directory CVS in .: No such file or
directory
cvs.exe update: in directory
driver-tests/httpsoapbc/HttpWSITTests/WebHttpbcWsitClient/src/conf/xml-resou
e-references/echoRELM/wsdl/nang-tecra.stc.com_18181/AppReliableMessaging-sun-http-binding/BpelReliableMes
cvs.exe update: cannot open CVS/Entries for reading: No such file or
directory
cvs.exe update: warning: cannot make directory CVS in .: No such file or
directory
cvs.exe update: in directory
driver-tests/httpsoapbc/HttpWSITTests/WebHttpbcWsitClient/src/conf/xml-resou
e-references/echoRELM/wsdl/nang-tecra.stc.com_18181/AppReliableMessaging-sun-http-binding/BpelReliableMes
cvs.exe update: cannot open CVS/Entries for reading: No such file or
directory
cvs.exe [update aborted]: cannot write
driver-tests/httpsoapbc/HttpWSITTests/WebHttpbcWsitClient/src/conf
web-service-references/echoRELM/wsdl/nang-tecra.stc.com_18181/AppReliableMessaging-sun-http-binding/BpelR
g//CVS/Template: No such file or directory

C:\>cvs -version

Concurrent Versions System (CVSNT) 2.0.51d (client/server)

Copyright (c) 1989-2001 Brian Berliner, david d `zoo' zuhn,
                        Jeff Polk, and other authors
CVSNT version (Aug 19 2004) Copyright (c) 1999-2004 Tony Hoyle and others
see http://www.cvsnt.org

CVS may be copied only under the terms of the GNU General Public License,
a copy of which can be found with the CVS distribution kit.

SSH connectivity provided by PuTTY:
  PuTTY is copyright 1997-2001 Simon Tatham.
  Portions copyright Robert de Bath, Joris van Rantwijk, Delian
  Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry,
  Justin Bradford, and CORE SDI S.A.
  see http://www.chiark.greenend.org.uk/~sgtatham/putty/

Specify the --help option for further information about CVS

C:\mgmt\open-jbi-comps\open-jbi-components>"C:\Program
Files\Cvs\cvs.exe" -version

Concurrent Versions System (CVS) 1.11.21 (client)

Copyright (C) 2005 Free Software Foundation, Inc.

Senior active maintainers include Larry Jones, Derek R. Price,
and Mark D. Baushke.  Please see the AUTHORS and README files from the CVS
distribution kit for a complete list of contributors and copyrights.

CVS may be copied only under the terms of the GNU General Public License,
a copy of which can be found with the CVS distribution kit.

Specify the --help option for further information about CVS



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Russ Tremain]