IDM Browser Client - documation.net.au · Configuring IDM Browser Client 20.1 6 Part 1: IDM Browser...

Version 20.1 rev 2

IDM Browser Client

Installation Instructions

Notices

PUBLISHERThis document is published anddistributed by Vignette Corporation. It wasdesigned and produced using FrameMakerpublishing software.

VERSIONIDM Browser Client InstallationInstructions, version 20.1 rev 2(Publication Date: 11 December 2006)

DISCLAIMERVignette does not warrant, guarantee, ormake representations concerning thecontents of this document. All informationis provided "AS-IS," without express orimplied warranties of any kind including,without limitation, the warranties ofmerchantability, fitness for a particularpurpose, quality and title.

Any information provided by Vignettecustomers or partners was obtained afterthe implementation of Vignette softwareand may have changed as of thePublication Date. You may not achieve thesame results or benefits from usingVignette as described in this document.Nothing in this document is considered tobe part of any product documentation orspecification for any purpose. Vignettereserves the right to change the contents

of this document and the features orfunctionalities of its products and servicesat any time without obligation to notifyanyone of such changes.

COPYRIGHT AND TRADEMARKS

Copyright © 2006 Vignette Corporation. Allrights reserved. Vignette, the V Logo,e:fficiency and e:fficiency experts aretrademarks or registered trademarks ofVignette Corporation in the United Statesand other countries. All other company,product, and service names and brandsare the trademarks or registeredtrademarks of their respective owners.

SEND US YOUR COMMENTS

If you have comments or suggestions aboutthis manual, please send them to thisaddress:

[email protected]

A member of the Publications team willacknowledge your mail as soon aspossible.

You can also reach us at the followingaddress:

Vignette CorporationPublications Department1301 South MoPac Expressway, Suite 100Austin, TX 78746USA

© 2006 Vignette Corporation. All rights reserved.2 v20.1 rev 2

Table of Contents

Chapter 1. Introduction 5Prerequisites 5

Release notes 5New installation 5Upgrade installation 5Configuring IDM Browser Client 20.1 6

Part 1: IDM Browser Client 20.1 for Unix

Chapter 2. Installing IDM Browser Client 20.1 (Unix) 9Installation summary 9Repository component installation 10

Initial setup 10GUI mode installation 11Console mode installation 12

Web server component installation 13Initial setup 13GUI mode installation 13Console mode installation 14

Configuring the web server 16To configure Apache/Tomcat 16To configure iPlanet 17To configure BEA WebLogic 17To configure IBM WebSphere 18

To set up an Application Server Toolkit project 18To create the .war file 20To install the new application 20

Chapter 3. Uninstalling IDM Browser Client 20.1 (Unix) 23Uninstalling summary 23Uninstalling IDM Browser Client 20.1 24

v20.1 rev 2 3IDM Browser Client Installation Instructions

Table of Contents

Initial setup 24GUI mode uninstall 24Console mode uninstall 25Manual file cleanup 26

Chapter 4. Troubleshooting on Unix 27Malformed \uxxxx encoding" error 27

Part 2: IDM Browser Client 20.1 for Windows

Chapter 5. Installing IDM Browser Client 20.1 (Windows) 31Installation summary 31Repository component installation 32

Initial setup 32Installing the repository component 32Post installation steps 33

Web server component installation 34Initial setup 34Installing the web server component 34

Support information 35Multiple instance installation workaround 35Multiple instance modification workaround 35

Chapter 6. Uninstalling IDM Browser Client 20.1 (Windows) 37Uninstalling summary 37

Uninstalling IDM Browser Client 20.1 37

Chapter 7. Repairing or modifying IDM Browser Client 20.1 (Windows) 39Repairing IDM Browser Client 20.1 39Modifying IDM Browser Client 20.1 components 41


Chapter

1
Introduction
There are two parts to complete a full installation of IDM Browser Client 20.1:

• IDM Browser Client—Repository component installed on the IDM Server.

• IDM Browser Client—Web Server component installed on the web server.

Prerequisites• All software must be patched to the supported level. For all supported versions of

third-party and Vignette software, including patches, please refer to the Supported Platform Matrix within the release notes. These can also be downloaded from the Vignette Global website http://global.vignette.com/. From the top menu, select Support > Release Notes.

• Your IDM Server must be version 20.1.

• You must have a working web server.

• On Unix systems, the web server must have Java Server Pages enabled. See the Supported Platforms Matrix for supported versions.

• The instance user installing IDM Browser Client must have write permission for all installation directories used including:

• any temporary installation directories

• the web server installation directory

• the installation directory for the repository component and

• on Unix systems, the JacORB home directory

Release notesThe release note for IDM Browser Client 20.1 contains further information on new features in the release and the detailed Supported Platforms Matrix as well as the background information on outstanding issues.

New installationEnsure all prerequisites are met before installing IDM Browser Client 20.1.

Upgrade installation• Upgrades from previous versions of IDM Browser Client are not supported. If a

previous version of IDM Browser Client is installed, this must be uninstalled before installing IDM Browser Client 20.1.


1Chapter

Configuring IDM Browser Client 20.1After you have installed IDM Browser Client, you can configure it in accordance with instructions to be found in either:

• Vignette IDM Browser Client for Windows Technical Reference or

• Vignette IDM Browser Client for Unix Technical Reference.

These manuals are available for download from the Vignette Global websitehttp://global.vignette.com/.


v20.1 rev 2

Part 1:

IDM Browser Client 20.1 for Unix

7IDM Browser Client Installation Instructions


1Part

Chapter

2
Installing IDM Browser Client 20.1 (Unix)
Installation summaryCheck Prerequisites on page 5 before proceeding with the installation of IDM Browser Client for Unix 20.1. Note in particular that you must have a functioning web server of the prescribed type.

In outline, the process for a new installation of IDM Browser Client for Unix 20.1 is:

1. Perform initial setup for the repository component of IDM Server.

2. Install the repository component using either the GUI or the console installer.

These steps are described in detail under Repository component installation on page 10.

3. Perform initial setup for the web server component of IDM Server.

4. Install the web server component using either the GUI or the console installer.

These steps are described in detail under Web server component installation on page 13.

5. Configure the web server.

This step is described in detail under Configuring the web server on page 16.

You may use the instructions in this chapter to install and configure individual components of your system.


2Chapter

Repository component installation• The IDM Browser Client for Unix 20.1 requires the C++ runtime libraries to be

installed. For AIX, the minimum version recommended is 8.0.

• Determine the working instance of IDM Server 20.1 on which IDM Browser Client for Unix 20.1 will be installed.

• Also take note of the instance user. This instance user is a user with administration rights that was used when installing IDM Server 20.1. This user will be referred to as the instance user throughout these instructions.

• Determine a directory that can be used as the installation temporary directory. This will be referred to as <temporary installation directory>.

This directory needs at least 120 MB.

The instance user must have write permission on this temporary directory.

Initial setup

The IDM Browser Client installation can be run in either GUI or console mode. Continue to either the GUI mode installation immediately below or Console mode installation on page 12.

Installation steps Information notes

1. Log in to the server as the instance user.

2. Shut down the IDM Server 20.1 instance on which IDM Browser Client is to be installed by executing the following command:

$CTL_RUNTIME_DIR/is/admin/stopsys.sh

3. Confirm that all instance user processes have stopped.

4. Save the installation file to a local directory. Unix installation files will be:

setupAIX_IBCU.binsetupHP_IBCU.binsetupHPIA64_IBCU.binsetupSolaris_IBCU.bin.

These will be referred to as:

setup<platform>_IBCU.bin

5. Change permissions on the installer *.bin file to allow root to have execute permission (755 or 777)



GUI mode installation• When using the GUI mode installation, you must log in directly - you cannot ‘su’ or the

installation will terminate.

• To setup the X-terminal display, execute the following command (where <IP_address> is the IP address of the PC you are running the install from):

export DISPLAY=<IP_address>:0.0

• Use the following command to start the GUI installer:

sh ./setup<platform>_IBCU.bin

If necessary, add the option -is:tempdir <temporary installation directory>:

• Configure the repository as necessary by referring to the IDM Browser Client for Unix Technical Reference.

• If you installed the web server component, log out and log back in.

This is required so that the changes made to environment variable in the user’s profile take effect.

• If you installed the web server component, configure the web server as necessary. Refer to Configuring the web server on page 16 and to the IDM Browser Client for Unix Technical Reference.


1. Welcome screen:

Click Next to continue to the license agreement.

2. Accept the license agreement.

Click Next.

To continue with the installation, the license agreement is required to be accepted..

3. Select the Vignette IDM Browser Client for Unix - Repository component.

If the web server component is to be installed on the same machine as the repository component, select to install both components together.

Click Next.

4. This step only applies if you selected Web Server Component in step 3.

Web server component

Accept the web server component installation location or input a new location then continue.

For WebSphere only: the directory path should be a temporary directory that is visible to the WebSphere Application Server Toolkit.

5. This step only applies if you selected web server component in step 3.

JacORB installation directory

Accept the JacORB installation location or input a new location then continue.


6. Review the summary information.

Click Install.

If a message is displayed: “Component previously installed”, select to overwrite the component and continue to install.

7. Installation completion.

Verify that no errors occurred by looking at the log file.

Click Finish.

The log file is in the IBCU installation location and is called IDMBrowserClient-Installer.log.


2Chapter

Console mode installationUse the following command to start the console installer:

sh ./setup<platform>_IBCU.bin -console

If necessary, add the option -is:tempdir <temporary installation directory>.

• Configure the repository as necessary by referring to the IDM Browser Client for Unix Technical Reference.

• If you installed the web server component, log out and log back in.


• If you installed the web server component, configure the web server as necessary. Refer to Configuring the web server on page 16 and to the IDM Browser Client for Unix Technical Reference.


1. At the Welcome, continue to the next screen.

2. Accept the license agreement and continue. To continue with the installation, the license agreement is required to be accepted.

3. Select to install the repository server component and continue.

If the web server component is to be installed on the same machine as the repository component, select to install both components together.

Read the Web server component installation on page 13 before installing the web server component.

4. Repository Server component

Accept the repository server component installation location or input a new location and then continue.


Web server component




JacORB installation directory

Accept the JacORB installation location or input a new location and then continue.

See Web server component installation on page 13 for more information.


7. Review the summary information and continue to install.


8. Installation complete:


Enter 3 to complete and exit the installation.




Web server component installation

NOTE: If you have installed the web server component at the same time as the repositorycomponent, continue to Configuring the web server on page 16.

• Ensure that your web server has Java Server Pages enabled. See the Supported Platforms Matrix for supported versions.

• Ensure that your web server has JRE installed. Check whether your web server installs its own JRE and if not, refer to the Supported Platforms Matrix to determine which version to install. Versions of the JRE for Windows, Solaris, and Linux can be found at Sun’s Java website, http://java.sun.com. Install the JRE in its default location.

Initial setupThe installation file (which is platform specific) must be copied to a local temporary installation directory as outlined below.

The IDM Browser Client for Unix installation can be run in either GUI or console mode. Proceed to either GUI mode installation immediately below or Console mode installation on page 14.

GUI mode installation• Execute the following command to set up the X-terminal display:


Where <IP_address> is the IP address of the PC you are running the install from.

• Execute <temporary installation directory>/setup<platform>_IBCU.bin to start the GUI installer.


1. Determine a directory that can be used as the installation temporary directory. This will be referred to as <temporary installation directory>.

This directory needs at least 120 MB.

2. Change directory to the location of the IDM Browser Client for Unix installer.

3. Copy the installation file setup<platform>_IBCU.bin to <temporary installation directory>.


1. Welcome screen:

Click Next to continue to the license agreement.


Click Next.

To continue with the installation, the license agreement is required to be accepted.

3. Choose to install web server component.

Click Next.


http://java.sun.com

2Chapter

• Log out and log back in.

This is required so that the changes made to environment variables in the user’s profile take effect.

• Configure the web server as necessary by referring to Configuring the web server on page 16 and to the IDM Browser Client for Unix Technical Reference.

Console mode installationUse the following command in <temporary installation directory> to start the console installer:

sh ./setup<platform>_IBCU.bin -console

4. Web server component:

Accept the web server component installation location or input a new location and then continue.

For WebSphere only: the directory path should be a WebSphere temporary directory that is visible to the WebSphere Application Server Toolkit.

5. JacORB installation directory:

Accept the JacORB installation location or input a new location and then continue.

Select Next.



Click Install.

Ensure the installation location is correct.

Click the Back button to return to any previous installer screens.

7. If a message is displayed: “Component previously installed”, select to overwrite the component and continue to install.

This may occur when an IDM product has been installed then uninstalled.

8. Installation completion.


Click Finish.


9. You will see a screen reminding you to log out and then back in again.

Click Finish.


1. At the Welcome, continue to the next screen.

2. Accept the license agreement and continue. To continue with the installation, the license agreement is required to be accepted.

3. Select to install the web server component and continue.

4. Web server component:



5. JacORB installation directory:

Accept the JacORB installation location or input a new location then continue.





• Log out and log back in.


• Configure the web server as necessary by referring to Configuring the web server on page 16 and to the IDM Browser Client for Unix Technical Reference.

6. Review the summary information and continue to install.


7. Installation complete:


Enter 3 to complete and exit the installation.




2Chapter

Configuring the web serverThis section describes all post-installation instructions for specific versions of supported web servers for IBCU 20.1.

• Apache/Tomcat version 5.5.12

• iPlanet version 6.1 service pack 5

• BEA WebLogic versions 8.1.5 and 9.0

• IBM WebSphere version 6.0.2

For background information about configuring the web server component for IDM Browser Client for Unix, see the IDM Browser Client for Unix Technical Reference and refer to the section Configuring IBCU web server component.

To configure Apache/Tomcat

These instructions are specific to Apache/Tomcat version 5.5.12.

1. Ensure that the Apache/Tomcat web server is stopped.

2. Open for editing the file catalina.sh in the directory $CATALINA_HOME/bin. ($CATALINA_HOME is the directory where Apache/Tomcat files are installed.)

3. Add the following lines after the comments at the top of the file:

# Add JacORB jars to classpath for IDM Brower ClientJAVA_OPTS="-Xbootclasspath/p:${JACORB_HOME}:${JACORB_HOME}/lib/jacorb.jar\

:${JAVA_HOME}/jre/lib/rt.jar:${CLASSPATH} \-Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB \-Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton \$JAVA_OPTS"

4. Save and close catalina.sh.

5. Add the following directories to the CLASSPATH in the web server user profile file:

• $TDP_WS_HOME/tower/WEB-INF/lib/ttuwsstubs_tao.jar

• $TDP_WS_HOME/tower/WEB-INF/lib/ttuwsjavabeans_tao.jar

• $TDP_WS_HOME/tower/WEB-INF/lib/vidm_corbastubs_tao.jar

• $TDP_WS_HOME/tower/WEB-INF/lib/servlet.jar

• $JACORB_HOME

• $JACORB_HOME/lib/jacorb.jar

• $JACORB_HOME/lib/concurrent-1.3.2.jar

• $JACORB_HOME/lib/logkit-1.2.jar

• $JACORB_HOME/lib/antlr-2.7.2.jar

• $JACORB_HOME/lib/avalon-framework-4.1.5.jar

• $JACORB_HOME/lib/wrapper-3.1.0.jar



• $JAVA_HOME/lib/tools.jar

NOTE: An alternative option to the step above is as follows:

If your web server supports a common location for all the extra .jar files which then wouldbe automatically added to the web server classpath, you may copy all the files from$JACORB_HOME/lib to that location.For example, if you are using Tomcat, copying all files from $JACORB_HOME/lib to$CATALINA_HOME/common/endorsed, you will not need to add these files to theclasspath.

If the file servlet.jar exists in both $CATALINA_HOME/common/lib and $CATALINA_HOME/webapps/tower/WEB-INF/lib then remove the one from $CATALINA_HOME/webapps/tower/WEB-INF/lib.

Note that Some Tomcat versions may or may not include servelet.jar in location$CATALINA_HOME/common/lib. Check this in your Tomcat version.

6. Perform the tasks listed under Common configuration within the IDM Browser Client for Unix Technical Reference.

To configure iPlanetThese instructions are specific to iPlanet version 6.1 sp5.

In outline, in this procedure you install the web server component and package it into a .war file. Next you deploy the .war file. That instance of the web server component has then served its purpose and may be deleted.

1. Using the instructions in Web server component installation on page 13, install the web server component of IDM Browser Client for Unix into a temporary directory, say $TDP_TMP.


3. Copy all the .jar files under $JACORB_HOME/lib to $TDP_TMP/tower/WEB_INF/lib.

4. Create a .war file which includes everything under the tower directory. To achieve this, perform:

cd $TDP_TMP/towerjar -cvf <file name>.war *

5. Deploy IBCU as a web application using the iPlanet administration client.

6. When the deployment is successful, delete the directory containing the temporary IBCU installation. In our example, this is $TDP_TMP.

To configure BEA WebLogicThese instructions are specific to BEA WebLogic versions 8.1.5 and 9.0.

BEA recommends that you consult the BEA web site for information on OS tuning:

http://e-docs.bea.com/wls/docs81/perform/WLSTuning.html

http://e-docs.bea.com/platform/suppconfigs/index.html

1. Ensure that the WebLogic server is stopped. To stop it, use the script stopWebLogic.sh.

For version BEA WebLogic version 8.1.5, stopWebLogic.sh is located in $WL_HOME/user_projects/domain/<domain_name>, where $WL_HOME is the WebLogic location and


2Chapter

<domain_name> is the name of the WebLogic web server on which IBCU was installed. For version 9.0, it is located in $WL_HOME/user_projects/domain/<domain_name>/bin.

2. Open for editing the file startWebLogic.sh in the directory $WL_HOME/user_projects/domains/<domain_name> for WebLogic 8.1.5 or $WL_HOME/user_projects/domains/<domain_name>/bin for WebLogic 9.0.

3. Ensure that the following .jar files are included in the CLASSPATH

• $JACORB_HOME/lib/antlr-2.7.2.jar

• $JACORB_HOME/lib/avalon-framework-4.1.5.jar

• $JACORB_HOME/lib/concurrent-1.3.2.jar

• $JACORB_HOME/lib/jacorb.jar

• $JACORB_HOME/lib/logkit-1.2.jar

• $JACORB_HOME/lib/wrapper-3.1.0.jar

• $TDP_WS_HOME/tower/WEB-INF/lib/servlet.jar

• $TDP_WS_HOME/tower/WEB-INF/lib/ttuwsjavabeans_tao.jar

• $TDP_WS_HOME/tower/WEB-INF/lib/ttuwsstubs_tao.jar

• $TDP_WS_HOME/tower/WEB-INF/lib/vidm_corbastubs_tao.jar

Where $JACORB_HOME is the directory where JacORB files are installed and $TDP_WS_HOME is where IBCU web server component is installed.

4. Save and close startWebLogic.sh.

5. For BEA WebLogic version 9.0 only, edit the file web.xml in the directory $TDP_WS_HOME/tower/WEB-INF.

Either delete the <description> tags within <context-param> or ensure that the <description> tags are placed prior to <param-name> and <param-value> tags.

Save and close web.xml.

6. Start the WebLogic server using the script startWeblogic.sh.

7. From a browser, log in to the BEA Admin server (normally http://<hostname>:<admin port>/console). For example,

http://vgnidm:7001/console

where 7001 is the default administration port.

8. Deploy the tower directory (under the directory where IBCU web server component was installed) as a web application. See the BEA product documentation for details on how to deploy a web application.


To configure IBM WebSphereFollowing are the steps required to package and deploy the IDM Browser Client for Unix on WebSphere 6.0.0.1 using the WebSphere Application Server Toolkit version V6.0.0 for Windows. Note that some of the operations in the Unix deployment are carried out on a Windows machine.

The material below shows one method for doing this.

In outline, in this procedure you install IBCU and package it into a .war file with the WebSphere Application Server Toolkit. That IBCU has then served its purpose and may be deleted. Next you deploy the .war file from the WebSphere administration console.

To set up an Application Server Toolkit project



1. Using the instructions in Web server component installation on page 13, install the web server component of IDM Browser Client for Unix into a temporary directory.

2. Navigate to the temporary installation directory and tar the installed files.

3. Transfer the .tar file to your Windows machine and untar these files in a location which is visible to the WebSphere Application Server Toolkit.

4. Navigate to the folder ...\tower\WEB-INF\.

5. Copy the file web.xml to a safe location.

This file will be needed as a replacement file when you have finished the deployment.

6. Launch the WebSphere Application Server Toolkit.

By default, this is located in c:\Program Files\IBM\AST and is called ast.exe.

(Formerly the directory and drive were called ASTK and astk.exe.)


1. In the Application Server Toolkit window, open the J2EE perspective to work with J2EE projects. To do this, select Window > Open Perspective > Other. Then from the Select Perspective window, select J2EE.

2. Set up a new project: click File > New > Dynamic Web Project.

3. Enter a project name.

Click Finish.

For example, IBCU20_1_0.


2Chapter

To create the .war file

To install the new application1. Via Internet Explorer, open the WebSphere administration console. Expand

Applications and clickInstall New Application.

1. In the left menu, right-click the WebContent folder of the newly created project and select Import.

The Import window opens.

2. Select File System > Next..

3. Navigate to the directory where the IBCU was expanded, select the tower subdirectory, check Select All.

4. In the Options panel, ensure that the Create selected folders only option is selected.

Click Finish.

The Create Selected Folders Only option is the default.

5. Right click on your project and select Export > WAR file. Select a name and location for the .war file and ensure the following check boxes remain unchecked

- Export source files

- Overwrite existing files without warning

6. Click Finish.

You will be asked whether to overwrite the existing web.xml file.

Answer No.

Experience shows that the toolkit can overwrite web.xml regardless of the setting. This is the reason for saving web.xml in step 4 above.

The toolkit now creates the .war file on your Windows machine. It must now be deployed on the Unix machine which runs IBCU.

7. You may now delete temporary directory containing the web server component of IDM Browser Client for Unix.



2. Browse to the newly created .war file.

3. Specify a context root for the installation and click Next.

The context root will be the virtual root as seen from the client.

There may be a delay of a few minutes, even after the progress bar completes.

4. On the Choose to generate default bindings and mappings screen, accept the default settings, which are that Generate Default Bindings is unchecked, Do not override existing bindings is selected.

Click Next.

5. You may see an Application Security Warnings screen.

Click Continue.

6. On the Specify options for installing enterprise applications and modules—Step 1: Select installation options screen, accept the default installation options and click Next.

7. On the Specify options for installing enterprise applications and modules—Step 2: Map modules to servers screen, you may accept the default settings if you are deploying to a single server.

If you are deploying to multiple servers, select the mapping to be used for this installation (and you will have to repeat the installation for each server.)

Click Next.

8. On the Specify options for installing enterprise applications and modules—Step 3: Map virtual hosts for Web modules screen, you may again accept the default settings if you are deploying to a single server.

If you are deploying to multiple servers, expand Apply Multiple Mappings and select the mapping to be used for this installation (and you will have to repeat the installation for each server.)

Click Next.

9. On the Specify options for installing enterprise applications and modules—Step 4: Summary screen, review the settings.

10. If you are not satisfied, click Previous and change the settings.

Applications menu

Install New Applications link


2Chapter

If you are satisfied, click Finish.

Observe the on-screen warning “the EJB deployment process can take several minutes. Please do not save the configuration until the process completes.”

11. Click Save to Master Configuration to save the changes to the server configuration.

12. On the WebSphere administration console, expand Environment. and click Shared Libraries. On the Shared Libraries screen, add jacorb.jar and all .jar files related to JacORB.

13. Still on the WebSphere administration console, go to Applications > Enterprise Applications and select the new application.

The Enterprise Applications screen will display the General Properties and the Additional Properties panels.

14. Add jacorb.jar and its associated .jar files to the application libraries. To do this, click on the Libraries link in the Additional Properties panel. This will give you a screen with a drop-down, allowing you to select jacorb.jar and the associated .jar files.

15. Go to the General properties panel (on the same screen as the Additional Properties panel) and check Use Metadata From Binaries. Leave all other settings unchanged.

16. Click the Save link in the Messages box (you may need to expand it first).

17. Click the Save button.

18. Replace the web.xml file located in

C:\<installation_directory>\WebSphere\AppServer\installedApps\<machine_name>\towerEAR.ear\tower.war\WEB-INF\web.xml

with the web.xml file copied in step 4 of To set up an Application Server Toolkit project on page 19, and restart the application.

19. You may delete the new project you set up in the procedure To set up an Application Server Toolkit project on page 18.


Chapter

3
Uninstalling IDM Browser Client 20.1 (Unix)
Uninstalling summaryThere are two steps to complete in order to uninstall IDM Browser Client 20.1 on Unix, as outlined below:

1. Uninstall, using either GUI or console mode.

2. Manual file cleanup.


3Chapter

Uninstalling IDM Browser Client 20.1The following instructions are only for those users of HP-UX and for WebSphere users. If you are not using either of these, continue to the Initial setup.

For HP-UX only:

To successfully uninstall IDM Browser Client 20.1on HP-UX:

• Java (or at a minimum, JRE) must be installed.

• Code from a Java .jar file is required so the java command must be on the user’s path.

• $JAVA_HOME must point to the location of the installed JRE.

For WebSphere only:

The web server component must also be removed from the WebSphere administration console.

Initial setup

The IDM Browser Client installation can be run in either GUI or console mode. Proceed to either GUI mode uninstall immediately below or Console mode uninstall on page 25.

GUI mode uninstall• Change directory to the IBCU uninstall directory <IBCU install location>/_uninst_IBCU.

(IBCU was installed in the directory <IBCU install location>).

• Launch the uninstaller.

For AIX or Sun

Execute uninstaller.bin.

For HP-UX

Run the command

$JAVA_HOME/bin/java -jar <IBCU install location>/_uninst_IBCU/uninstall.jar

Uninstallation steps Information notes

1. Log in to the server as the instance user who installed IDM Browser Client.

2. If the repository component is to be uninstalled, shut down its corresponding IDM Server 20.1 instance. To do this, run $CTL_RUNTIME_DIR/is/admin/stopsys.sh.

3. If the web server component is to be uninstalled, shut down the web or application server.

4. Execute the following command to set up the X-terminal display:


The <IP_address> is the IP address of the PC you are running the installation from.


1. Welcome screen:

Click Next to continue.


Uninstalling IDM Browser Client 20.1 (Unix)

Proceed to Manual file cleanup on page 26.

Console mode uninstall• Navigate to the IBCU uninstall directory <IBCU install location>/_uninst_IBCU. (IBCU was

installed in the directory <IBCU install location>).

• Launch the uninstaller.

For AIX or Sun

Execute this command:

./uninstaller.bin -console

For HP-UX

Execute this command:

$JAVA_HOME/bin/java -jar <IBCU install location>/_uninst_IBCU/uninstall.jar -console

Proceed to Manual file cleanup immediately below.

2. You will be offered check boxes for the components (repository and/or web server) that are present on this machine.

Check the component or components you wish to uninstall.

Click the Next button.


Click Uninstall.

If you need to make a change to any of the input, click the Back button to return to the necessary installer screen.

The wizard displays a progress screen during the uninstallation.

4. Uninstallation Completion.

Click Finish.

This completes the installation and exits the installation wizard.


1. At the Welcome, choose Next to continue to the next screen.

That is, enter 1.

2. You will be asked to confirm which of the repository and web server components you wish to uninstall.

If you are satisfied to uninstall the component or components identified, enter 0.

If not, choose the option set out on the screen for the component you wish to omit.

Usually, if both compnents are installed, the uninstaller will present these options:

1. [x] Repository Server Component2. [x] Web Server Component


Enter 1 to continue.

4. The wizard displays a progress screen during the uninstallation.

5. When the uninstallation is complete, enter 3 to complete and exit the uninstaller.



3Chapter

Manual file cleanupFiles that were not created by the installer cannot be removed by the uninstaller. Some manual cleanup of these files may be required.

1. Remove directories and files using the following commands if they exist in the <IBCU install location>:

rm IDMBrowserClient-Installer.logrm –rf _uninst_IBCU

2. If the web server component was uninstalled, navigate to the directory containing the IBCU installation location and remove the ‘tower’ directory using this command:

rm –rf tower

3. If the repository component was uninstalled, go to the directory containing the IBCU installation location and remove the following lines from the file/etc/tower/profile.custom.<instance user>:

• NAMING_SERVICE_PORT=14888

• export NAMING_SERVICE_PORT

4. If the repository component was uninstalled, remove the orb directory (and all its contents) from $CTL_RUNTIME_DIR/is.

5. If applicable, for the web server component pointing to this repository, un-deploy the demo client. The procedure for doing this will depend on which web server is being used. For example, if your web server is Tomcat, remove ws_demo_client_api_test.war from its webapps directory.


Chapter

4
Troubleshooting on Unix
Malformed \uxxxx encoding" error

Install, com.installshield.product.service.product.PureJavaProductServiceImpl$Installer, err, ServiceException: (error code = 315; message = "A file name cannot contain any of the following characters: `'"^()\|{}[]<> "; severity = 0)

…

This error: “Malformed \uxxxx encoding" error during install/launch” can occur when the PS1 shell variable is customized to control the information displayed at a Unix command prompt. It will not occur with the default shell variable setting.

Should this error occur just before the installation of the files, this variable should be reset then the installer re-run. (You may also notice just before the error occurs, the default path will be incorrect.)

To reset this variable, execute the following before running the installer: PS1=”$ “


4Chapter


v20.1 rev 2

Part 2:

IDM Browser Client 20.1 for Windows

29IDM Browser Client Installation Instructions


2Part

Chapter

5
Installing IDM Browser Client 20.1 (Windows)
Installation summaryCheck Prerequisites on page 5 before proceeding with the installation of IDM Browser Client for Windows 20.1.

In outline, the process for a new installation of IDM Browser Client for Windows 20.1 is:

1. IDM Browser Client for Windows—repository component

• Initial installation setup.

• New installation—repository component.

This installs all files that are owned and accessed by the instance user.

• Post installation configuration.

2. IDM Browser Client for Windows—web server component

• New installation—web server component.

This installs all files that are owned and accessed by the instance user.


5Chapter

Repository component installation• If you are installing a second or subsequent instance of the Vignette IDM Browser

Client for Windows repository component, refer to Multiple instance installation workaround on page 35 before installing.

• Determine the working instance of IDM Server 20.1 on which IDM Brower Client 20.1 will be installed.

• Take note of the instance user. The instance user is a user with Administration rights that was used when installing IDM Server 20.1. This user will be referred to as the instance user throughout these instructions.

• Ensure that IIS and .NET Runtime are installed.

Initial setup

Installing the repository componentNavigate to the temporary installation directoryand launch Setup.exe to start the installation.


1. Log in to the server as the instance user.

2. Shut down the IDM Server 20.1 instance on which IDM Browser Client 20.1 is to be installed:

Stop the service Vignette IDM(<instance user>).

3. Confirm that all instance user processes have stopped.

4. Determine a directory that can be used as the instance user installation’s temporary directory.

This will be referred to as <temporary installation directory>.

This directory needs at least double the size of the installation file.

The instance user must have write permission on this temporary directory

5. Change directory to the location of the IDM IDM Browser Client 20.1 installer.

6. Copy the installation files to <temporary installation directory>.


1. Welcome screen:

Click Next.

2. Accept the license agreement. To continue with the installation, the license agreement is required to be accepted.

3. Ensure the repository server component is selected by clicking the check box next to the component description.

Click Next.



Post installation steps1. If multiple instances of the IDM Browser Client for Windows repository component

are to be installed or are already installed, remember to refer to Multiple instance installation workaround on page 35.

2. Start the Vignette IDM (<instance user>) Service.

NOTE: Refer to the Vignette IDM Browser Client for Windows Technical Reference 20.1 forinformation on configuring the repository component.

4. If the web server is to be installed on the same box as the repository server:

Select the web server component as well. The two components will be installed together.

Click Next.

If both components are checked, the next screen will ask you to input or confirm the the installation path for web server.

SeeWeb server component installation on page 34 for more information.


Click Next.

If you need to make a change to any of the input, select the Back button to return to the necessary installer screen.

6. Installation Completion.

Select Yes to restart the computer.

Click Finish.

Select Finish to complete the installation and exit the installation.



5Chapter

Web server component installationInitial setup

• Ensure that IIS and .NET Runtime are installed.

• Take note of the instance user. The instance user is a user with Administration rights that was used when installing IDM Server 20.1. This user will be referred to as the instance user throughout these instructions.

Installing the web server componentGo to the temporary installation directory and launch Setup.exe to start the installation.


1. Welcome screen:

Click Next.


Click Next.

To continue with the installation, the license agreement is required to be accepted.

3. Ensure the web server component is selected by clicking the check box next to the component description.

Click Next.

If the web server and repository components are to be installed on the same box, both components can be selected during the repository component installation.

4. Accept the default installation location or select Browse to navigate to the installation location.

Click Next.


Click Next.

If you need to make a change to any of the input, click the Back button to return to the necessary installer screen.

6. Installation Completion.

Click Yes to restart the computer.

Click Finish.

Select Finish to complete the installation and exit the installation.



Support information

Multiple instance installation workaroundThis describes how to install Vignette IDM Browser Client for Windows repository component into multiple instances of the IDM Server, all running on the same server.

Notice that this procedure ‘wraps around’ the installation procedure. You must read this procedure and plan your installation in conjunction with the installation procedure.

1. Install IDM Browser Client for Windows repository component into a default instance of IDM Server using these installation instructions. Before installing to a second or subsequent instance, ensure that the following steps are completed.

2. After the first installation of Vignette IDM Browser Client for Windows repository component only, obtain the Installshield registry key by selecting Start > Run and launching regedit.

• Expand the tree and find HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ 35A49B08-CBF0-4452-A5E8-8E3AA5B38071}.

• Highlight the key.

• On the toolbar, choose File > Export and export the file as IBCW.reg to the temp directory. This file will be required to run uninstallations of the IDM Browser Client for Windows repository component.

• Close the registry editor.

3. Open Windows Explorer.

4. Navigate to the directory C:\Program Files\InstallShield Installation Information\{35A49B08-CBF0-4452-A5E8-8E3AA5B38071}.

5. This directory may be hidden. If so, unhide it.

6. Rename this directory, adding the instance number just installed. For example, {35A49B08-CBF0-4452-A5E8-8E3AA5B38071}_instance1.

You may now install the IDM Browser Client for Windows repository component into a second instance, as follows.

7. Log in as the instance user and install the Vignette IDM Browser Client for Windows repository component following the ordinary installation instructions.

You have now installed another instance.

8. Using Windows Explorer, navigate to the directory C:\Program Files\InstallShield Installation Information\{35A49B08-CBF0-4452-A5E8-8E3AA5B38071}.

9. Rename this directory, adding the instance number just installed. For example, {35A49B08-CBF0-4452-A5E8-8E3AA5B38071}_instance2.

10. Repeat step 7 onwards if more than two installations of the IDM Browser Client for Windows repository component are to be installed in more instances.

Multiple instance modification workaroundThis describes how to uninstall, reinstall or modify components of IDM Browser Client for Windows repository component on multiple instances of IDM Server on the same server.

Notice that this procedure ‘wraps around’ the uninstallation, modification or reinstallation procedure. You must read this procedure and plan your installation in conjunction with those procedures.


5Chapter

1. Log in as the instance user into the instance that the IDM Browser Client for Windows repository component will be uninstalled, modified or reinstalled.

2. Navigate to the directory C:\Program Files\InstallShield Installation Information.

3. Rename the directory {35A49B08-CBF0-4452-A5E8-8E3AA5B38071}_instance<number> to {35A49B08-CBF0-4452-A5E8-8E3AA5B38071} where instance<number> is the instance of the IDM Browser Client for Windows repository component to be uninstalled, modified or reinstalled.

4. Launch regedit.

5. Choose File > Import and import the registry key exported into the temp directory as file IBCW.reg when you performed step 2 of Multiple instance modification workaround on page 35.

6. Perform the desired uninstallation, modification or repair.

7. If you have just performed a modification or reinstall (but not an uninstall) you must now change the directory name back to the way it was. Log in again as the instance user.

8. Navigate to C:\Program Files\InstallShield Installation Information.

9. Rename the directory {35A49B08-CBF0-4452-A5E8-8E3AA5B38071} to {35A49B08-CBF0-4452-A5E8-8E3AA5B38071}_instance<number> where again, instance<number> is the instance of the IDM Browser Client for Windows repository component that you modified or reinstalled.


Chapter

6
Uninstalling IDM Browser Client 20.1 (Windows)
Uninstalling summaryThere are two steps to complete in order to uninstall IDM Browser Client 20.1 on Windows, as outlined below:

1. Uninstall.

2. Additional clean-up for web server component.

NOTE: If you are uninstalling one of many instances of the IDM Browser Client forWindows repository component, refer to Multiple instance modification workaround onpage 35.

Uninstalling IDM Browser Client 20.1• Log in as the installation instance user who installed IDM Browser Client 20.1 and

shut down the IDM Server instance.

• Go to the directory containing the IDM Browser Client installation file Setup.exe and double-click to launch it.


1. Select Remove.

Select Next.

2. Select OK to the Confirm Uninstall message.

The uninstallation of the IDM Browser Client 20.1 will now commence.

If the Shared File Detection window appears, check the Don’t display this message again checkbox and click Yes.

3. Select Finish in the Installation Complete screen to complete and exit the uninstallation.


6Chapter


Chapter

7
Repairing or modifying IDM Browser Client 20.1 (Windows)
Repairing IDM Browser Client 20.1Repairing an installation of IDM Browser Client 20.1 may be required when other IDM products that have shared file directories, are installed.

There are two ways to do this. You can repair IDM Browser Client 20.1:

• using the installer, or

• use the Add/Remove Programs utility from the Windows control panel.

NOTE: Components modified since the original install will not be reinstalled.

To repair IDM Browser Client 20.1 using the installer

If multiple instances of Vignette IDM Browser Client for Windows repository component have been installed, refer to Multiple instance modification workaround on page 35 before reinstalling.

• Log in as the instance user who installed IDM Browser Client.

• If you are reinstalling the repository component, shut down the IDM Server instance.


Once restarted, log back in as the installation instance user.


1. Select Repair.

Select Next.

2. Review the Perform Maintenance Operations details.

Select Next.

If any settings are incorrect, select the Back button to navigate back to the incorrect setting and change accordingly.

3. The reinstallation of the Vignette IDM Browser Client for Windows will now commence.

If the Shared File Detected or Locked File Detected window appears, check the Don’t display this message again checkbox and click Yes or Reboot.

4. Select Yes and the Finish button to reboot the machine.


7Chapter

The reinstallation of IDM Browser Client is now complete.

NOTE: If this was a repair on one of many instances of the IDM Browser Client repositorycomponent, refer to Multiple instance modification workaround on page 35.

To repair IDM Browser Client using the control panel

1. From the control panel, select Add or Remove Programs.

2. Select IDM Browser Client.

3. Click the Change button.


Repairing or modifying IDM Browser Client 20.1

Modifying IDM Browser Client 20.1 components

This section details how to modify a selected component, or install an additional component for IDM Browser Client 20.1.

If multiple instances of IDM Browser Client repository component have been installed, refer to the Multiple instance modification workaround on page 35 before modifying components.

• Log in as the installation user who installed IDM Browser Client.

• If you are modifying the repository component, shut down the IDM Server instance.


Once the system has restarted, log back in as the installation instance user.


1. Select Modify.

Click Next.

2. Select components to be installed by clicking the box next to each component description.

Click Next.

Any new components that have a checked box will be installed.

Any previously installed components that have a checked box will be reinstalled.

Any previously installed components that have an unchecked box will be uninstalled.

Any components modified since the original install will not be reinstalled.

3. If the IDM Browser Client web server component was previously selected for installation and not already installed, the Destination Folder for this component is required.

Accept the default installation location or select Browse to navigate to the installation location.

Click Next.

4. Review the Performing Maintenance Operations details.

Click Next.

If any settings are incorrect, select the Back button to navigate back to the incorrect setting and change accordingly.

5. The installation of additional IDM Browser Client components will now commence.

If the Shared File Detected or Locked File Detected window appears, check the Don’t display this message again checkbox and click Yes or Reboot.

6. Select Yes and the Finish button to reboot the machine.


7Chapter

The installation of additional IDM Browser Client components is now complete.

NOTE: If this was a modification of one of many instances of the Vignette IDM BrowserClient for Windows repository component, return to Multiple instance modificationworkaround on page 35.


Date post:	03-Apr-2018
Category:	Documents
Upload:	lamliem
View:	241 times
Download:	2 times

IDM Browser Client - documation.net.au · Configuring IDM Browser Client 20.1 6 Part 1: IDM Browser...

Documents