OracleFMW MapViewer 11.1.1.4.1 (PS3) Release Notes

This is the MapViewer 11.1.1.4.1 patch released on March 2011.

A partial list of bugs fixed in this release:

10241219 HEATMAP FOI THEME NOT DISPLAYED DUE TO CONTAINER SRID DIFF
10218853 MVTHEMEBASEDFO.ISVISIBLE RETURNS WRONG RESULT WITH THEME MIN/MAX
         VISIBLE LEVEL
10207236 VERTICAL OFFSET OF NAVIGATION PANEL MESS UP ZOOM SLIDER BAR
         CLICKING
10197810 JAVA EXCEPTION THROWN DURING MAP CACHING
10177458 UNABLE TO DECODE WFS CAPABILITIES DUE TO NULL FEATURE ATTRIBUTE
10138718 INST:DEMO DEMOS FILES IN./BI_HOME/BIFOUNDATION/JEE/MAPVIEWER.EAR
10108013 EXTREMELY BAD PERFORMANCE WITH MARKER STROKE WHEN ZOOMED IN
10100897 MAPBUILDER CANNOT EASILY CONNECT TO RAC
10100889 PATH ATTRIBUTE IN SAVE_IMAGES_AT WRONG FOR WLS
10093532 WHOLE IMAGE THEME BASED FOI LAYER DOES NOT SHOW HAND/POINTER CURSOR
         IN IE
10084618 CASED LINES FROM DIFFERENT THEMES ARE ALL JOINED TOGETHER
10032454 3D GEOM THEME BROKEN WITH CACHING=ALL
10029922 SUPPORT FOR ELOCATION AS A HOSTED MAP TILE SERVICE
10022302 NEED AN OPTION TO SKIP INDEX BUILDING IN SHAPEFILE IMPORT TOOL
9956791  SLOW QUERY AT STREET ZOOM LEVEL THAT REQUIRES INDEX HINT
9924866  WMS GETCAPABILITIES DOES NOT RETURN PRECISE MBR FOR LAYERS
9881543  NSDP JOIN FAILS WHEN THE THEME HAS A LABELING COLUMN DIFFERENT FROM
         THE KEY COL
8623505 INCORRECT RENDERING WHEN GEOMETRIES HAVE MANY SIGNIFICANT DIGITS 

and many Oracle Maps JavaScript API related bug fixes.

Enhancements in this release:

o WMS theme now supports authentication when required by a remote WMS service
  provider. User name and password can be stored as part of a WMS theme 
  through MapBuilder. The Java client API also supports supplying the 
  authentication detail at run time.


This patch includes all fixes and enhancements from earlier MapViewer patches such
as patch 10084760.


To apply the patch perform the following steps:
-----------------------------------------------

The correct steps for redeploying the mapviewer patch should be:

0. Backup any modified files in your existing MapViewer folder!   

1. Important note: As always, make sure to first backup any files you may 
   have changed or added to your current MapViewer instances.

2. This patch  contains the mapviewer.ear file that needs  to be deployed
over your existing MapViewer instance.
   
   For actual deployment instructions, please refer to the included MapViewer
User's Guide.


   Specifically, refer to section 1.4 for deployment instructions.

Note that while  deploying the mapviewer.ear, there is no  need to perform
the extra step  of copying  a xmlparserv2.jar into MapViewer's  WEB-INF/lib
folder.  
This JAR file and its dependent files are already in the WEB-INF/lib folder.


Other Notes
    
A. This patch is self sufficient and does not depend on any existing MapViewer
   instance. To apply this patch over an existing MapViewer instance, or to
   freshly install a new one, please take the supplied mapviewer.ear file
   and deploy it to your J2EE container.
    
B. If you are currently using the Quickstart kit from a previous version
   (MapViewer 11g R1 or 10.1.3.3), you can deploy this patch by simply copying
   the new mapviewer.ear over the one in $OC4J_HOME/j2ee/home/applications, 
   followed by a restart of OC4J.

   Note that this release also comes with a new Quickstart kit, which is based
   on the OC4J standalone version 10.1.3.5.

C. Steps/Notes to re-deploy MapViewer in weblogic

    1. Shut down mapviewer
    2. Shutdown weblogic
    3. Go to dir $MAPVIEWER_HOME where the file mapviewer1.ear is
    4. Delete the old mapviewer1.ear
    5. Place there the new file and name it also mapviewer1.ear
    6. delete directory mapviewer.ear
    7. Create new directory mapviewer.ear
    8. Unpack the mapviewer1.ear into directory mapviewer.ear
    9. Change to directory mapviewer.ear
   10. Rename web.war to web1.war
   11. Create dir web.war
   12. Unpack web1.war into directory web.war
   13. Startup weblogic