Page 1
ACE
Release Notes
ACE 7.81c
Revised February 2008
Page 2
Contact information Contact us on the Web at http://technicalsupport.businessobjects.com
If you find any problem with this documentation, please report it to Business Objects
in writing at
Copyright © 2008 Business Objects. All rights reserved.
Patents Business Objects owns the following U.S. patents, which may cover products that are
.
offered and licensed by Business Objects: 5,555,403; 5,857,205; 6,289,352;
6,247,008; 6,490,593; 6,578,027; 6,831,668; 6,768,986; 6,772,409; 6,882,998;
7,139,766; 7,299,419; 7,194,465; 7,222,130; 7,181,440 and 7,181,435.
Trademarks Business Objects and the Business Objects logo, BusinessObjects, Business Objects
Crystal Vision, Business Process On Demand, BusinessQuery, Crystal Analysis,
Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal
Reports, Desktop Intelligence, Inxight, the Inxight Logo, LinguistX, Star Tree, Table
Lens, ThingFinder, Timewall, Let there be light, Metify, NSite, Rapid Marts,
RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are
trademarks or registered trademarks in the United States and/or other countries of
Business Objects and/or affiliated companies. All other names mentioned herein may
be trademarks of their respective owners.
Third-party contributors Business Objects products in this release may contain redistributions of software
licensed from third-party contributors. Some of these individual compo nents may
also be available under alternative licenses. A partial listing of third-party
contributors that have requested or permitted acknowledgments, as well as required
notices, can be found at: http://www.businessobjects.com/thirdparty
2
ACE Release Notes
Page 3
Introduction
Welcome to ACE 7.81c. These release notes contain information about new
features and changes in this version of ACE.
Note: You may want to first install this version of ACE to a non-production
environment to test the changes and see how the changes affect your data.
What’s new in this release?
What’s in your package
This release contains a few enhancements that increase the quality of ACE. In
addition, this version has new installation steps and setup information.
“BusinessObjects License Manager” on page 5
“Installing ACE” on page 7
“Keycode functions for Library and RAPID” on page 9
“eLOT information in output for DSF2” on page 10
“DPV totals in Job Summary lists separate totals” on page 10
Your software package includes the ACE installation based on the platform(s)
that you have purchased. In addition, each installation contains product
documentation, and administrative files.
Both the DPV and LACS
separate components. As part of the ACE installation, DPV and LACS
Link
products are included in the ACE installation as
Link
supporting files are installed by default in the following directories:
Platform DPV LACS
Link
Windows pw\dpv\ pw\lacslink
UNIX postware/dpv/ postware/lacslink
You must also copy directory updates to these locations.
Product versions Product versions for this release are as follows:
ACE 7.81c. This is the overall version of the ACE software.
CASS-certified ACE version 7.80.01.L. The last character is the letter L for
CASS Cycle L. This is the most recently CASS-certified version of ACE.
Mover ID version 5.0. This version applies to ACE’s Mover ID option.
Split shipments For customers who have requested physical delivery of USPS directories as well
as ACE, you will receive your packages separately.
Important: You might not receive both boxe s at the same time. You should
!
wait to install ACE until you receive both boxes.
Introduction
3
Page 4
ACE Documentation You can access product documentation in several places:
On your computer. Release notes, manuals, and other documents for each
product that you have installed are available in the Documentation folder.
Choose Start > Programs > Business Objects Applications >
Documentation.
On the Business Objects support site. A complete set of ACE
documentation (listed below) is available for you to view or download at
http://support.businessobjects.com/documentation/product_guides/
default.asp.
You can view the PDFs online or save them to your computer for viewing or
printing.
In addition, ACE Views comes with a built-in help file that gives descriptions of
options and provides steps to perform ACE processes. To access the ACE Views
help file, open ACE and choose Help > Help Topics.
We suggest that you consult the following manuals for information about ACE
features and options, and about setting up jobs in ACE Job, Views, Library, and
RAPID.
ACE documentation Other useful documents
ACE Release Notes
ACE User’s Guide
ACE Job-File Reference
ACE Library Reference
Mover ID User’s Guide for NCOA
(this document)
System Administrator’s Guide
Views Quick Star t Guide
Database Prep
Quick Reference for Views and Job-
Link
File Products
Quick Reference for Library Products
RAPID User’s Guide
Edjob User’s Guide
4
ACE Release Notes
Page 5
BusinessObjects License Manager
License Manager is a Business Objects application that lets you manage your
product activation keycodes—the numeric codes that are referred to each time
that you run ACE. In the BusinessObjects License Manager application, you can
view, add, and remove product activation keycodes for ACE.
System requirements: BusinessObjects License Manager requires that you
have Java 1.4 or higher installed on your system.
How it works Your installation CD today contains all ACE features. Business Objects provides
you with product activation keycodes for the features that you have purchased.
You enter the product activation keycodes into License Manager.
After installation, if you decide to purchase one of the ACE add-on features
Link
(NCOA
for example), Business Objects provides you with the feature’s
product activation keycode. You can immediately activate the feature in your
software by entering the new keycode into License Manager.
For-sale options With License Manager, you can immediately activate additional for-sale options
that you purchase by entering the associated product activation keycode into
License Manager.
Accessing License Manager
For Windows installations, License Manager opens automatically after ACE
installation has completed. And you can later open License Manager from your
Start menu to add more product activation keycodes for additional feature
purchases.
For UNIX, you open License Manager manually.
Important: You must run License Manager before you can use ACE.
!
BusinessObjects License Manager
5
Page 6
Setting up License Manager
Windows If you use Windows, you don’t need to perform any manual setup of License
Before you can run License Manager on its own (that is, not during the
installation process), you may need to do some setup.
Manager. Environment variables are set when License Manager is installed.
UNIX If you use UNIX, you need to set the environment variable
(BOE_REGISTRYHOME) for License Manager.
If you use Bourne shell, add product entries to your .profile or .login file. For
example:
BOE_REGISTRYHOME=/var/opt;
export BOE_REGISTRYHOME
If you use C shell (Berkeley), add product entries to your .cshrc file. For
example:
setenv BOE_REGISTRYHOME /var/opt/
For complete information about running License Manager, see the System
Administrator's Guide.
Library and RAPID users
For function calls to activate License Manager, see “Keycode functions for
Library and RAPID” on page 9
6
ACE Release Notes
Page 7
Installing ACE
Important: Read about the new License Manager utility before installing
!
ACE (“BusinessObjects License Manager” on page 5).
Operating system versions
Run ACE on one of our supported operating systems, which are listed at http://
technicalsupport.businessobjects.com
ACE does not run on unsupported operating systems such as Windows 98, NT,
and ME.
Installation advice To simplify installation, read the following tips before you begin:
Make sure you view the latest System Administrator’s Guide for complete
installation instructions.
Give the contents of this software shipment to your system administrator.
This software should be installed by, or with the approval of, your system
administrator.
Although you can install your applications and dir ect ories in any order, it’s
best to install software first and then directories.
Install ACE on Windows
You need administrative privileges to install ACE Views on Windows 2000/XP.
However, you do not need administrative privileges to run ACE Views on
Windows 2000/XP.
When you start the ACE installer, the installation program should start
automatically. If it doesn’t, follow these steps:
1. Access your Windows Start menu and choose Run.
2. Type x:\setup (where x is the location of the ACE installer) and click OK.
After the program completes the installation, BusinessObjects License Manager
launches. For instructions to access and run BusinessObjects License Manager,
see the System Administrator’s Guide.
Installing ACE
7
Page 8
Install ACE on Unix To install ACE on Unix, use the install_console installation for the Java Runtime
Environment explained in the System Administrator’s Guide.
Notice more CDs? In your ACE package for UNIX systems, y ou may notice that you have more than
one product installation CD.
To ensure that you are provid ed with software that meets your system
requirements, we will provide multiple operating systems per product in one
software package (based on the operating systems available in ACE). You choose
the install that matches your operating system, version, and bit level.
For example, if you order ACE version X on HP9000-HPUX, you could receive
two CDs:
ACE v. X HP9000-HPUX (32-bit)
ACE v. X HP9000-HPUX (64-bit)
If ACE v. X is only available on 32-bit, you could receive one CD.
Client shortcuts If you have ACE installed on one computer , but you run it from another comp uter
using client shortcuts, you must refresh your client-side shortcuts b y usi ng the
Universal Client installer.
Run Edjob for Views, Job, and RAPID
To update all of your existing ACE jobs to the new Presort version 7.81c, run
Edjob. For instructions on running Edjob, see the Edjob User’s Guide.
This does not apply to you if you have just purchased ACE and you are installing
it for the first time.
8
ACE Release Notes
Page 9
Keycode functions for Library and RAPID
Library and RAPID users have the option to use the following functions to enter
product activation keycodes within application code. This is an alternative to
using the License Manager to enter product activation keycodes in the registry.
These are optional.
eim_add_keycode()
Synopsis void eim_add_keycode(const char* keycode);
Description The eim_add_keycode() function adds a single key code to the collection of
Business Objects key codes used for enabling prod uct functionality. This function
may be called once per key code owned.
All calls to eim_add_keycode() must occur between eim_keycode_global_init()
and eim_keycode_global_term(), and must be called before ace_open().
Returns None
eim_keycode_global_init(), eim_keycode_global_ term()
Synopsis void eim_keycode_global_init(void);
void eim_keycode_global_term(void);
Description The eim_keycode_global_init() and eim_keycode_global_term() functions are
only required if eim_add_keycod e() is called within the application. The
eim_keycode_global_init() function initializes the Business Objects keying
system for use. An eim_keycode_global_init()call must precede any call to
eim_add_keycode(). The eim_keycode_global_term() function releases all
memory allocated by the Business Objects keying system functions and
terminates the Business Objects keying system. This call must be made at some
point following ace_open(). These functions are meant to be called once per
application, and are not meant to be called once per thread.
Returns None
Keycode functions for Library and RAPID
9
Page 10
eLOT information in output for DSF
2
We clarified with the USPS that it is optional to output the eLOT Delivery
Sequence Number and the Ascending/Descending Code to an output file.
Therefore we have updated ACE to output the following info rmation wh en DSF
is enabled:
AP.Lot
AP.Lot_Order
APM.Lot
APM.Lot_Order
Previously the USPS documented in the DSF2 Developer Guide that vendors
were to “Remove the eLOT Delivery Sequence Number and the Ascending/
Descending Code from the customer’s final file.” That statement was reversed
and now it is optional.
DPV totals in Job Summary lists separate totals
In the Delivery Point Validation Summary (DPV) portion of the Job Summary
Report, DPV totals for AP.DPV_STATUS indicators of Y, S, and D are listed
separately so that you can obtain a more accurate confirmed total. Previously the
Total Confirmed summary included records with a status value of Y, S, and D.
2
Here is a look at the new DPV Summary section:
Delivery Point Validation Summary (DPV)
CMRA DPV
DPV Status Code Count Confirmed No Stat
-------------------------------- --------- --------- --------Primary/Secondary Confirmed (Y) 380 0 13
Secondary Not Confirmed (S) 3 0 2
Secondary Missing (D) 18 0 18
-------------------------------- --------- --------- --------Total: 401 0 33
Total Not Confirmed: 0
For your reference, here are descriptions of the AP.DPV_STATUS indicators Y,
S, and D:
Y = The address is a confirmed delivery point. The primary range and secondary
range (if present) are valid.
S = The primary range is a valid delivery point, but the parsed secondary range
(including extran_sec # sign data) is not valid in the DPV directo r y.
D = The primary range is a valid delivery point but the secondary range data is
not available on input.
See the Quick Reference for Views and Job-File Products for more DPV field
descriptions.
10
ACE Release Notes
Loading...