Upgrading to Serena Business Mashups
Download
1 / 31

Upgrading to Serena Business Mashups - PowerPoint PPT Presentation


  • 105 Views
  • Uploaded on

Upgrading to Serena Business Mashups. Presented by: Ethan Goldberg. Before you Begin. Review the moving to SBMS guide. Know your ODBC connection Username and Password and the port number for your database (Default is 1521 for Oracle and 1433 for SQL Server)

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Upgrading to Serena Business Mashups' - janus


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

Upgrading to Serena Business Mashups

Presented by: Ethan Goldberg


Before you begin
Before you Begin

  • Review the moving to SBMS guide.

  • Know your ODBC connection Username and Password and the port number for your database (Default is 1521 for Oracle and 1433 for SQL Server)

  • Know Database server name\Instance name.

  • Back up your database prior to the upgrade.

  • Make sure you have enough disk space for the upgrade, if you use the Unicode upgrade utility the size of your database could potentially double.


Multi environment upgrade
Multi-Environment Upgrade

  • The multi-environment upgrade requires a specific process to keep these multiple databases synchronized. A very high-level view of the process is as follows:

  • 1. Complete all in-progress changes and move them to your production environment.

  • 2. Upgrade your production environment.

  • 3. Re-establish the other environments using a copy of the upgraded production database.


When to run the uuencode utility

Always run the utility if your Database is SQL

If using an Oracle database running the utility depends on a combination of factors.

When to run the Uuencode Utility


What the unicode utility does

During the Unicode Upgrade Utility, in a nutshell, all text fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?The utility steps through each table in the database and does this:- Creates a Temp table with columns matching the target table's text fields, but in Unicode.- Copy the data from the target table into the temp table- Drop the columns in target tables and recreate them as Unicode compliant columns- Copy the data back from the temp table to the target table- Drop the temp table and start over again with the next target table

Because Unicode uses 2 bytes to describe each character, there can be significant increases in the size of each ROW in a table.  This is especially important in MS SQL Server because of the row size limitation of 8060 bytes.  This is a hard limit and will cause the Unicode Upgrade Utility to halt.  You will need to clean out some columns and restart the upgrade from the beginning.

Two important points to remember:1.  The resulting database may be twice as large as the old TT 6.6.1 database, so make sure that they have plenty space for the database to grow.2.  Always, always backup the database before doing the utility, so that you have a clean copy to revert to in case of a failure.

What the Unicode Utility does


Installation welcome screen
Installation Welcome Screen fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


End user license agreement
End User License Agreement fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Installation path
Installation Path fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Installation type
Installation Type fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Component selection
Component Selection fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


License server
License Server fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Sample database screen
Sample Database Screen fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Select database type
Select Database Type fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Database connection information
Database Connection Information fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Website selection screen
Website Selection Screen fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Single sign on screen
Single Sign-on Screen fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Jboss port
JBoss Port fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Mail server information
Mail Server Information fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Installation summary screen
Installation Summary Screen fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Installation running
Installation Running fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Post installation summary
Post Installation Summary fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Unicode upgrade utility
Unicode Upgrade Utility fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Unicode upgrade utility running
Unicode Upgrade Utility Running fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Unicode upgrade utility complete
Unicode Upgrade Utility Complete fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Administrator upgrade screen
Administrator Upgrade Screen fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Mashup administrator
Mashup Administrator fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Mashup manager login screen
Mashup Manager Login screen fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Mashup manager
Mashup Manager fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Repository options screen
Repository Options Screen fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


Answers fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?For Your Questions


Thank you for attending
Thank you for Attending fields are translated to Unicode text fields.  For example all varchar fields are converted to nvarchar.  But, how is that accomplished?


ad