
Porting Events
During application porting, the following events occur:
Example
• Conditions and environment options are converted when possible. See Other
PeriProducer Changes on page 27. See PeriProducer for the Avaya BCM for more
information about Avaya BCM-specific changes to PeriProducer.
• Blocks are converted to their nearest possible counterparts in 3.00. See
PeriProducer
3.00 Block Changes on page 22. See PeriProducer for the Avaya BCM for more
information about Avaya BCM-specific changes to PeriProducer.
• Resources are rendered obsolete. See PeriProducer for the Avaya BCM for more
information about Avaya BCM-specific changes to PeriProducer.
• The original file is renamed by changing its extension to .p2x
• The PeriPro 2.30 Runtime Behavior is enabled by default. See the PeriProducer User
Guide for more information about the 2.30 Runtime Behavior option.
• A file with name conversionlog_ <application> .txt is created and contains messages
pertaining to the conversion process. A similar file is created with the extension .html
and is in HTML format.
Conversion Logs
The conversion logs are detailed lists of issues encountered during conversion of PeriProducer
2.30 applications to PeriProducer 3.00. The conversion logs are written to the same directory
as the source (2.30) application. The logs are named conversion_a ppname .txt (in plain text
format) and conversion_ appname .html.
Each log entry indicates an application function that required some translation to become
PeriProducer 3.00-compatible. A conversion log is divided into three categories:
Example
1. Information: An information message indicates a conversion event that does not
affect the functionality of the application. For example, an information message
generates from the conversion of a 2.30 condition name to a new 3.00 condition
Porting Events
Avaya Business Communications Manager—IVR Upgrade Guide September 2010 83
Comentarios a estos manuales