Adapters by /n software (OpenESB users: feedback requested!)

[Frank Kieviet]

Some javascript/style in this post has been disabled (why?)

All:

 

It's my pleasure to share with you the news that software vendor /n software is porting several of their communication components to JBI so that they can be used in OpenESB! This will further increase the number of components that are available to OpenESB users!

 

Unlike the components in OpenESB, the components by /n software will be closed source components and commercial support will be provided by /n software. Since we expect the /n software components to be a good match for OpenESB, we'll try to make it easy for OpenESB uses to download them via the OpenESB web site, and we're expecting /n software to monitor the OpenESB users' mailing list for questions regarding these components. I think you'll agree with me that commercial (closed-source) software can co-exist peacefully with OpenESB.

 

At the moment, /n software is currently working on JBI ports of these components (a beta of these components is expected shortly):

- FTP BC

- SFTP BC

- Secure Email BC

- SSH BC

- SMPP BC / SMS

- SNPP BC

- XMPP BC / Jabber

- S3 BC

- RSS BC

As you can see, there is some overlap with existing OpenESB components, but I'd like to think that more choice is better. Once the components are released we should provide some documentation in which we compare for instance the OpenESB FTP BC and the /n software FTP BC.

 

The following components are candidates to be ported:

- AS1 BC - AS1 (EDI-INT) Binding Component for e-business messaging.

- AS2 BC - eBusinessReadyT Certified AS2 (EDI-INT) Binding Component.

- AS3 BC - AS3 Binding Component for Secure (FTP/S) File Transfer.

- OFTP BC - Odette File Transfer Binding Component for BizTalk.

- WebDav BC - Web-based distributed authoring and versioning client Component.

- Credit Card BC - Credit card transaction processing Binding Component.

- NAESB BC - North American Energy Standards / GISB 1.4 (EDM) Binding Component.

- Some flavor of the pipeline components listed here: http://www.nsoftware.com/products/biztalk/pipeline/

 

Decisions on which components will be ported, and in which order, will be made based on interest from the user community. And here is where your input is requested: if you're interested in one or more of these components, make yourself heard! It is your chance to influence the /n software roadmap!

 

Frank

 

Frank Kieviet

OpenESB Community Manager (http://open-esb.org)

Senior Staff Engineer, SOA/BI, Sun Microsystems, Monrovia, CA

Tel [phone]

Blog: http://frankkieviet.blogspot.com/

 

[Rohit Rai]

What is the licensing on these components? Are you planning to release them in opensource?

if not any hint in terms of pricing?

Regards,

Rohit

The diamond cannot be polished without friction, nor man perfected without trials
http://mytechrantings.blogspot.com

On Wed, Oct 7, 2009 at 5:31 AM, Frank Kieviet <[hidden email]> wrote:

All:

 

It's my pleasure to share with you the news that software vendor /n software is porting several of their communication components to JBI so that they can be used in OpenESB! This will further increase the number of components that are available to OpenESB users!

 

Unlike the components in OpenESB, the components by /n software will be closed source components and commercial support will be provided by /n software. Since we expect the /n software components to be a good match for OpenESB, we'll try to make it easy for OpenESB uses to download them via the OpenESB web site, and we're expecting /n software to monitor the OpenESB users' mailing list for questions regarding these components. I think you'll agree with me that commercial (closed-source) software can co-exist peacefully with OpenESB.

 

At the moment, /n software is currently working on JBI ports of these components (a beta of these components is expected shortly):

- FTP BC

- SFTP BC

- Secure Email BC

- SSH BC

- SMPP BC / SMS

- SNPP BC

- XMPP BC / Jabber

- S3 BC

- RSS BC

As you can see, there is some overlap with existing OpenESB components, but I'd like to think that more choice is better. Once the components are released we should provide some documentation in which we compare for instance the OpenESB FTP BC and the /n software FTP BC.

 

The following components are candidates to be ported:

- AS1 BC - AS1 (EDI-INT) Binding Component for e-business messaging.

- AS2 BC - eBusinessReadyT Certified AS2 (EDI-INT) Binding Component.

- AS3 BC - AS3 Binding Component for Secure (FTP/S) File Transfer.

- OFTP BC - Odette File Transfer Binding Component for BizTalk.

- WebDav BC - Web-based distributed authoring and versioning client Component.

- Credit Card BC - Credit card transaction processing Binding Component.

- NAESB BC - North American Energy Standards / GISB 1.4 (EDM) Binding Component.

- Some flavor of the pipeline components listed here: http://www.nsoftware.com/products/biztalk/pipeline/

 

Decisions on which components will be ported, and in which order, will be made based on interest from the user community. And here is where your input is requested: if you're interested in one or more of these components, make yourself heard! It is your chance to influence the /n software roadmap!

 

Frank

 

Frank Kieviet

OpenESB Community Manager (http://open-esb.org)

Senior Staff Engineer, SOA/BI, Sun Microsystems, Monrovia, CA

Tel [phone]

Blog: http://frankkieviet.blogspot.com/

 

[Paul Perez]

Hi Franck

It is good to see that a company like /n software is involved in JBI and proposes BC components (Congratulationfor the Job). In spite of a gloomy climate on Sun products, at Pymma we are happy to see other companies confident in JBI and Open-ESB technologies.

Since few months, in the light of Oracle-Sun deal, many organisations are hesitant to reply on JBI/Open-ESB technologies for their future integration projects. From our part, we think that Glassfish-ESB and Oracle fusion do not aim at the same type of applications and the same public. Oracle that already has competitor product in hits portfolio (Ex: Siebel, JD Edouard, oracle applications) will continue the job made by Sun on ESB and invest in it. Oracle will not be able to compete against JBoss ESB, ServiceMix… with Oracle fusion only and Open-ESB will be a perfect for that role.

We still believe that a light and powerful ESB, easy to use, relying on well known standards, with user-friendly tools, is a strong requirement for companies.

To see a company like /n software issuing new BC components confirm our point of view.

Kevin, congratulation for your job made for the community

Paul Perez

Frank Kieviet wrote:

All:

 

It's my pleasure to share with you the news that software vendor /n software
<http://www.nsoftware.com/>  is porting several of their communication
components to JBI so that they can be used in OpenESB! This will further
increase the number of components that are available to OpenESB users!

 

Unlike the components in OpenESB, the components by /n software will be
closed source components and commercial support will be provided by /n
software. Since we expect the /n software components to be a good match for
OpenESB, we'll try to make it easy for OpenESB uses to download them via the
OpenESB web site, and we're expecting /n software to monitor the OpenESB
users' mailing list for questions regarding these components. I think you'll
agree with me that commercial (closed-source) software can co-exist
peacefully with OpenESB.

 

At the moment, /n software is currently working on JBI ports of these
components (a beta of these components is expected shortly):

- FTP BC

- SFTP BC

- Secure Email BC

- SSH BC

- SMPP BC / SMS

- SNPP BC

- XMPP BC / Jabber

- S3 BC

- RSS BC

As you can see, there is some overlap with existing OpenESB components, but
I'd like to think that more choice is better. Once the components are
released we should provide some documentation in which we compare for
instance the OpenESB FTP BC and the /n software FTP BC.

 

The following components are candidates to be ported:

- AS1 BC - AS1 (EDI-INT) Binding Component for e-business messaging.

- AS2 BC - eBusinessReadyT Certified AS2 (EDI-INT) Binding Component.

- AS3 BC - AS3 Binding Component for Secure (FTP/S) File Transfer.

- OFTP BC - Odette File Transfer Binding Component for BizTalk.

- WebDav BC - Web-based distributed authoring and versioning client
Component.

- Credit Card BC - Credit card transaction processing Binding Component.

- NAESB BC - North American Energy Standards / GISB 1.4 (EDM) Binding
Component.

- Some flavor of the pipeline components listed here:
http://www.nsoftware.com/products/biztalk/pipeline/

 

Decisions on which components will be ported, and in which order, will be
made based on interest from the user community. And here is where your input
is requested: if you're interested in one or more of these components, make
yourself heard! It is your chance to influence the /n software roadmap!

 

Frank

 

Frank Kieviet

OpenESB Community Manager (http://open-esb.org <http://open-esb.org/> )

Senior Staff Engineer, SOA/BI, Sun Microsystems, Monrovia, CA

Tel [phone]

Blog: http://frankkieviet.blogspot.com/

 

[Paul Perez]

Frank,

From our point of view, - Credit Card BC  and AS* would be good additionnal BCs for Open-ESB

regards

PPe

Frank Kieviet wrote:

All:

 

It's my pleasure to share with you the news that software vendor /n software
<http://www.nsoftware.com/>  is porting several of their communication
components to JBI so that they can be used in OpenESB! This will further
increase the number of components that are available to OpenESB users!

 

Unlike the components in OpenESB, the components by /n software will be
closed source components and commercial support will be provided by /n
software. Since we expect the /n software components to be a good match for
OpenESB, we'll try to make it easy for OpenESB uses to download them via the
OpenESB web site, and we're expecting /n software to monitor the OpenESB
users' mailing list for questions regarding these components. I think you'll
agree with me that commercial (closed-source) software can co-exist
peacefully with OpenESB.

 

At the moment, /n software is currently working on JBI ports of these
components (a beta of these components is expected shortly):

- FTP BC

- SFTP BC

- Secure Email BC

- SSH BC

- SMPP BC / SMS

- SNPP BC

- XMPP BC / Jabber

- S3 BC

- RSS BC

As you can see, there is some overlap with existing OpenESB components, but
I'd like to think that more choice is better. Once the components are
released we should provide some documentation in which we compare for
instance the OpenESB FTP BC and the /n software FTP BC.

 

The following components are candidates to be ported:

- AS1 BC - AS1 (EDI-INT) Binding Component for e-business messaging.

- AS2 BC - eBusinessReadyT Certified AS2 (EDI-INT) Binding Component.

- AS3 BC - AS3 Binding Component for Secure (FTP/S) File Transfer.

- OFTP BC - Odette File Transfer Binding Component for BizTalk.

- WebDav BC - Web-based distributed authoring and versioning client
Component.

- Credit Card BC - Credit card transaction processing Binding Component.

- NAESB BC - North American Energy Standards / GISB 1.4 (EDM) Binding
Component.

- Some flavor of the pipeline components listed here:
http://www.nsoftware.com/products/biztalk/pipeline/

 

Decisions on which components will be ported, and in which order, will be
made based on interest from the user community. And here is where your input
is requested: if you're interested in one or more of these components, make
yourself heard! It is your chance to influence the /n software roadmap!

 

Frank

 

Frank Kieviet

OpenESB Community Manager (http://open-esb.org <http://open-esb.org/> )

Senior Staff Engineer, SOA/BI, Sun Microsystems, Monrovia, CA

Tel [phone]

Blog: http://frankkieviet.blogspot.com/

 

[Lance Robinson]

Rohit Rai wrote:

What is the licensing on these components? Are you planning to release them
in opensource?
if not any hint in terms of pricing?

Regards,
Rohit

Thanks to Frank and everyone else for the comments.  At /n software we are very excited about our entry into this area, and we're hoping that the community will be able to give us a lot of feedback on our offerings.  We want to know what you think we are doing right, and what you think we are doing wrong.

There is not a current plan for open-sourcing these components, they will be offered through a commercial license.

Lance Robinson
/n software