This section covers general release information.
x
As of Version 7 Release 7.06, support has been dropped
for the following operating systems, adapters, and features.
Operating Systems
- Solaris 8 Sparc.
- OS400 V5R4 iSeries
(nearest supported v6.1).
Adapters
- Business Object Universe
- EJB
- Erwin
- ESSBASE 6.5 (as of
Version 7 Release 7.04)
- MQSeries ( WebLogic 8 and WebSphere)
- MS SQL Server 2000
- Netezza ODBC Adapter
- Progress 10.0 and
10.1
- Redbrick 6.1
- Sybase ASE/IQ 12-15x
- XBRL
Other Features
- Deprecation of EDA
API
As of the 7.7.06 and
8.1.x releases, the building of customer EDA API applications for
client communication is in a deprecated state. The distributed source
code examples in etc/src3gl have been removed, as well as references
in the documentation. Existing applications from prior releases
should continue to work with 7.7.06 and 8.1.x until final drop of
the API, which is slated for the next major release. Please report
any conditions in which there are failures.
In most cases,
applications may be re-written using ODBC (by configuring and using the
ODBC Connector) to replace the use of the EDA API. Additionally,
technologies such as CMRUN, -REMOTEBEGIN/END and the WebFOCUS Servlet
may be useful in some cases.
xChange in Default Code Page on ASCII Platforms
As of Version 7 Release 7.06, the default code page
on ASCII platforms is 1252.
xChange in Default for the ACRSVRBTITL Parameter
As of Version 7 Release 7.06, the default value for
the ACRSVRBTITL parameter, which controls the display of the title
of a single field in an ACROSS group, has been changed to HIDEONE.
xElimination of the SESSION_EXPIRATION Listener Parameter
As of Version 7 Release 7.06, the SESSION_EXPIRATION
setting and the foccache_maxage setting have been combined under
the setting foccache_maxage. When a session is expired, the session
foccache files are expired as well, and are removed from the operating
system so that no unexpired files are left on foccache directories
after the user session is expired.
If you are using an odin.cfg file from a prior release, and it
has a SESSION_EXPIRATION setting, then the longer interval of the
two (foccache_maxage and SESSION_EXPIRATION) is chosen to expire
both the session and the session foccache files.
The SESSION_EXPIRATION setting has been removed from the Web
Console. To set a session expiration, use the foccache_maxage setting.
This setting is under Application Settings on the Web Console Applications
page.
xImplementation Change to the User Home Application
In Version 7 Release 7.06,
the home application for any user who is not a server administrator
appears in two places on the Web Console application tree. Both
of these applications point to the same physical location, so that
that they can be referenced in two ways. The two applications are:
- Application myhome,
which is prepended to APPPATH.
- Application homeapps,
which is appended to APPPATH and can be expanded to see the user
home application stored with a name that matches the user ID, such
as pgmtst1.
Server administrator users have the myhome application prepended
and the homeapps application appended to APPPATH, The homeapps folder
can be expanded to show the home applications for all users.
The following image shows both the myhome
application and the homeapps application for user pgmtst1:
The files created in home applications can be referenced in procedures
as myhome/procname.fex and homeapps/pgmtst1/procname.fex
The first type of reference can be ported easily to any user.
It enables you to create a common application that utilizes data
stored in the home applications of users as myhome/data, so that
each user can run the same procedure but get a report based on the data
stored in the home application of that user.
The second type of reference enables you to run applications
specific to a user, referring to the data and procedure for each
user as homeapps/pgmtst1/proc1.fex and homeapps/pgmtst1/data.
This type of reference can be used for testing applications before
moving them to common application folders.
xDeprecation of the EDA API
As of the 7.7.06
and 8.1.x releases, the building of customer EDA API applications
for client communication is in a deprecated state. The distributed
source code examples in etc/src3gl have been removed, as well as
references in the documentation. Existing applications from prior
releases should continue to work with 7.7.06 and 8.1.x, until final
drop of internal code for the API, which is slated for a later major
release. Please report any conditions in which there are failures.
In most cases, applications may be re-written using ODBC (by
configuring and using the ODBC Connector) to replace the use of
the EDA API. Additionally, technologies such as CMRUN, -REMOTE BEGIN/END
and the WebFOCUS Servlet may be useful in some cases.
x
Version 7 Release 7.06 includes the following changes
to the installation process.
x
IBISAMP Legacy Data Sources
Version 7 Release
7.06 marks a major re-implementation of the way samples and tutorials are
delivered to customers.
In the past, a static application directory named IBISAMP was
created and populated with a number of sample files. Additionally,
there were Web Console and Data Management Console (DMC) folder
options for selecting and creating other samples.
As of 7.7.06, the IBISAMP folder is still created as part of
the installation process, but it is not populated, and you use the
Web Console or DMC folder option New -> Tutorials (or the Tutorials button
on the Web Console Applications page) and its pull-down list to
select and create a particular sample or tutorial.
Because the tutorial creation feature is at the folder level,
you may choose to continue using IBISAMP as the location for creating
the samples or pick any other folder. The pull-down list for Legacy
tutorials will create most of the sample files that were in IBISAMP previously
into the selected folder, but not all of them. Some of the prior
files were DataMigrator related, and these tutorials were moved
to occur under their specific tutorial pull-down.
Under z/OS PDS Deployment, there are some additional restrictions.
The z/OS PDS JSCOM Listener option must have been selected at installation
time as this option also “co-installs” various HFS source files
that are used by the various tutorial creation options. If the HFS
files of a z/OS PDS Deployment are not present, a tutorial creation
request will produce a specific HFS files not found message.
Note that not all tutorials are implemented for z/OS, so selecting
a particular tutorial creation request may produce a not implemented message.
x
As of Version 7 Release 7.06, the default security provider
configured during installation is the PTH (server internal) security
provider. A default server administrator user ID is established
for this security provider. The installer can accept the default,
or change it, but must provide a password for this server administrator
user ID. This enables the server to start with security immediately
after installation. It is recommended that you keep this server
administrator user ID and password as a backup.
All new security subjects for all security providers will be
registered with a two-part name, provider\userid or provider\groupid.
If one-part name registrations exist from a prior release, they
are respected and are assumed to be primary provider registrations.
Support is now provided for cutting SMF records with non-OPSYS
security providers (LDAP, PTH, DBMS). Therefore, the user ID fields
in our SMF records have been increased to 20 characters to accommodate
a reasonable size for longer user IDs under z/OS.
x
HTML modes (HTML-Default, HTML-Blue, and HTML-Gray)
are no longer available as Web Console Appearance options, as of
Version 7 Release 7.05.
xPlatform Naming Conventions
Vendors occasionally change the name of their operating
system and hardware, but effectively there is no technical change.
The term IBM i generically refers to all OS/400
and i5/OS operating system releases as of Version 5, regardless
of hardware name changes that have occurred, such as iSeries, Series
i and the more recent change to IBM i.
The term Solaris also generically refers to SunOS regardless
of hardware or release level.
xServer Installation for Windows
As of the 7.7.04 Windows server installation, the Start
Security options have changed. The Start With Alternate
Security Modes folder has been removed. The Start
Security OPSYS option has been changed to Start
Security ON. A new Start Security OFF option
has been added. More information on new security options and the security
changes in 7.7.04 is available in the Security topic
of the Server Enhancements chapter in the New
Features Version 7 Release 7.04 manual.
As of the Version 7 Release 7.02, separately installable debuggable
versions are no longer required to get a full stack trace of information
for a savediag. The Debuggable Version - Install
and Debuggable Version - Remove options
have been removed from the Windows menu.
If you have an earlier Version 7.7.x release that contains the
debug menu options, and have installed service pack upgrades of
7702 (or higher), these menu options should be deleted, since they
no longer function or are needed.
The size of a Windows installation has also changed, since the
debuggable information is now carried as .pdb files that are not
optional. While this change does increase disk space requirements,
it is beneficial since abnormal terminations now produce a full
stack trace without extra steps, speeding problem resolution.
xSupport for SunOS Version 11
The server is now certified to support SunOS Version
11 for both SPARC and i86pc.