But what if you *want* to sell a packaged deal? We are building a tool that
uses J2EE technologies, and eventually want to sell it as a developer's kit.
But before we get to selling an SDK, we want to sell an easy to set up, easy
to maintain packaged solution. Ideally, I don't want our end-users to have
to manage whichever application server we choose - it should be hidden from
them through our management console. The hardest part is choosing which
low-cost app server to use for the packaged version...
Jason Boehle
[EMAIL PROTECTED]
-----Original Message-----
From: Suneet Shah [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 15, 2001 11:53 PM
To: Orion-Interest
Subject: RE: Strategies for bundling Orion
Hello Vidur,
We approach the problem a little differently. My company provides EJB
components that run in a J2EE app server. We provide deployment instructions
in the product for the servers that we have deployed on.
Its pretty straight forward. I don't think there much advantage to hiding
the appsever. Most of our customers see a strenght in knowing that we are
support a standards based app server and did not build everything ourselves.
Regards
Suneet Shah
Diamelle Technologies http://www.diamelletechnologies.com
Components based solutions for eCommerce and CRM
-----Original Message-----
From: Vidur Dhanda [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 14, 2001 10:20 PM
To: Orion-Interest
Subject: Strategies for bundling Orion
Hello,
I need to deliver a "packaged" solution that uses Orion. I need to make
the installation as simple as possible and also not expose Orion server
to the customer. What are my options for delivering the server code?
The reasons for "hiding" Orion from the customer is to decrease their
perception of maintenance. After all, the customer is purchasing a
solution from me and they don't want to be bothered about the solution's
internal workings. Has anyone bundled an Orion server with the beans?
Any pitfalls that I should be aware of?
Thanks,
Vidur
