Expected Run Times for Conversion Effort

-
Hint: I tend to expect my conversion effort to run for about 24-36 hours all up (assuming the machine has been spec'ed to suit the customers implementation footprint and standard batch schedule expectations). This tends to include the migration to Prod, and Tidy Balances (including database backups at various stages throughout the process).
As a rule of thumb though I tend to break the processing down to:

~10-20% - Input Transform (ie ConversionCentral)
~25-30% - Object Validation
~ 5-10% - Key Generation
~ 5-10% - Tidy Balances
~10-15% - Production Migration
~15-25% - Reporting

Comments

GoBipUser said…
How can i get a cobol source code from the application Viewer in Text format?.

Thanks for your support.

Gabriel
February 15, 2008 at 1:59 AM
Stuart Ramage said…
Gabriel,

The Application Viewer contains a mix of Oracle Utilities CC&B Base Code and Customer Modifications and is read-only by design. The Oracle Base Code is protected and should NOT be changed under any circumstances. The Customer Modifications should be available to you in the clients source repository. It is also available on the server in the $SPLEBASE\cobol\source\cm directory as a last resort.
February 15, 2008 at 7:15 AM
Post a Comment

Popular posts from this blog

Database Upgrades and their impact on Conversion

-
Hint: It appears that the current strategy in relation to application of Single Fixes and Service Packs no longer supports application of these scripts against a staging schema (at least as part of CC&B 2.x.x). As a result it is recommended that you drop and rebuild the Conversion schema from the Production instance once this has been upgraded with the latest patch-sets. We have also noted that application of these single fixes may require a redelivery of all custom java code from the development environment, since the java compilation is not performed as part of the patch install process (unlike the Cobol implementation process).
Read more

Embedding web-based external applications within the framework.

-
Image
My current project contained a requirement to embed an external application within the the CC&B framework and initiate calls to this application supplying a number of context elements to ensure that the correct information is displayed. The client also requested that the application be 'skinned' to maintain the CC&B look-and-feel. This is how we implemented it.. Defined a number of Business Object to manage retrieval of data from some of the base CC&B objects in a flattened format (ie. Characteristics mapped to descriptive elements, unused fields not defined, etc). Defined a UI map which forms the canvas for 'painting' the application within our framework. A Query Zone to ensure that the required data associated with the Context Zones are retrieved (using Zone type F1-DE-QUERY). A Business Service to wrap the call to the Query Zone into a usable service. A Script to initiate the call to the Business Service with the associated Context Identifiers (fr...
Read more

Bundle Corrections.

-
We have identified an issue with the use of bundling and UI Maps, whereby the resulting Bundle was wrapping the UI Map in a set of CDATA tags, but only after it had already removed all formatting from the source records, resulting in corruption of the UI Map HTML fragments. This has now been corrected by implementing Single Fix 8228025 on FW/CC&B 2.2.0. If you are using the Bundling subsystem in your implementation, I strongly recommend that you implement this patch.
Read more