tivoli integrated portal 2.2.0.7 installation and ... · pdf fileibm-portal-topology.xml being...
TRANSCRIPT
Version 1.1 Tivoli Integrated Portal 2.2.0.7
Tivoli Integrated Portal 2.2.0.7Installation and troubleshooting guide
���
Version 1.1 Tivoli Integrated Portal 2.2.0.7
Tivoli Integrated Portal 2.2.0.7Installation and troubleshooting guide
���
NoteBefore using this information and the product it supports, read the information in “Notices” on page 23.
This edition applies to version 2, release 2, fix pack 7 of Tivoli® Integrated Portal and to all subsequent releases andmodifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.
Contents
Tivoli Integrated Portal 2.2.0.7 fix packoverview . . . . . . . . . . . . . . 1
Authorized Problem Analysis Reports(APARs). . . . . . . . . . . . . . . 3
Installing Tivoli Integrated Portal 2.2.0.7fix pack . . . . . . . . . . . . . . . 5Installing Tivoli Integrated Portal 2.2.0.7 fix pack insilent mode . . . . . . . . . . . . . . . 6
Silent mode response file parameters for fix packs 8Uninstalling Tivoli Integrated Portal . . . . . . . 9
Uninstalling a fix pack in silent mode . . . . . 9
Troubleshooting fix pack installations 11Installation errors . . . . . . . . . . . . 11
Non-root installation fails on Solaris 64-bitsystem . . . . . . . . . . . . . . . 11Insufficient disk space for install . . . . . . 12Log files . . . . . . . . . . . . . . 12Install fails after deployment engine upgrade . . 14Installation fails on Windows Server 2008 . . . 14Setting the libstdc++ level for Linux systems . . 15Installation fails with error code ADMR0104E inSystemOut.log . . . . . . . . . . . . 15
Connection Manager . . . . . . . . . . . 15Connection Manager data not synchronized afterinstallation in load balanced environments . . . 16
Websphere Application Server Network Deploymenttracing . . . . . . . . . . . . . . . . 16
WebSphere Application Server NetworkDeployment trace service issue . . . . . . . 16
Charting . . . . . . . . . . . . . . . 16Bar or line chart does not display in InternetExplorer 9 . . . . . . . . . . . . . . 17
User management . . . . . . . . . . . . 17Implications of special characters in a user ID . . 17Manage Users and Manage Groups taskbar tabsmissing . . . . . . . . . . . . . . . 18
Exporting and Importing . . . . . . . . . . 18Rules for exporting . . . . . . . . . . . 18Rules for importing. . . . . . . . . . . 19Importing specific plugins . . . . . . . . 21
Notices . . . . . . . . . . . . . . 23Trademarks . . . . . . . . . . . . . . 24
Index . . . . . . . . . . . . . . . 25
© Copyright IBM Corp. 2012 iii
iv Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Tivoli Integrated Portal 2.2.0.7 fix pack overview
Use this fix pack to update your Tivoli Integrated Portal 2.2.0.x environment toTivoli Integrated Portal 2.2.0.7.
Tivoli Integrated Portal 2.2.0.7 is a cumulative fix pack and includes fix for allissues since the release of Tivoli Integrated Portal 2.2. This fix pack updates yourexisting Tivoli Integrated Portal 2.2.0.x environment to Tivoli Integrated Portal2.2.0.7 regardless of its current version number.
© Copyright IBM Corp. 2012 1
2 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Authorized Problem Analysis Reports (APARs)
APARs addressed in the IBM Tivoli Integrated Portal in recent fix packs.
APARs:
v IBM Tivoli Integrated Portal version 2.2.0.3:– PM34540 - ITM webservice does not fetch charts from ITM when SSL is
enabled in ITM– PM37499 - Preupgreade script fails when not using the default certificates– PM37773 - Page "Define Resource View" does no remember its portlets sizes if
opened automatically after login– PM40211 - ERROR CWLAA6003 IS OCCURRING WHEN SEARCHING FOR
USERS– PM40403 - Invalid unique name exception with upgrade.sh
v IBM Tivoli Integrated Portal version 2.2.0.5:– PM52135 - Execution of scripts in SMUtils.js(DelayedRunscripts) causes stack
overflow– PM52914 - Unable to save changes to Web Widget page with non-English
locale– PM53123 - Session time out message is displayed for new login– PM53928 - Tivoli Integrated Portal Change Password portlet displaying
success message for error– PM54251 - The fix for PM54251 expects that a fresh export be done always– PM54333 - Page Order after Import is not correct– PM54980 - Logging out of an invalid session does not destory the session– PM56341 - Users with no role are able to login to Tivoli Integrated Portal
Version 2.2– PM56529 - Rapidly changing currentPage cause NPE– PM56777 - Error 500 on logout– PM56774 - Error 500 displayed in content area when response already
committed– PM57391 - Handle quick page launches , avoid NPE– PM57573 - tipcli export getting duplicate entries– PM57619 - All authenticated users are able to login to TIP– PM58398 - MergeRoles issue– PM58585 - Duplicate page entries created when importing pages within
subfolders– PM59093 - Unable to navigate to any custom views because of default
ibm-portal-topology.xml being used.
© Copyright IBM Corp. 2012 3
4 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Installing Tivoli Integrated Portal 2.2.0.7 fix pack
Tivoli Integrated Portal 2.2.0.7 fix pack can only be installed in silent mode at thecommand line using a response file.
Tivoli Integrated Portal 2.2.0.7 fix pack installation files are available from IBMSupport Fix Central.
You must download 2.2.0-TIV-TIP-FITSuit-FP0007.zip and 2.2.0-TIV-TIP-OSplatform-FP0007.zipWhere OSplatform reflects the operating system and platform architecture (32-bit or64-bit).
Important: This fix pack is designed to be installed in a Tivoli Integrated PortalVersion 2.2 environment only.
Important: The fix pack is available in both 32-bit and 64-bit versions for someoperating systems. Ensure that your fix pack media matches that of the installedTivoli Integrated Portal Version 2.2 instance with regard to operating system andplatform (32-bit or 64-bit).
Important: If you are installing the fix pack into a Tivoli Integrated Portalenvironment that uses a base (non-embedded) version of WebSphere ApplicationServer, you must install WebSphere Application Server Update Installer UPDI)before you install the fix pack. For details on how to install UPDI, see:http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.installation.express.doc/info/exp/ae/tins_updi_install.html
Important: For systems running Microsoft Windows Server 2008, orMicrosoft Windows Server 2008 R2, ensure that you have at least 2.5 GB of freespace in your installation location.
Additionally, the following requirements and restrictions must be considered whenyou install this fix pack:v WebSphere Application Server Version 7.0 (7.0.0.19) or later. WebSphere
Application Server hardware and software requirements apply, for moreinformation, see http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.installation.express.doc/info/exp/ae/rtop_reqs.html
v Ensure that you have installed the IBM version of Java Runtime Environment(JRE) 1.6.0 and that there at least 500 MB of memory available in the tempdirectory for the installation process.
v Before you install the fix pack, you must stop any Tivoli Integrated Portal relatedJava processes that are running on your system.
Tip:
Use the ps command to view details of the Java processes thatare running.
Use a services utility to view the paths associated with each Javaprocess.
© Copyright IBM Corp. 2012 5
After the installation, the Tivoli Integrated Portal administrator and any registeredusers can log in to the Tivoli Integrated Portal by entering the URL in a browser,for example, if you installed using default port numbers, you would access theconsole using the following web address:v http://localhost:16310/ibm/console
Note: Fix pack installation logs are saved to TIPFPInstaller-xx.log located in theia directory contained in the following zip archive: tip_home_dir/22_FP7.logs.zip.Related reference
“Non-root installation fails on Solaris 64-bit system” on page 11A non-root user installation on a Solaris 64-bit system may fail where TivoliIntegrated Portal had been previously installed by the root user.
Installing Tivoli Integrated Portal 2.2.0.7 fix pack in silent modeThe Tivoli Integrated Portal 2.2.0.7 fix pack silent installation uses a response filethat is included with your fix pack media that you can edit as needed.
Before you begin
If necessary, download and extract Tivoli Integrated Portal 2.2.0.7 fix packinstallation files from IBM Support Fix Central.
Your must download two files:v Fix Pack Intelligence Tool: 2.2.0-TIV-TIP-FITSuit-FP0007.zip
Download and extract this file to the following directory associated with yourexisting Tivoli Integrated Portal 2.2.0.x environment:tip_home_dir/profiles/TIPProfile/etc
v Tivoli Integrated Portal 2.2.0.7 fix pack installation package:2.2.0-TIV-TIP-OSplatform-FP0007.zipWhere OSplatform reflects the operating system and platform architecture (32-bitor 64-bit).Download and extract the relevant file for the system running your existingTivoli Integrated Portal instance to a directory of your choosing.For example, if your system is running a 64-bit version of HP-UX, you mustdownload and extract 2.2.0.7-TIV-TIP-HPUX64-RP0001.zip
Note: The Tivoli Integrated Portal 2.2.0.7 fix pack installation package ziparchive includes a Readme.txt that provides guidance when installing the fixpack.
When you are installing Tivoli Integrated Portal 2.2.0.7 fix pack in a load balancedenvironment. You must remove all nodes from the cluster and install the fix packon each node separately. Once all nodes are updated, you can rejoin the nodes tothe cluster. For more information on joining and removing nodes, see:v http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/
com.ibm.tip.doc/ttip_config_ha_unjoin.htmlv http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/
com.ibm.tip.doc/ttip_config_ha_join.html
6 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Important: When you are installing the fix pack on a HP Integrity (Itanium) 64-bitserver running HP-UX, before you start the installation, as root, you must clear thecontents of the following directory:/var/tmp
About this task
The fix pack silent installation proceeds automatically, using the settings as theyare specified in a response file (for example, sample_response.txt). Before you runthe installation, edit this file to specify the choices and values to be used by the fixpack silent installer. The response file can be re-used on other computers whereyou would like the same kind of fix pack installation. In these steps, be sure toprovide the complete (absolute) path of the response file for the silent installer.Otherwise, the installer will not find the response file and the installation fails.
Restriction: On systems running Windows, the file path to your fix packinstallation files should be less than 40 characters in length. For example, if thepath to your installation files is image_dir\cdimage.fixpack, then the pathrepresented by the variable image_dir should be less than 40 characters long.
Procedure1. Open your response file in a text editor (for example, sample_response.txt)
and review the configuration settings. Edit as needed, then save and close thefile.
Important: Ensure that you provide the correct Tivoli Integrated Portaladministrator ID and password in the response file, that is, the administratorID and password associated with the existing Tivoli Integrated Portal version2.2.0.x installation.
Restriction: The value that you provide for IAGLOBAL_TIP_HOME in theresponse file is case sensitive and it must exactly match the path to the existingTivoli Integrated Portal instance (or WebSphere Application Server instance,where you are installing into a base WebSphere Application Serverenvironment).
2. At the command line, change to directory that contains your response file.3. Enter the following at the command line:
v ./install.sh -i silent -f full_path_to_response_file
v install.bat -i silent -f full_path_to_response_file
Where:full_path_to_response_file is the absolute path to the location of the responsefile (for example, C:\cdimage\sample_response.txt).
Note: full_path_to_JRE should not include the bin subdirectory.
Ensure that you enter escape characters the way the Java properties expectsthem. Non-text characters must be UTF-8 escaped (such as \u0022 for the "double-quote character).
What to do next
The passwords entered in the response file can be seen by anyone who reads thefile. When you are done using this file, delete it or move it to a secure place tokeep passwords secure.
Installing Tivoli Integrated Portal 2.2.0.7 fix pack 7
Silent mode response file parameters for fix packs
The passwords entered in the response file can be seen by anyone who reads thefile. When you are done using this file, delete it or move it to a secure place tokeep passwords secure.
INSTALLER_UI=SILENTThis parameter indicates that Tivoli Integrated Portal is to be installed in silentmode and it should not be altered.
IAGLOBAL_TIP_HOME=tip_home_dir
Restriction: The value for IAGLOBAL_TIP_HOME is case sensitive and itmust agree with the path for the existing Tivoli Integrated Portal instance.v If the existing Tivoli Integrated Portal 2.2 instance is not associated with a
WebSphere Application Server base installation, specify the location of theexisting Tivoli Integrated Portal 2.2 instance. The default directory providedis:– C:\\IBM\\tivoli\\tipv2. The \ backslash is seen as an escape
character. Use \\ two backslashes when defining the path.– /opt/IBM/tivoli/tipv2
v If the existing Tivoli Integrated Portal instance is associated with aWebSphere Application Server base installation, you must specify thelocation of the WebSphere Application Server base installation. For example:– C:\\IBM\\WebSphere\\AppServer. The \ backslash is seen as an
escape character. Use \\ two backslashes when defining the path.– /opt/IBM/WebSphere/AppServer
IAGLOBAL_WASUserID=tip_admin_IDIALOCAL_WASPassword=tip_admin_password
These parameters are for defining the administrator ID for the applicationserver profile. The values that you provide for IAGLOBAL_WASUserID andIALOCAL_WASPassword must match the administrator ID and passwordassociated with the existing Tivoli Integrated Portal Version 2.2 installation.
IAGLOBAL_UPDI_HOME_19=UPDI_home_dir
Important: This setting is for advanced users and typically no path need bespecified.To specify a custom path, uncomment the parameter by removing the hashcharacter (#) preceding it and providing a custom path to an instance of theUpdate Installer for WebSphere Application Server. If the specified versiondoes not match the required version, the installation will not succeed.
IAGLOBAL_enableOSPrereqChecking=false
Important: This setting is for advanced users and typically you can accept thedefault setting (false).This parameter, when set to true enables operating system prerequisitechecking, and allows the installation to continue and log warnings even ifprerequisite checking fails.
IAGLOBAL_COI_SELECTED_LOGICAL_COMPONENTS=Common,TIPFinalThis parameter indicates which components are to be installed. You must atleast include the default values (Common,TIPFinal). Ensure that the additional
8 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
components are available to the installer at cdimage/COI/PackageSteps. Forexample, to install the BIRTExtension component enter a value ofCommon,TIPFinal,BIRTExtension.
IAGLOBAL_LOCALE=enThis parameter indicates the locale of the resource bundle for the installation.
Uninstalling Tivoli Integrated PortalUninstall Tivoli Integrated Portal when you no longer need it on a computer.
Important: WebSphere Application Server fix packs and interim fixes are notremoved when you uninstall Tivoli Integrated Portal.
Important: If you are uninstalling Tivoli Integrated Portal as a non-administrativeuser and you previously installed this instance of Tivoli Integrated Portal into anexisting Tivoli Integrated Portal environment that had been installed by anadministrative user, you may see the following error in the log files:
Caused by: com.ibm.ac.si.install.InstallUnauthorizedException: ACUINI0040WUser, user_ID, does not have proper authority!
In this particular circumstance, the error message may be ignored and no furtheraction is required.
Uninstalling a fix pack in silent modeUse the silent uninstaller to roll back Tivoli Integrated Portal to its state before afix pack was installed.
About this task
The silent mode fix pack uninstaller rolls back an instance of Tivoli IntegratedPortal to its state prior to installing the fix pack. Normally, you would uninstall afix pack immediately after installing it in cases where the installation provedproblematic. Uninstalling a fix pack after using the updated Tivoli IntegratedPortal for a prolonged period may result in the loss of a significant amount ofdata. This uninstallation mode uses a response file (for example,uninstall_response.txt). The file has a number of parameters:v IAGLOBAL_WASUserID=tipadmin - This is the administrator's user ID.v IALOCAL_WASPassword=mypassword - This is the administrator's password.
To uninstall Tivoli Integrated Portal in silent mode:
Procedure1. From the command line, change to the following directory:
tip_home_dir/_uninst/TIPInstall2201
2. Enter this command:v ./uninstall.sh -i silent -f
full_path_to_response_file
v uninstall.bat -i silent -f full_path_to_response_file
Installing Tivoli Integrated Portal 2.2.0.7 fix pack 9
Restriction: After uninstalling the fix pack, due to a caching performanceenhancement added in Tivoli Integrated Portal Version 2.2.0.3, it is stronglyrecommended that you clear your browser's cache before logging back into theportal.
3. After the process is complete, delete the tip_home_dir branch from the tivolidirectory (such as C:\IBM\ and /opt/IBM/) if it still remains and there are nopreviously installed applications in that branch that you want to keep.
10 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Troubleshooting fix pack installations
Consult these troubleshooting notes to help determine the cause of a problemwhen you are installing a fix pack and what to do about it.
Installation errorsReview the preparing to install topics before starting an installation; review thetopics here for handling errors that might arise during the installation.
Non-root installation fails on Solaris 64-bit systemA non-root user installation on a Solaris 64-bit system may fail where TivoliIntegrated Portal had been previously installed by the root user.
If you install Tivoli Integrated Portal as a non-root user on Solaris 64-bit systemthat previously had an instance of Tivoli Integrated Portal installed by the rootuser, then the installation my fail.
It has been observed that the following file is not always removed during theuninstallation of the root installed instance:
/var/tmp/responsefile.updiinstaller.txt
When the non-root installation process attempts to write to the updiinstaller.txtfile, the installation fails due to the non-root user not having sufficient permissions.
The solution is to delete the responsefile.updiinstaller.txt file and restart thenon-root installation.Related concepts
“Installing Tivoli Integrated Portal 2.2.0.7 fix pack” on page 5Tivoli Integrated Portal 2.2.0.7 fix pack can only be installed in silent mode at thecommand line using a response file.
© Copyright IBM Corp. 2012 11
Insufficient disk space for installHave enough space in the temporary directory for the installation or it will fail.
Your product installation requires at least 500 MB of disk space for the temporaryfiles that are used during installation. On Linux and UNIX, allocate enough spacein the /tmp or /opt directory of the computer.
Important: For systems running Microsoft Windows Server 2008, orMicrosoft Windows Server 2008 R2, ensure that you have at least 2.5 GB of freespace in your installation location.
Log filesLocate and review the logs and related files after an installation to confirm that thecomponents were successfully installed.
Here are the logs created during a Tivoli Integrated Portal installation. The installercreates a log called TIPFInstaller-xx.log, which is located in the user's homedirectory. This should be the first log reviewed. It shows the installation as itprogresses, giving tracing information. Each step that is executed in the installationcreates a log in the tip_home_dir/logs directory.
Tivoli Integrated PortalvalidatePrereqs.*backuptip.*propagateTIPRoles.*retrieveSigners.*
Administrative consolecreateProfile.errcreateProfile.outcreateTIPService.errcreateTIPService.outdeleteProfile.err (uninstall)deleteProfile.outenableAppSecurity.errenableAppSecurity.outextendJaveMemory.errextendJaveMemory.outmodifyWASServiceName.errmodifyWASServiceName.outremoveTIPService.err (uninstall)removeTIPService.out
Common Gateway Interface ServerCGIServer.errCGIServer.outconfigureIAuthzShLib.errconfigureIAuthzShLib.outdeployiAuthzEar.errdeployiAuthzEar.out
Enterprise Storage ServerdeployESSApplication.errdeployESSApplication.outESSConfiguration.errESSConfiguration.outosgiCfgInit.errosgiCfgInit.out
IBM Tivoli Monitoring Web ServiceITMWebServiceEAR.errITMWebServiceEAR.out
12 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Load BalancingcreateTipDataSource.errcreateTipDataSource.outHADBInstall.errHADBInstall.outHADBJoin.errHADBJoin.out
ChartingassignChartAdminRole.errassignChartAdminRole.outTIPChartPortlet.errTIPChartPortlet.out
Reporting Time Scheduling ServicesTipTssEar.errTipTssEar.outTipTssEWASScheduler.errTipTssEWASScheduler.outTipTssJDBC.errTipTssJDBC.outTipTssSharedLibraries.errTipTssSharedLibraries.out
Tivoli Common Reportingtcr.errtcr.outtcrConfigClient.errtcrConfigClient.outtcrsPostConfig.errtcrsPostConfig.out
Virtual Member ManagerVMM.errVMM.out
VMM LDAP ConfigurationconfigureVMMLDAP.errconfigureVMMLDAP.out
VMM ObjectServer PluginVMMObjectServerPlugin.errVMMObjectServerPlugin.out
WebSpherecheckWAS.errcheckWAS.outstartWAS.errstartWAS.out
Troubleshooting fix pack installations 13
Install fails after deployment engine upgradeRunning the installer on a computer that has an existing Tivoli Integrated Portalenvironment can fail if the deployment engine (DE) was upgraded from a veryearly version.
If you have an old version of the DE installed, the Tivoli Integrated Portal installerwill upgrade it and continue with the installation. On rare occasions certain olderversions of the DE might not be upgraded successfully. When this happens, theinstallation can fail. If you are aware that your product uses a very old version ofthe DE (such as Version 1.2), you can install on the same machine, but sign on tothe portal with a different user name. If your old version of the DE was initiallyinstalled as root user on the Linux or UNIX operating system, consider uninstallingit if your new installation is failing after the DE upgrade.
Installation fails on Windows Server 2008If you add a non-admin user to the Administrators group in Windows Server 2008,you must disable the User Account Control setting for that user in order to installTivoli Integrated Portal.
You can disable the User Account Control setting for a user, as follows:1. Log on to the Windows Server 2008 computer as an administrator.2. In the Control Panel, click User Accounts and Family Safety.3. Click User Accounts.4. Click Turn User Account Control on or off.5. If User Account Control is currently configured in Admin Approval Mode, a
User Account Control message is displayed. Click Continue.6. Clear the Use User Account Control (UAC) to help protect your computer
check box, and then click OK.7. Restart the server to commit your changes.
You can now re-run the Tivoli Integrated Portal installation using the updated user'saccount.
14 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Setting the libstdc++ level for Linux systemsThe Deployment Engine component does not support libstdc++.so.6 or higher onLinux systems.
About this task
Your Tivoli Integrated Portal installation may fail on Linux systems if the libstdc++level is at /usr/lib/libstdc++.so.6 or higher. You must install thecompat-libstdc+-33 packages to successfully install Tivoli Integrated Portal:
Procedure1. On 32 bit and 64 bit systems, run the following command:
$yum install compat-libstdc++-33.i686
2. On 64 bit systems, you must also run the following command:$yum install compat-libstdc++-33.x86_64
3. When the command completes, check that the /usr/lib directory for thepresence of libstdc++.so.5.0.7 and that a symbolic link from libstdc++.so.5to libstdc++.so.5.xx.xx is created.
Installation fails with error code ADMR0104E in SystemOut.logAn installation will fail if a file is created in, or manually added to, a specificWebSphere Application Server configuration directory. An error with the codeADMR0104E is written to SystemOut.log, which provides details for file that causedthe problem.
An installation will fail if a file was created in, or manually added to the followingdirectory, and if the new file's access permissions differ to those of the other files inthe directory:
tip_home_dir/profiles/TIPProfile/config/cells/TIPCell/applications/isclite.ear/deployments/isclite/isclite.war/WEB-INF
In such cases, the following error is written to tip_home_dir/profiles/TIPProfile/logs/server1/SystemOut.log:
ADMR0104E: The system is unable to read document file path:java.io.FileNotFoundException: file path (Permission denied)
To resolve this issue you must move the file indicated in the error message fromthe WebSphere Application Server configuration directory, or ensure that the file isgranted file access permissions similar to those of the other files in the directory.
Once the file is removed or has had its file access permissions updated, you mustrestart the installation process.
Connection Manager
Troubleshooting fix pack installations 15
Connection Manager data not synchronized after installationin load balanced environments
After installing Tivoli Integrated Portal fix pack 2.2.0.7, in load balancedenvironments, Connection Manager data is not initially synchronized.
To synchronize the data, you must stop and restart the Tivoli Integrated PortalServer.
Websphere Application Server Network Deployment tracing
WebSphere Application Server Network Deployment traceservice issue
After installing Tivoli Integrated Portal fix pack 2.2.0.7 in aWebSphere ApplicationServer Deployment Network environment, the WebSphere Application ServerNetwork Deployment trace service may give errors.
You can normally enable tracing through the WebSphere Application Serveradministrative console (Troubleshooting > Logs and Trace > server1 > Diagnostictrace service > Change log detail levels > Runtime and expand the [Allcomponents] item). In a Tivoli Integrated Portal fix pack 2.2.0.7 environment youmay encounter the following error:
Internal error during parse 01 javax.management.JMRuntimeException:ADMN0022E: Access is denied
An error similar to the following error is written to tip_home_dir/profiles/TIPProfile/logs/server1/SystemOut.log:
0000001c RoleBasedAuth A SECJ0305I: The role-based authorization checkfailed for admin-authz operation TraceService:listAllRegisteredGroups.The user UNAUTHENTICATED (unique ID: unauthenticated) was not grantedany of the following required roles: deployer, operator, configurator,monitor, administrator, adminsecuritymanager, auditor.
To resolve this issue, you must run the following command:tip_home_dir/profiles/TIPProfile/bin iscdeploy.sh -restoreProfiles
Charting
16 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Bar or line chart does not display in Internet Explorer 9A bar or line chart may display correctly in Internet Explorer 9 unless the browseris reset to its default settings.
A bar or line chart may fail to display correctly in Internet Explorer 9 if itsconfiguration settings are not in the default state. To ensure that such a chartdisplays correctly in Internet Explorer 9 you must reset the browser.
To reset Internet Explorer 9 refer to the following Microsoft topic:http://windows.microsoft.com/en-US/windows7/Reset-Internet-Explorer-settings-in-Internet-Explorer-9
User management
Implications of special characters in a user IDSpecial characters in a user ID can cause problems depending on the character andthe type of user repository that is used.
Table 1 outlines details for special characters in user IDs that may cause problems.If you can avoid it in a user ID, do not use any of the characters listed. Theimplications of using such characters varies on whether you are using a file-baseduser repository or a central user repository, for example, LDAP.
Table 1. Limitations for special characters in user IDs
Special character notes Notes
Characters that are note supported in TivoliIntegrated Portal user IDs.
Multiple spaces and backslash (\)characters are not supported in TivoliIntegrated Portal. This limitation appliesto environments that have use a localfile-based user repository and also toenvironments that use a central userrepository, for example, LDAP.
Characters that need to use a backslash (\) whenusing tipcli commands if they are provided asarguments to list parameter queries. For example,for a user ID of x:x%a,bc=yy, to view a list of userIDs containing this string, enter the followingcommand:
tipcli.sh/bat --usersList "x\:x%a,bc\=yy
equals sign (=)
quotation mark (")
colon (:)
For characters that are invalid in relation to filenames, Tivoli Integrated Portal substitutes thecharacters so that they are allowable in file paths.
For example, for a user ID ofx:x%a,bc=yy the following file path isused its user preferences:
...\isc.dir\x%colon_x%%a,bc=yy
If you need to remove deleted users from roles, use the following tipcli commandto remove any users that cannot be found:
tipcli ListUsersFromRole --username tip_admin_userid --passwordtip_admin_password --roleName role_name -delete
Troubleshooting fix pack installations 17
Manage Users and Manage Groups taskbar tabs missingPages associated with the Manage Users and Manage Groups nodes in thenavigation pane do not show tabs in the taskbar.
When you click on the Manage Users or Manage Groups node in the navigationpane, the relevant page is displayed in the content area, but no tab for the selectedpage is available in the taskbar.
This is a known issue and it will be corrected in a future release.
Exporting and Importing
Rules for exportingWhen exporting customized configuration data, it is important to know the rulesgoverning the export function and the options available to you.
The following rules apply when exporting customized configuration data from aTivoli Integrated Portal environment:
Rules and options for pages
Rule
1. You can export a particular page by page ID or choose to export allpages.
2. You can export pages associated with a particular view.3. You can export pages that are associated with a particular portlet from
a particular WAR.4. If a page contains multiple portlets, but only some from a specified
WAR, then all elements of the page are exported.5. Pages that are targets of a wire for a specified page are exported.6. The default export scope is All if you do not define pages to be
exported under rule 2 and rule 3.7. The default export scope is NONE if you define pages to be exported
under rule 2 and rule 3.
Rules and options for views
1. You can export a particular view by view ID or choose to export allviews.
2. You can optionally export all views that contains a specified page.3. The default export scope is All.4. You can optionally export all pages associated with the views that you
want to export.5. If an view has a default node in the navigation pane associated with it,
then that page is automatically exported with the view.6. Views that match the following conditions should not be exported as
the subsequent import of that view will fail:v An empty view, that is, a view that contains no pages or roles.v A view that contains roles, but no pages.v A view that contains empty pages, that is, the page exists but it does
not contain portlets.
18 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Rules and options for custom roles and role preferences (console preferenceprofiles)
1. You can export a particular role by role ID or choose to export all roles.2. You can export a custom role and role preference that is associated with
a specified page or view.3. The default export scope is set to All, unless the
includeEntitiesFromApps parameter has been specified for a page orview, whereby it is then set to REQUIRED.
4. If a console preference profile has a custom view as its default view,then that view is automatically exported. If the exported view has adefault node in the navigation pane, then the associated page isautomatically exported with the view.
Rules and options for user preferences
1. You can export user preferences by user ID or choose to exportpreferences for all users.
2. The default export scope is set to All, unless theincludeEntitiesFromApps parameter has been specified for a page orview, whereby it is then set to REQUIRED.
Rules and options for console properties and customization propertiesAll console properties and customization properties are exported.
Rules and options for transformationsAll transformations are exported.
Rules for importingWhen importing customized configuration data, it is important to know the rulesgoverning the import function and the options available to you.
The following rules apply when importing customized configuration data for aTivoli Integrated Portal environment:
Rules and options for pages
Rule
1. You can import all pages included in an exported package.2. You can exclude system customized pages that do not exist in the new
environment.3. You can exclude pages associated with a WAR that is not deployed in
the new environment and thereby avoid introducing empty pages.4. If a page contains multiple portlets and some of portlets are associated
with a WAR that is not deployed in the new environment, the page isnot imported.
Rules and options for views
1. All views included in an exported package are imported.2. Views that match the following conditions should not be imported as
the import operation for the view fails:v An empty view, that is, a view that contains no pages or roles.v A view that contains roles, but no pages.v A view that contains empty pages, that is, the page exists but it does
not contain portlets.
Troubleshooting fix pack installations 19
Rules and options for custom roles and role preferences (console preferenceprofiles)
All roles included in an exported package are imported.
Rules and options for user preferencesAll user preferences included in an exported package are imported.
Rules and options for console properties and customization propertiesAll console properties and customization properties included in anexported package are imported.
Rules and options for transformationsAll transformations included in an exported package are imported, if thehaSupport parameter is set to Both or False.
Table 1 provides details how various elements are processed during import:
Table 2. Rules for overwriting and merging during import
Element Action Comments
Pages Overwritten In relation to pages, roles aremerged, view membershipsremain unchanged, andpositions are modified.
Views Overwritten In relation to views, existingpage memberships aremerged with imported pages
Roles Skipped In relation to roles, user andgroup mappings are merged.
Console preference profiles Skipped
Credential data Merged
Property files Merged
Transformations Skipped
Charts Overwritten
20 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Importing specific pluginsWhen importing plugins to a Tivoli Integrated Portal environment, ensure that theplugins that you want to import are available, that is, the data was previouslyexported and that the correct products are installed in the target environment.
About this task
To import particular plugins to a Tivoli Integrated Portal environment, follow thesesteps:
Procedure1. Ensure that the products associated with the plugins that you intend to import
are installed in the target Tivoli Integrated Portal environment.2. To list which plugins are available for import, on the originating Tivoli
Integrated Portal environment, run the following command:v tip_home_dir\profiles\TIPProfile\bin\tipcli.bat
ListExportPlugins
v tip_home_dir/profiles/TIPProfile/bin/tipcli.shListExportPlugins
3. To import a subset of available plugins, on the target environment, run thefollowing command:v tip_home_dir\profiles\TIPProfile\bin\tipcli.bat Import
[--includePlugins plugin1,plugin2] --username tip_username --passwordtip_user_password
v tip_home_dir\profiles\TIPProfile\bin\tipcli.sh Import[--includePlugins plugin1,plugin2] --username tip_username --passwordtip_user_password
Results
The specified plugins are imported to the target Tivoli Integrated Portalenvironment.
Troubleshooting fix pack installations 21
22 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Notices
This information was developed for products and services offered in the U.S.A.
IBM® may not offer the products, services, or features discussed in this documentin other countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:
IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.
Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.
© Copyright IBM Corp. 2012 23
All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs.
TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.
Internet Explorer is a trademark of Microsoft Corporation in the United States,other countries, or both
24 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
Index
AAPARs 3
Ccharting
Internet Explorer 9 17
Ddisk space 12
Eexporting
rules 18, 19
Ffix pack installations
troubleshooting 11fix pack silent installation 6
Iimport
plugins 21install 8
errors 11remove by silent mode 9
installation64-bit 11deployment engine
failure after upgrade 14error code ADMR0104E 15failure after DE upgrade 14fix pack 5, 6silent 6Solaris 11Windows Server 2008 14
Internet Explorer 9bar or line chart 17
Llibstdc++ 15load balancing
Connection Manager data 16log files 12
Ooverview 1
PPTEs 3
Rresponse file parameters 8
Ssilent 8
Ttrace service
troubleshooting 16troubleshooting
fix pack installations 11installation errors 11trace service 16
UUI
missing tabs 18uninstall 9user ID
special character 17
© Copyright IBM Corp. 2012 25
26 Tivoli Integrated Portal 2.2.0.7 Installation and troubleshooting guide
����
Printed in USA