Installing websphere portal express

I am trying to install websphere portal express 6.1 on my Windows XP machine. I am using the following download link:

https://www14.software.ibm.com/webapp/iwm/web/reg/download.do?source=ESD-PORTALEXPRESS&S_PKG=CR557ML&S_TACT=105AGX10&S_CMP=LP&lang=en_US&cp=UTF-8

Note that you will need to have an IBM user ID to see the links, but registration is free, and I suspect many of you already have one.

I have uploaded every file on the page linked above. The Websphere portal consists of several parts including Websphere Application Server, the portal itself, db2 express edition. The installation never goes beyond installing the W-2 drive where it installs db2 express. The installation fails with a popup that simply says the installation failed, check the log file. I did. The log file states that the db2 express installation was successful but requires a restart. The installer cannot do this. I am now running the installation as a user who is an administrator on the local machine, but also belongs to the work domain that I am connected to. The installation warns that there might be problems with this during installation, but that never says anything specific and I have yet to find a detailed error aboutwhy the installation failed.

I have verified that the portal user ID has a password that adheres to our domain rules.

It can also be noted that I have a full version of db2 already installed on my machine, but the installation does not allow it to search for this, and it does not allow me to disable any installation components. I suppose I think it might be the case because the installation process creates db2user under the Windows account. Since I already have the full version installed, this user already exists.

If anyone has any thoughts on why this installation might fail, I would love to hear about it. Thank!

  • Jason
0


source to share


2 answers


Found a solution:

Found the solution here: http://www.codeverge.net/item.aspx?item=65569

The specific solution came between the following post:

If you've installed / uninstalled multiple times, it might be helpful to clean things up before installing again. Please do the following: 1) uninstall DB2 Express using Control Panel → Add / Remove Programs 2) uninstall the portal and WAS using \ PortalServer \ uninstall \ uninstall.bat 3) after uninstalling the portal i) delete all files in the installation directory ( Portal) ii) delete files in Documents and Settings \ Administrator \ Local Settings \ Temp iii) delete files in Documents and Settings \ Administrator that start with "dot" iv) delete vpd.properties file in C: \ Windows v) delete folder and WPDB2INS files are included in it; should be C: \ WPDB2INS vi) Using User Manager, remove the DB2INS user that was created by the installation. 4) Restart your computer. Try a fresh install after that. Make surethat your cell names / node / host only include alphanumeric characters (the default cell name / node is your computer's name, and if it includes the characters "-", "" or other non-alphanumeric characters, it might Also, make sure the account that installs Portal Express has administrator rights on the installation machine. Hope this helps. --travis



and the changes I made to the trail files in the install directory. I modified the installresponse.txt file and put the passwords in the following sections:

  • USER USERS AND WEBSPHERE USER PASSWORD
  • ADMINISTRATIVE USER AND WEBSPHERE USER PASSWORD
  • DB2 USER AND PASSWORD (UNIBERS)

I think the problem I was facing was the password for the accounts created on my Windows XP machine were assigned passwords that did not meet our minimum requirements.

I cannot say for sure which one he fixed; however, I followed the steps presented in this post and then modified the above file and the installation works fine (albeit slowly).

+1


source


It also worked for me, but I did not delete the C: \ Windows \ vpd.properties file. Instead, I only deleted the lines related to WebSphere Portal.



There were other "Java Developer Services Pack" (jwsdp) lines in this file that had nothing to do with WebSphere.

0


source







All Articles