Note: For information about upgrading from Extra! Personal Client 6.x (which did not use the Microsoft Windows Installer), see KB 7021890.
Understanding the User Data Location
The User Data Location is the folder that is used to store your users’ session, scheme, and macro files (and their respective subdirectories). Extra! X-treme 9.x Setup offers the following options:
- My Documents: Store user data files in a personal My Documents folder, typically C:Documents and Settings<username>My DocumentsAttachmateExtra! where <username> is the user logged into Windows at install time.
- Application: Store user data files in the application installation folder, typically C:Program FilesAttachmateExtra! (or C:Program FilesAttachmateE!E2K). Note: If you select this option on Windows Vista, running Extra! requires elevated or special permissions due to User Account Control (UAC) security.
- All UsersDocuments: Store user data files in the All UsersDocuments folder for sharing by multiple users, typically C:Documents and SettingsAll UsersDocumentsAttachmateExtra!.
- User-Defined: Store user data files in a different folder (entered at setup). To store data files in different folders based on the logged-in Windows user at runtime, see also KB 7024219.
Note: Beginning with version 9.4, new installations of Extra! use MicroFocus instead of Attachmate.
Should I Do a Manual Upgrade?
Determine whether you will perform an automatic or manual upgrade:
- Identify the location that is currently being used by your existing installation of Extra! X-treme 8.0, myEXTRA! Enterprise 7.1, or Extra! Enterprise 2000.
- Decide which location is appropriate in your environment for use with Extra! X-treme 9.x.
- If you will continue using the same User Data Location, you can do an upgrade by over-installing Extra! X-treme 9.x. Setup will automatically detect and upgrade the earlier version. This process will un-install the previous version of Extra! and, create a new installation with the existing directory, registry settings, and user configuration files.
If you plan to change the User Data Location, we recommend you follow the instructions in this note, which include manually uninstalling the earlier version of Extra! before installing Extra! X-treme 9.x.
Preparing for the Manual Upgrade
Please review the following suggestions and collect the information described in the steps below before you begin the manual upgrade process.
- Review the readme files and documentation to become familiar with the new features and any new configuration options of Extra! X-treme 9.x. Make sure the operating system and hardware are compatible with the new version of Extra! before proceeding.
Extra! Documentation: https://support.microfocus.com/manuals/extra.html
- Create a “test” system that is non-critical to your daily work that can be used for testing the new version of Extra! to verify that it works properly before performing wide-scale upgrades. This test system is also good to have available during the initial deployment of the new version of Extra! if problems arise during the upgrade process.
- Identify and create secure backups of critical Extra! configuration files to carry forward. These include any files found in the Macros, Schemes, and Sessions subdirectories under the C:Program FilesAttachmateE!E2K or C:Program FilesAttachmateExtra! directory. Included with these will be the APPN Node configuration file called DEFAULT.XCP and the Security file called DEFAULT.ESF.
- You may want to capture screen shots of critical configuration panels or screens in the Extra! configuration that can be used for later reference during the Extra! 9 installation. Important screens include the Host Connection information and Global Preferences.
Note: If using the HLLAPI interface of Extra!, open the Global Preferences and record the HLLAPI Transport Type, HLLAPI Shortname Associations, and the HLLAPI Shortname information.
- Take a “snapshot” of the Attachmate registry settings. This snapshot can be used to determine any special settings that may have been in use with the earlier version of Extra! after that product is uninstalled.
Warning: These instructions should be carried out by a user with Administrative rights to the PC and who is familiar with registry manipulation tools. Proceed with extreme caution when editing the Windows Registry. Use Registry Editor at your own risk. For full details and warnings regarding editing the Windows Registry, see Microsoft Article 256986:
- Open Regedit.exe.
- In the left panel of the Registry Editor window, navigate to the following locations:
- Export each selected branch to a Registry Hive file. Refer to the Microsoft Windows web site for detailed instructions about how to export a Registry Hive. This can be viewed as a text file if needed at a later date.
Performing the Manual Upgrade
After collecting the information in the Preparing for the Upgrade section above, follow these steps to manually upgrade to Extra X-treme 9.x:
- Uninstall the earlier version of Extra! using Add/Remove Programs in Control Panel. This will remove the Extra! program files from the C:Program FilesMicro FocusE!E2K or C:Program FilesAttachmateExtra! directory but will leave the customized user configuration files.
- Decide where the user configuration files will be located (refer to Understanding the User Data Location).
- Decide if you need to create an Administrative Install point with a customized Transform file (MST), or if the base product only can be installed. Review the product documentation and the Custom Installation Wizard documentation to determine what is appropriate for your environment.
Extra! X-treme documentation: https://support.microfocus.com/manuals/extra.html
- Install Extra! X-treme 9.x using the SETUP.EXE program or the MSI file and a Windows Installer msiexec command line.
- Copy existing user configuration files to the new user data location (as described in Understanding the User Data Location).
Examples (These examples assume the previous Extra! installation was to the Application directory.)
My Documents Directory Install:
C:Documents and SettingsusernameMy DocumentsAttachmateExtra!Macros
C:Documents and Settings<username>My DocumentsAttachmateExtra!Schemes
C:Documents and Settings<username>My DocumentsAttachmateExtra!Sessions
Application Directory Install:
Note: If you use this location on Windows Vista, running Extra! requires elevated or special permissions due to User Account Control (UAC) security.
All Users Directory Install:
C:Documents and SettingsAll UsersDocumentsAttachmateExtra!Macros
C:Documents and SettingsAll UsersDocumentsAttachmateExtra!Schemes
C:Documents and SettingsAll UsersDocumentsAttachmateExtra!Sessions
Completing the Upgrade
- After the installation of Extra! X-treme 9.x is complete, thoroughly test the features and functionality.
- Verify that the Windows PATH environment variable, if it was set to include the directory of the previous version of Extra!, is changed to the new installation directory for Extra! X-treme 9.x.
- Store a backup copy of critical user configuration files in a secure location. These files can be used to restore the old version of Extra! if necessary.
- When you are satisfied that the new version of Extra! is working, you can delete the old user configuration directory to avoid any confusion about which directory structure and set of configuration files is currently in use.
This will make kdump act in a manner similar to the older netdump mechanism: the capture environment will go up to runlevel 3 (where network connectivity is enabled) and will use the secure copy command scp to transfer the kernel core dump to a separate system.
2. for SLES11
add the network device to be used to the variable: KDUMP_NETCONFIG in /etc/sysconfig/kdump.
In order to automatically set up a network device, pass the option “auto”. This is also the default.
For a custom setup, pass a string that contains the network device and the mode (dhcp,static), separated by
a colon, for example: “eth0:static” or “eth1:dhcp”.
If you use “static”, you have to set the IP address with ip=ipspec. ipspec is <client>:<server>:<gateway>:<netmask>:<hostname>:<device>:<proto>
as boot parameter. See mkinitrd(8) for details.
Pass the dumping method and the destination directory to the parameter: KDUMP_SAVEDIR in /etc/sysconfig/kdump
Supported methods are:
FTP, for example “ftp://user:password@host/var/log/dump”
SSH, for example “ssh://user:password@host/var/log/dump”
NFS, for example “nfs://server/export/var/log/dump”
CIFS (SMB) , for example “cifs://user:password@host/share/var/log/dump”
See also: kdump(5) which contains an exact specification for the URL format.
The existing Windows Firewall configuration prevents the remote loader from receiving any password changes as captured by the PWFilter.dll on other Domain Controllers within the domain. To solve this problem, do the following:
On the Windows Server firewall, (required only on the server which hosts the Active Directory Remote Loader) add the following rules:
— Inbound Rules —
Name Group Profile Enabled Action Override Program Local Address Remote Address Protocol Local Port Remote Port Allowed Users Allowed Computers.
dirxml port 8090 IN Domain Yes Allow No Any Any Any TCP 8090 Any Any Any
dirxml process dirxml_remote.exe IN Domain Yes Allow No %SystemDrive%NovellRemoteLoaderdirxml_remote.exe Any Any Any Any Any Any Any
NOTE: The port number should be the port number specified on the Remote Loader configuration. So instead of 8090, it will be whatever you specified in the configuration.
No specific Outbound Rules are needed.
The rules can be given any name.
They rules must be assigned to at least the Domain profile.
If using the 64 bit remote loader, the path differs: %SystemDrive%NovellRemoteLoader64bitdirxml_remote.exe
The rules can be also added from the command line using the following commands, modifying the port and path as applicable:
netsh advfirewall netsh advfirewall firewall add rule name="dirxml port 8090" dir=in action=allow enable=yes profile=domain protocol=TCP localport=80
netsh advfirewall firewall add rule name="dirxml process dirxml_remote.exe" dir=in action=allow program="%SystemDrive%NovellRemoteLoaderdirxml_remote.exe" enable=yes profile=domain
1. Will Micro Focus release updates for Oracle JDK 8 or JDK 11 for Identity Manager?
Answer: No, Identity Manager will be distributing the Azul Open JDK moving forward. Any improvements, fixes and security concerns will be addressed based on the Azul Open JDK.
2. What if you are using an older version of Java (release prior to January 2019) in Identity Manager? Will you be responsible for any additional license fees?
Answer: No. Only newer updates specific to Oracles JDK that are post January 2019 require and licensing. Further, the vendor that redistributes the Oracle JDK is responsible for the licensing. If you are using a version of Oracle JDK prior to January 2019, no additional licensing is required
The parameter to configure the SSL between the Remote Loader andthe Engine is then added to the end of this as follows:
hostname=ipAddressOrDNSNameOfServerport=8090 kmo=’Certificate Short Name’
In this example the name of the certificate (an object of class’NDSPKI:Key Material’) associated with the server hosting the IDM(Identity Manager) engine is ‘Certificate Short Name’ and must be wrapped accordinglyin single quotation marks. The full name of the certificateas shown in iManager or ConsoleOne would look something like thefollowing:
Certificate Short Name -serverName
Via LDAP it may have looked like the following:
cn=Certificate Short Name -serverName,dc=servername,dc=server,dc=system
Keep in mind that only the short name of the certificate is used inthe Key Material Object (KMO) parameter within the driver configuration. On theRemote Loader side the exported trusted root certificate from thiscertificate or the self-signed certificate from the tree CA shouldbe imported per the Novell Identity Manager documentation.