Manual steps for migrating projects with customized files

After migration, a number of files that might potentially need customization will have names with the following format: filename_version_bak. This has been done so you don't lose your customizations due to migration.

Customized projects may require manual intervention. See WebFacing support for multiple browsers for further details.

Certain display files in projects created before V7.5.0 might need reconversion after migration to display in Firefox browser, such as DSPF fields using .CURRENTVALUE or .REF replacement values in their Web settings. It is recommended that a re-conversion be performed on the migrated WebFacing project. To convert a single resource, locate and select the DDS or UIM Help file in the WebFacing Projects view. To convert the entire project, locate and select the project in the WebFacing Projects view. Right click and select Convert.

If you customized your WebFacing project, you might need to merge your customizations from the original files into the following:
Note: If the project being migrated is a HATS/WebFacing enabled Web project, then the corresponding HATS project needs to be migrated also.

Rendering of styles in browsers

There are some differences in how different browsers render styles. Several changes have been made to the IBM® supplied styles so they work in the Firefox browser. If you create a new WebFacing project, the styles will contain those changes. However, if you migrate an existing project created before V7.5.0 that uses an IBM supplied style, the five files that control the style are backed up, if found, and replaced with the new ones. The five files that control the style are:
  • stylename.css
  • appearea.css
  • PageBuilder.jsp
  • CmdKeys.jsp
  • MenuKeys.jsp (not available in all styles)
You need to compare the new and previous style files and merge any changes you might have made. If you do not use an IBM supplied style, or you have additional style changes, you have to make those changes manually.
To see what changes were made to the new files, compare the old style files with the updated files. The following list shows the changes made:
  • All values must have units. In Internet Explorer, values are considered as pixels unless another value is specified. For example:
    .launchbutton
    {
     border-color:black;
     border-width:1px;
     text-align:right;
    }
  • In some of the IBM supplied styles, an incorrect syntax was specified for the margins. Internet Explorer tolerated the syntax, but Firefox does not. For example, in stylename.css, margin : 0px,0px,0px,0px; was changed to remove the commas: margin : 0px 0px 0px 0px;. For margins where the four margins had the same setting, the change would be margin : 0px;.
  • CSS expressions that were valid only for Internet Explorer (shown in italics in the following example) were removed from the .wf_layer class and replaced with the background color of the body (shown in bold in the following example):
    .wf_layer {
    		background-image:expression(document.body.currentStyle.backgroundImage);
    		background-color:expression(document.body.currentStyle.backgroundColor);
    		background-repeat:expression(document.body.currentStyle.backgroundRepeat);
    		background-attachment: expression(document.body.currentStyle.backgroundAttachment);
    		background-color: #E3C993; 
    	}
  • The cursor: hand; notation changed to cursor: pointer;
To enable WebFacing applications to display properly when they are rendered using a strict doctype, additional changes were made to the following files:
  • apparea.css:
    SPAN.wf_field  {
    		width: 100%;
    		border-style: none;
    		display: inline-block; //for all browsers
    		display: -moz-inline-block; //for Firefox 2}
    .scrollbarUpArrow {
    	background-color: transparent;
    	background-image: url("UpArrow.gif");
    	background-position: bottom;
    	background-repeat: no-repeat;
    	width: 16px;
    	height: 16px;
    }
    
    .scrollbarDownArrow {
    	background-color: transparent;
    	background-image: url("DownArrow.gif");
    	background-position: top;
    	background-repeat: no-repeat;
    	width: 16px;
    	height: 16px;
    }
    
    .scrollbarSlider {
    	background-color: #73a2bd;
    	background-image: url("CurrentSegment.gif");
    	background-repeat: repeat-y;
    }
    
    .scrollbarBackground {
    	background-color: transparent;
    	background-image: url("segment.gif");
    	width: 16px;
    	height: 100%;
    	background-repeat: repeat-y;
    }
  • PageBuilder.jsp
    The height for certain styles where page elements should fill the vertical space is added:
    <html <wf:lang text="lang="/> style="height:100%"> 
    <head>
    ...
    </head>
    <body style="height:100%">
    ...

Feedback