x

Releases prior to 7.7.06 pre-load various samples into the IBISAMP application. As of 7.7.06, on a new installation, the IBISAMP application is created, but is not pre-loaded. The server Web Console has a new feature on the ribbon and on the application tree (under new), Tutorials (the Create Tutorial Framework page), which has a pull-down for various samples. The DMC also has this feature on the application tree.

There are currently about 10 different tutorial/sample selections available on the pull-down select list to match various customer needs. The bulk of the prior IBISAMP sample objects can be generated by selecting the Create Legacy Sample Tables and Files tutorial. Other prior IBISAMP Data Migrator sample objects (usually starting with the characters dm*) are now loaded by choosing their respective Data Migrator tutorials. Under the new method, the tutorials/samples may be loaded to any application, not just IBISAMP.

If you are doing just a software refresh, the prior IBISAMP objects will be unchanged (because a refresh does not touch app directories).

x

When the effective number of CPUs (cores) on a computer exceeds the number allowed by the server license, depending upon the license, either the server will not start or users will be given warnings in edaprint.log and at Web Console or Data Management Console login.

To correct the situation, the installation site has two choices:

• Install the server on a computer with a physical number of CPUs/cores that is less than or equal to the license amount.
• Create a virtual environment using VMware or Microsoft Virtual PC with a number of cores that matches the license requirement, and run the server instance under one of these virtualization options.

Note: Running multiple instances of the server (each under a limited virtual processor set) or adding processors to the virtual set after the server is running, constitutes a license violation.

Microsoft Virtual PC only supports single CPU/core virtualization, while VMware supports multiple CPU/cores. Both offer converter tools to reimage a PC into a virtualization. At server installation time, if a site is in violation, the site has the option of continuing (and converting to virtualization afterwards) or stopping the initial install to reattempt the installation in an environment that is already virtualized correctly.

The specifics of installing and configuring VMware and Microsoft Virtual PC or the use of their respective converter tools are beyond the scope of this document. From the perspective of a server installation, the installation utility does not know that virtualization has occurred and there is no difference. Consult the related virtualization documentation for further information on the use of these features.