|
|
| 1. Workgroup vs. Enterprise Edition |
| Workgroup and Enterprise Editions are actually quite similar and both offer exactly the same robust PowerBuilder feature support and fast performance. The key difference between the two editions is that Workgroup Edition is intended for smaller deployments of few hundred users that only require a single stand-alone server while the Enterprise Edition can scale to any number of users. |
| |
| |
Workgroup Edition |
Enterprise Edition |
| DEPLOYMENT |
|
|
| New Web Development |
√ |
√ |
| Migration of Existing PB Applications |
√ |
√ |
| Client-side Printing |
√ |
√ |
| OLE/OCX/DLL Client Integration |
√ |
√ |
| |
|
|
| SERVER |
|
|
| .NET Server Support |
√ |
√ |
| J2EE Server Support |
√ |
√ |
| NVO N-Tier Support |
√ |
√ |
| Web Services Support |
√ |
√ |
| Clustering & Load Balancing |
|
√ |
| Server Failover |
|
√ |
| CPUs Supported |
2 |
∞ |
| |
|
|
| DEVELOPMENT |
|
|
| Unsupported Features Analyzer |
√ |
√ |
| IntelliSense (for Supported Features) |
√ |
√ |
| PB-to-Web Debugger |
√ |
√ |
| Incremental Web Deployment |
√ |
√ |
| Web Deployment Packaging Tool |
√ |
√ |
|
|
| 2. Supported Application Servers |
| All Editions of Appeon for PowerBuilder support both .NET and J2EE platforms, offering support for Microsoft IIS and most leading J2EE application servers. A pure-PowerBuilder project deployed by Appeon to one application server or operating system can be deployed automatically to a different application server or operating system, including switching between J2EE and .NET platforms, automatically! |
| |
.NET Application Server Support |
Microsoft IIS |
Microsoft Windows |
|
| |
J2EE Application Server Support |
| Sybase EAServer |
Microsoft Windows |
| Red Hat Linux |
BEA WebLogic |
Microsoft Windows |
Red Hat Linux |
IBM AIX |
IBM WebSphere |
Microsoft Windows |
Red Hat Linux |
IBM AIX |
|
|
| 3. Application Server Differences |
Because of differences between application servers, operating systems and platforms, there are some features that may differ from one technology stack to another, especially if your project contains non-PowerBuilder or external code. Please verify using the chart below that the technology stack you have chosen in step #2 contains all the key features your Web project requires.
|
| |
| |
J2EE |
.NET |
| Windows |
UNIX |
Windows |
| EAServer |
WebSphere |
WebLogic |
EAServer |
WebLogic |
WebSphere |
IIS |
| Client-side Features |
|
|
|
|
|
|
|
| Large Complex Applications |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
| PFC Framework |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
| Robust DataWindow Support |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
| MDI/SDI Support |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
OLE/OCX/DLL
/WIN32 Calls |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
| |
|
|
|
|
|
|
|
| |
EAServer/
Windows |
WebSphere/
Windows |
WebLogic/
Windows |
EAServer/
UNIX |
WebSphere/
UNIX |
WebLogic/
UNIX |
IIS/
Windows |
| Server-side Features |
|
|
|
|
|
|
|
| N-Tier PowerBuilder NVOs |
√ |
√1 |
√1 |
√ |
|
|
√ |
| J2EE Component Integration |
√ |
√ |
√ |
√ |
√ |
√ |
|
| .NET Component Integration |
|
|
|
|
|
|
√ |
| Web Services Integration |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
| Distributed DataWindows |
√ |
√ |
√ |
|
|
|
APB 6.0 |
| Web Server File Upload and Download |
√ |
√ |
√ |
√ |
√ |
√ |
APB 6.0 |
DLL/WIN32 Server-side
Calls |
√ |
√ |
√ |
|
|
|
√ |
| |
|
|
|
|
|
|
|
| |
EAServer/
Windows |
WebSphere/
Windows |
WebLogic/
Windows |
EAServer/
UNIX |
WebSphere/
UNIX |
WebLogic/
UNIX |
IIS/
Windows |
| Database Support |
|
|
|
|
|
|
|
| Sybase ASA |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
| Sybase ASE |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
| Sybase IQ |
√ |
|
|
√ |
|
|
|
Microsoft
SQL Server |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
| Oracle |
√ |
√ |
√ |
√ |
√ |
√ |
√ |
| IBM DB2 |
√ |
|
|
√ |
|
|
|
| Informix |
√ |
|
|
√ |
|
|
|
|
| 1 Requires the PowerBuilder Application Server Plug-in, which can be purchased from Sybase, Inc. or authorized Sybase resellers. |
| |
|
