本文探讨了Oracle E-Business Suite OnDemand (OOD) 的实际应用体验，列举了使用OOD服务的优势与不足之处，包括Oracle提供的维护和支持、减少IT人员配置需求、无需本地硬件设施等好处，以及应用程序密码丢失、定制化实施困难等问题。
Oracle E-Business Suite On Demand(OOD)是指服务器在Oracle那边，由Oracle负责管理维护，客户通过公网（或VPN）来访问EBS系统。
和传统的ERP系统（In-House）比，有好处也有麻烦的地方, Oracle E-Business Suite On Demand (OOD): Real Life Experiences对于OnDemond的好处和坏处做了罗列，可作参考（评论中也有亮点）
===Good Things Regarding Oracle On Demand===
* Can lead to a reduction in IT staff (if you can consider this to be a good thing.)
* No on-site hardware is needed (except for a Virtual Private Network [VPN] devise.)
* Database health checks and database system administration are monitored and administered by Oracle.
* Oracle assigns a migration and/or an implementation team to each client (usually consisting of a Service Delivery Manager, Service Delivery Engineer, Affinity Engineer, and sometimes a Database Administrator.)
* Uptime and performance of the applications is very good.
===Not-So-Good Things Regarding Oracle On Demand===
* Loss of the Apps password for the Production instance.
* Loss of the System Administrator and Applications Developer responsibilities in all instances (replaced by a responsibility called Applications Administrator which contains only a few forms.)
* OOD customers cannot bounce the server on any instance (customers must log a TAR and then update the TAR with a Change Request Template (CRT) to give OOD a time frame when to perform these tasks, and then wait for OOD to perform these tasks.) This can slow down implementation of CRM modules because the Apache Server must be bounced and the JSP cache cleared for many changes to take effect.
* Internal communications at OOD is sometimes slow and lacking knowledge (especially functional knowledge of the Oracle E-Business Suite.)
* Customizations are sometimes difficult to get properly set up into the OOD Production instance (since the customer only has read-only access to Linux OOD personnel must install customizations, and obviously, they are not familiar with customer specific customizations or their business requirements.)
* More TARs are required, and, of course, this takes a considerable amount of time and communication following up in Metalink.
和传统的ERP系统（In-House）比，有好处也有麻烦的地方, Oracle E-Business Suite On Demand (OOD): Real Life Experiences对于OnDemond的好处和坏处做了罗列，可作参考（评论中也有亮点）
===Good Things Regarding Oracle On Demand===
* Three instances are provided (Development, Test and Production.)
* Maintenance and security patches are routinely analyzed and applied.* Can lead to a reduction in IT staff (if you can consider this to be a good thing.)
* No on-site hardware is needed (except for a Virtual Private Network [VPN] devise.)
* Database health checks and database system administration are monitored and administered by Oracle.
* Oracle assigns a migration and/or an implementation team to each client (usually consisting of a Service Delivery Manager, Service Delivery Engineer, Affinity Engineer, and sometimes a Database Administrator.)
* Uptime and performance of the applications is very good.
===Not-So-Good Things Regarding Oracle On Demand===
* Loss of the Apps password for the Production instance.
* Loss of the System Administrator and Applications Developer responsibilities in all instances (replaced by a responsibility called Applications Administrator which contains only a few forms.)
* OOD customers cannot bounce the server on any instance (customers must log a TAR and then update the TAR with a Change Request Template (CRT) to give OOD a time frame when to perform these tasks, and then wait for OOD to perform these tasks.) This can slow down implementation of CRM modules because the Apache Server must be bounced and the JSP cache cleared for many changes to take effect.
* Internal communications at OOD is sometimes slow and lacking knowledge (especially functional knowledge of the Oracle E-Business Suite.)
* Customizations are sometimes difficult to get properly set up into the OOD Production instance (since the customer only has read-only access to Linux OOD personnel must install customizations, and obviously, they are not familiar with customer specific customizations or their business requirements.)
* More TARs are required, and, of course, this takes a considerable amount of time and communication following up in Metalink.
扫一扫
4533
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
