Upgrading the embedded WebSphere Application Server to a full installation of WebSphere Application Server
Before you begin
Capture the settings from the installed embedded WebSphere Application Server:
Keep in mind: This doesn't actually migrate anything from one installation to another. This is just taking note of the eWAS settings to reenter them in the full WAS. Raj did not want to take "migrating" out of the title even though there is no real migration going on here. Raj's original text file is attached to task 51776.
- Start the IBM Rational® Asset Manager server that runs on the embedded WebSphere Application Server.
- In a web browser, type the URL of the server setup application. For example:
http://localhost:13080/ram.setupDraft comment:
http://localhost:13080/ram.setup/wizard/main/index.jsp - Click Next until you reach the Summary page, and then verify that the current installation has no issues. If issues exist, correct them before you continue with the server setup.
- Click the Deployment link to return to the beginning of the setup, and then click Previous to return to the Introduction page.
- Back up the configuration report.
- Click .
- Right-click the page and save the file locally.
- Close the configuration report.
- In the server setup application, review each page and note the values that you defined for
the embedded WebSphere Application Server
installation. Either write the selections or take screen captures of them. The following table
shows the selections to note on each page.
Table 1. Information to capture about the embedded WebSphere Application Server Information to review in server setup
Server setup page Items to note Introduction
- Database vendor name
- Authentication type
- IBM Rational Team Concert™ server
- Server or cluster for IBM Rational Asset Manager:
You can choose to install a Rational Team Concert™ server or work with an existing server. If you select to not install a new server, then you will continue to use that server even when running on a full installation of WebSphere Application Server.
Deploy IBM Rational Asset Manager
The installed applications and documentation:- IBM Rational Asset Manager
- Rational Team Concert
- Help and user assistance
- Asset-based development (ABD) process and governance
Configure Database: Part 2
Database connection properties:- Database vendor
- Database server
- Port
Database resources:- Database JAR files. Even if you have the JAR files, you might be required to upload them again to the new server.
IBM Rational Asset Manager core database:- Name
- User ID
- Password
IBM Rational Asset Manager lifecycle database:- Name
- User ID
- Password
Users and Authentication
The values depend on the Authentication type that was selected on the Introduction page.
You might capture these values:- LDAP vendor
- Server
- Port
- Bind user DN and password
- Administrator ID
- User search filter
- User search base
Configure IBM Rational Asset Manager Settings: Part 1
Configure the license server:- License server or key
- License type
Server address, such as http://host:13080
Configure the paths:- IBM Rational Asset Manager server
- Web services
- Help and user assistance
- Asset Based Development Process and Governance
Configure IBM Rational Asset Manager Settings: Part 2
Disk storage settings- Persist folder
- Local storage folder
- Index folder
Configure Lifecycle management settings
Rational Team Concert path:- Server URL
- Type
- If you selected I need to install a new server for the Rational Team Concert server option on the Introduction page, the type is Internal.
- If you selected I have an existing server for the Rational Team Concert server option on the Introduction page, the type is External.
Rational Team Concert - User Management- Jazz™ Administrator ID
- Password
Rational Team Concert - Project Area Management- Project Area Name
- Project Area Administrator ID
- Password
Procedure
LJW: If you split this topic in two, you can remove this stepsection tag.
LJW: There are enough prerequisite steps for this task that I think we can split the task in two. We could have one topic with the prereq text called "Preparing to upgrade the embedded WebSphere Application Server" and then keep this topic as is, but remove most of the text from the prereq section and just say "Complete the tasks in "Preparing to upgrade the embedded WebSphere Application Server."