ENVINSA PATCH NOTES

Transcription

1 ENVINSA PATCH NOTES

2 Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of MapInfo Corporation, One Global View, Troy, New York MapInfo Corporation. All rights reserved. MapInfo, the MapInfo logo, MapXtreme, MapMarker, miaware, Envinsa, and StreetPro are trademarks of MapInfo Corporation and/or its affiliates. Copyright 2006 The Legion Of The Bouncy Castle Copyright IPDR Organization All Rights Reserved Copyright 2006, International Business Machines Corporation and others. All Rights Reserved. Copyright 2006 Open GIS Consortium, Inc., All Rights Reserved. Copyright 2006 World Wide Web Consortium, (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University). All Rights Reserved. This product includes software developed by the Apache Software Foundation ( Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. MapInfo Corporate Headquarters: Voice: (518) Fax: (518) Sales Info Hotline: (800) Government Sales Hotline: (800) Technical Support Hotline: (518) Technical Support Fax: (518) Contact information for all MapInfo offices is located at: Adobe Acrobat is a registered trademark of Adobe Systems Incorporated in the United States. Products named herein may be trademarks of their respective manufacturers and are hereby recognized. Trademarked names are used editorially, to the benefit of the trademark owner, with no intent to infringe on the trademark. May 2006

3 Table of Contents What s In This Patch Fixes Enhancements Files and Directories Enhancement Details Confidence Scores Added to the MapInfo World Geocoding Component Improvements to Canadian Geocoding In the Location Utility Service Anti-aliasing Added to Presentation Service Route Service Now Has Pedestrian Data for North America Installer Now Supports WebLogic Chapter 2: Applying the Patch Applying the Patch Updating the Named Resources Updating the Services Testing Your Update

4 What s In This Patch 1 Welcome to the Envinsa Patch Notes. This chapter describes the fixes and enhancements that are contained in this patch. In this section: What s In This Patch Enhancement Details

5 What s In This Patch This patch includes numerous fixes and enhancements. Note that the fixes and enhancements contained in the Envinsa patch release have also been included in the Envinsa patch release. Fixes The following issues have been resolved in this patch release: Map Manager Envinsa Map Manager returns an exception when applying a theme on any datasource that does not have a MAPINFO_MAPCATALOG entry. This issue affects both Presentation and Web Map Services. Envinsa Map Manager does not allow color to be set on brush styles except solid. The brush definitions in the NamedResource have been updated to allow color to be set properly on any brush styles. Map Manager returns an error when creating a named layer using a local CM URL on UNIX systems. Map Manager returns error when starting up. Enterprise Manager Services administrators are not displayed in the Enterprise Manager console when deploying in WebSphere application server. This issue affects the Find Location, Gateway, Location Utility and Route services. The service administrators are shown in Enterprise Manager when the services are deployed to the WebSphere application server. Content Manager Content Manager returns error if there is a null value in the data. The content manager now correctly handles the null value. Content Manager returns an error if searching a content in the Catalog that is published under a different content name in the Catalog. Presentation Service Presentation Service returns error when using styles from different enterprises in the same requests..net Web Controls and mitrip Geocode street intersection streets response is overwritten if a separate submit is triggered from another control. When using the Geocode control together with the Map control, changing the Zoom level on the Map control causes the loss of information in the Geocode control MapInfo Corporation. All rights reserved. 5 Envinsa40_Patch02_Notes.pdf

6 The order in which the mapwidthtool and the mapping Web controls are defined in a form causes unexpected error. Search Preference control fails to display the search radius and maximum candidates set in the FindNearest Model. WebControlsRegistrationTool behaves incorrectly if the Web controls are already registered to Microsoft Visual Studio. EnvinsaWSMapHandler Pan, ZoomIn, ZoomOut changes the center of the map to an unexpected location. GetGeometryOverlayMap method called after a Pan action gets unexpected Presentation Service error. CenterMap() changes the zoom value in the map. Map Control Zoom Level Enter triggers the submission of the full page. Fails to render the map if the MapModel.MapContent is set to URL. Zoom Level displays the wrong distance unit sets in the model. Geocode Control Geocodes the same input address differently. Error message missing if other control triggers a submit request. Geocode type fails to render correctly. GeocodeModel.Municipality/CountrySubdivision settings do not get reset when the values are removed in the UI. Java Client SDK GetResourceInfoResponse of Presentation Service returns null pointer exception in optional LabelPosition. EnvinsaDemo Other CombineTemplateFilterRequest in US returns error. Gateway Service does not use the userid and password entered during the login. Gazetteer Landmark returns an improper response. Individual theme layer on point features generates blank map when using custom symbols. This issue occurs on all Envinsa supported platforms. Envinsa has a problem processing MapBasic PEN Styles with a width setting of 11 to 19. The Presentation Service, Web Map Service, and Map Manager have been updated to fix this issue MapInfo Corporation. All rights reserved. 6 Envinsa40_Patch02_Notes.pdf

7 Enhancements The first enhancement is to the Location Utility Service. It enables you to obtain confidence scores to determine how well returned candidates match the request input. The Client SDKs have also been updated to include API access to this capability. For more information, refer to Confidence Scores Added to the MapInfo World Geocoding Component on page 8. The second enhancement is to the Location Utility Service. Numerous improvements have been made to geocoding of Canadian locations using the Location Utility Service. For more information, refer to Improvements to Canadian Geocoding In the Location Utility Service on page 10. The third enhancement is to the Presentation Service. It enables you to switch on anti-aliasing to enhance the quality of the map created. This can be done as a service configuration setting or on a per-request basis. (The request setting overrides the service setting.) The Client SDKs have also been updated to include API access to this capability. For more information, refer to Anti-aliasing Added to Presentation Service on page 11. The fourth enhancement is to the Route Service. Pedestrian data is now available for the U.S. and Canada to facilitate calculation of walking directions via the Route Service. Files and Directories This patch release contains the following files and directories: /sdk/envinsa40dotnetsdk.zip Patched Envinsa.NET Client SDK /sdk/envinsa40javasdk.zip Patched Envinsa Java Client SDK /ENV40SRV1/installer Patched Envinsa installer /ENV40SRV6/CMC.jar Patched Content Manager component /ENV40SRV6/CMS.jar Patched Content Management Service component /ENV40SRV6/DirectoryService.jar Patched Directory Service component /ENV40SRV6/EnvinsaDemo.jar Patched Envinsa Demo component /ENV40SRV6/LocationUtilityService.jar Patched Location Utility Service component /ENV40SRV6/MapManager.jar Patched Map Manager Service component /ENV40SRV6/NamedResource.jar Patched Named Resource component /ENV40SRV6/RouteService.jar Patched Route Service component /ENV40SRV6/PresentationService.jar Patched Presentation Service component /ENV40SRV6/WebMapService.jar Patched OGC Web Map Service component /ENV40DEMO Envinsa demo disk /ENV40LIC1 Enhanced license package file /ENV40LIC2 Standard license package file 2006 MapInfo Corporation. All rights reserved. 7 Envinsa40_Patch02_Notes.pdf

8 Enhancement Details Confidence Scores Added to the MapInfo World Geocoding Component Confidence scores have been added to the MapInfo World Geocoding Component. They enable you to determine how well a returned candidate matches the Location Utility Service request input. Confidence scores range from 0 (low match confidence) to 100 (high match confidence), and are available for the following types: postal code municipality municipality subdivision country subdivision country secondary subdivision Schema Changes New integer attributes have been added to GeocodingQOSType so that candidate confidence scores can be returned in a Location Utility Service response. The schema change for the new confidence score attributes is indicated below in bold type. <complextype name="geocodingqostype"> <documentation>quality of service type</documentation> <attribute name="accuracy" type="float" use="optional"> <documentation>this is the score (probability) associated with the match function</documentation> </attribute> <attribute name="matchtype" type="string" use="optional"> <documentation>describes the type of match made by the function, example zip+4</documentation> </attribute> <attribute name="postalscore" type="int" use="optional"> <documentation>this is the confidence score of the postal code. The valid value is from 0 to 100. Higher value indicates higher confidence. It is valid only in response document that describes how well the postal code matches the input.</documentation> </attribute> <attribute name="municipalityscore" type="int" use="optional"> <documentation>this is the confidence score of the municipality. The valid value is from 0 to 100. Higher value indicates higher confidence. It is valid only in response document that describes how well this place name matches the input.</documentation> </attribute> <attribute name="municipalitysubdivisionscore" type="int" use="optional"> 2006 MapInfo Corporation. All rights reserved. 8 Envinsa40_Patch02_Notes.pdf

9 <documentation>this is the confidence score of the municipality subdivision. The valid value is from 0 to 100. Higher value indicates higher confidence. It is valid only in response document that describes how well this place name matches the input. </documentation> </attribute> <attribute name="countrysubdivisionscore" type="int" use="optional"> <documentation>this is the confidence score of the country subdivision. The valid value is from 0 to 100. Higher value indicates higher confidence. It is valid only in response document that describes how well this place name matches the input.</documentation> </attribute> <attribute name="countrysecsubdivisionscore" type="int" use="optional"> <documentation>this is the confidence score of the country secondary subdivision. The valid value is from 0 to 100. Higher value indicates higher confidence. It is valid only in response document that describes how well this place name matches the input. </documentation> </attribute> </complextype> The following code (in bold type) shows an example of how the confidence scores are returned as attributes of a GeocodeMatchCode element in a Location Utility Service response: <GeocodeMatchCode accuracy="0.0" matchtype="z1" municipalityscore="95" postalscore="100" xsi:type="ns2:geocodingqostype" /> Java SDK Changes The following methods have been added to the com.mapinfo.miaware.clientsdk.common.geocodingqos class to provide access to the returned confidence scores: Method public int getpostalcodescore() public int getmunicipalityscore() public int getmunicipalitysubdivisionscore() Description Returns the confidence score of the postal code. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned. Returns the confidence score of the municipality name. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned. Returns the confidence score of the municipality subdivision name. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned MapInfo Corporation. All rights reserved. 9 Envinsa40_Patch02_Notes.pdf

10 Method public int getcountrysubdivisionscore() public int getcountrysecsubdivisionscore() Description Returns the confidence score of the country subdivision name. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned. Returns the confidence score of the country secondary subdivision name. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned..net SDK Changes The following properties have been added to the com.mapinfo.miaware.clientsdk.common.geocodingqos class to provide access to the returned confidence scores: Method public virtual int PostalCodeScore public virtual int MunicipalityScore public virtual int MunicipalitySubDivisionScore public virtual int CountrySubDivisionScore public virtual int CountrySecSubDivisionScore Description Returns the confidence score of the postal code. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned. Returns the confidence score of the municipality name. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned. Returns the confidence score of the municipality subdivision name. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned. Returns the confidence score of the country subdivision name. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned. Returns the confidence score of the country secondary subdivision name. Valid values are from 0 to 100. A higher value indicates higher confidence. If the score is not available, -1 is returned. Improvements to Canadian Geocoding In the Location Utility Service Geocoding Canadian locations using the Location Utility Service has been greatly improved. The new features include: more efficient data storage 2006 MapInfo Corporation. All rights reserved. 10 Envinsa40_Patch02_Notes.pdf

11 faster throughput user dictionaries better matching, with fewer false positives fallback to postal code or city Geocoding Canadian location using the Location Utility Service will now correctly return more candidates when the closematchesonly option is set to false (the default). Anti-aliasing Added to Presentation Service An anti-aliasing option has been added to the Presentation Service. This enables you to specify antialiasing for map rendering in Presentation Service requests. The following illustrations show how map display quality can be improved by turning on anti-aliasing: Anti-aliasing Off Anti-aliasing On 2006 MapInfo Corporation. All rights reserved. 11 Envinsa40_Patch02_Notes.pdf

12 Schema Changes A new boolean attribute has been added to OutputTypeEx to enable users to specify anti-aliasing in Presentation Service requests. The schema change for the new anti-aliasing attribute is indicated below in bold type. <complextype name="outputtypeex"> <documentation>mi OutputType</documentation> <complexcontent> <extension base="xls:outputtype"> <sequence> <element name="screencontext" type="mixls:screencontexttype" minoccurs="0"/> <element name="cartographiclegend" type="mixls:cartographiclegendtype" minoccurs="0"/> <element name="scalebar" type="mixls:scalebartype" minoccurs="0"/> <element name="vrmlcontext" type="mixls:vrmlcontexttype" minoccurs="0"> <documentation>only GeoVRML1.1 supported now</documentation> </element> <element name="wbmpcontext" type="mixls:wbmpcontexttype" minoccurs="0"/> </sequence> <attribute name="returnzoomlevel" type="string" use="optional" default="off"> <documentation>set to "on" to return the zoom level in the response, otherwise set to "off". </documentation> </attribute> <attribute name="radiustype" type="mixls:zoomradiustype" use="optional" default="inner"/> <attribute name="zoomlevelunit" type="xls:distanceunittype" use="optional"> <documentation>the unit of returned zoom level in response, the default is meter. </documentation> </attribute> <attribute name="antialiasing" type="boolean" use="optional"> <documentation>rendering is done with antialiasing, using the server setting if not specified</documentation> </attribute> </extension> </complexcontent> </complextype> The following code (in bold type) shows how this attribute can be used in a Presentation Service request: <_RequestParameters xsi:type="ns2:portraymaprequesttype"> 2006 MapInfo Corporation. All rights reserved. 12 Envinsa40_Patch02_Notes.pdf

13 <Output xsi:type="ns3:outputtypeex" BGcolor="#ffffff" content="url" format="image/png" height="500" transparent="true" width="500" antialiasing="true" xmlns:ns3=" </Output> <Basemap filter="exclude"/> </_RequestParameters> Anti-aliasing Configuration in Enterprise Manager A service configuration setting for the new boolean attribute defaultantialiasing has been added in the Enterprise Manager. The default setting is false. To change the setting, go to Global > Rendition > Preferences > defaultantialiasing, as shown here: Java SDK Changes The following three constants have been added to the OutputEx class to define the rendering preference: Constant Value Description RENDERING_DEFAULT 0 Specifies that the server-side setting will be used when rendering maps. Maps will be rendered with or without anti-aliasing according to the server-side setting. RENDERING_SPEED 1 Specifies that speed is preferred when rendering maps. Maps will be rendered without anti-aliasing MapInfo Corporation. All rights reserved. 13 Envinsa40_Patch02_Notes.pdf

14 Constant Value Description RENDERING_QUALITY 2 Specifies that quality is preferred when rendering maps. Maps will be rendered with anti-aliasing. A corresponding pair of set/get methods for this preference have also been added: public void setrenderingpreference(int rendering) public int getrenderingpreference() The following code (in bold type) shows how to set the rendering preference to specify anti-aliasing: PortrayMapRequest maprequest = new PortrayMapRequest(METHOD_NAME,VERSION, "R1"); //specify the width, height and mime image format in the map output OutputEx output = new OutputEx(500, 500, "image/png"); output.setrenderingpreference(outputex.rendering_quality); //return embedded image data. output.setpresentationcontent(output.content_base64);//"data" maprequest.addoutput(output); //suppose that all layers should be visible, set nothing to exclude. Basemap basemap = new Basemap(Basemap.FILTER_EXCLUDE); maprequest.setbasemap(basemap);.net SDK Changes A new enum class RenderingPreference has been added. All available rendering preferences are defined in this class: Constant Default Speed Quality Description Specifies that the server-side setting will be used when rendering maps. Maps will be rendered with or without anti-aliasing according to the server-side setting. Specifies that speed is preferred when rendering maps. Maps will be rendered without anti-aliasing. Specifies that quality is preferred when rendering maps. Maps will be rendered with anti-aliasing. A corresponding property named RenderingPreference has also been added to the Output class. The following code (in bold type) shows how to specify the rendering preference based on the server setting. PortrayMapRequest pr = new PortrayMapRequest(); pr.requestid = "R1"; //Set map outputs //output1: define the map format, size and context Output output1 = new Output(); 2006 MapInfo Corporation. All rights reserved. 14 Envinsa40_Patch02_Notes.pdf

15 output1.renderingpreference = RenderingPreference.Default; output1.width = 500; output1.height = 500; output1.format = "image/gif"; Output[] outs = {output1}; pr.output = outs; //assume that all layers should be visible, set nothing to exclude. Basemap basemap = new Basemap(LayerTypeFilter.Exclude); pr.basemap = basemap; Route Service Now Has Pedestrian Data for North America Pedestrian data is now available for the U.S. and Canada to facilitate calculation of walking directions via the Route Service. Installer Now Supports WebLogic 9.0 The Envinsa Location Platform installer now supports deployment to BEA WebLogic Server MapInfo Corporation. All rights reserved. 15 Envinsa40_Patch02_Notes.pdf

16 Applying the Patch 2 This chapter describes the steps you need to follow to apply the Envinsa Patch. In this section: Applying the Patch Testing Your Update

17 Chapter 2: Applying the Patch Applying the Patch Use the following steps to apply the Envinsa Patch using the Envinsa 4.0 Enterprise Manager. Updating the Named Resources 1. Back up your NamedResource directory in the Platform domain (for example, <installdirectory>/envinsa-4.0/platformdomain/namedresource) as you will have to copy some files back to this directory after installing the new NamedResource component. 2. Start the Enterprise Manager console. 3. Using the Enterprise Manager, uninstall the NamedResource component. For details, refer to the Uninstalling a Resource (Data) section in Chapter 8: Managing Deployments in the Administration Guide. 4. Using the Enterprise Manager, install the new NamedResource component. Make sure the location of the domain directory is the same as the previous location. For details, refer to the Deploying a Data Resource section in Chapter 7: Deploying in the Administration Guide. 5. From the backup NamedResource directory, copy the MapDisplay subdirectory (under NamedResource/namedResources/PUBLIC) back to the newly installed NamedResource directory. Also copy any named resources that you have created yourself back to the NamedResource directory. Updating the Services 1. Back up the following files in the service domain directory of each Envinsa Service being updated: <servicedomain>/resources/admin/*.xml <servicedomain>/resources/admin/*.xsd <servicedomain>/resources/admin/*.emks <servicedomain>/resources/billing/* <servicedomain>/resources/archive/* 2. Make sure all services are up and running as the Enterprise Manager requires these services to propagate information to other peers. 3. Start the Enterprise Manager console. 4. Using the Enterprise Manager, uninstall the services you are updating. For details, refer to the Uninstalling a Service section in Chapter 8: Managing Deployments in the Administration Guide. 5. Using the Enterprise Manager, install the new versions of the services. Make sure the locations of the domain directories are the same as the previous locations, and that all container parameters (host, port, directory) are the same as before. For details, refer to the Deploying a Service section in Chapter 7: Deploying in the Administration Guide. 6. Shut down the Web containers. 7. Copy the files you backed up from the <servicedomain>/resources directories in step 1 back to the newly installed <servicedomain>/resources directories MapInfo Corporation. All rights reserved. 17 Envinsa40_Patch02_Notes.pdf

18 Chapter 2: Applying the Patch 8. Restart the Web containers for changes to take effect. The patch upgrade is now complete. You can test the upgrade through the Envinsa Demonstration for the services, as described in Testing Your Update on page 18. Testing Your Update Test your service updates using the Envinsa Demonstration (EnvinsaDemo) application installed with your Envinsa Web Services. This is the demonstration used to test your Web Service installations. The EnvinsaDemo application lists all of the services you have installed and demonstrates the discovery process, which discovers Envinsa Web Services on your network. It also shows the request and response messages for Envinsa Web Services. To run EnvinsaDemo, ensure that the Web container hosting EnvinsaDemo and affected Web Services is running. 1. Start EnvinsaDemo. Enter the following URL in your Web browser. Substitute your host name and port number. Be sure to use the correct port number for where you have installed EnvinsaDemo. EnvinsaDemo displays. For example: 2006 MapInfo Corporation. All rights reserved. 18 Envinsa40_Patch02_Notes.pdf

19 Chapter 2: Applying the Patch 2. Select the Web Service that you updated. 3. Select an XML Request. In the following example the Gateway link and Nortel_HandleRequest data were chosen in order to test an update to the Gateway Service MapInfo Corporation. All rights reserved. 19 Envinsa40_Patch02_Notes.pdf

20 Chapter 2: Applying the Patch Click the Submit Request button to submit a request. The results of the request display. For example: Test any other service updates that you made, using the same procedure. Do You See an Error Message? An error message displays if an issue occurred installing the service. The message should indicate the type of error. Uninstalling and reinstalling the affected service should resolve any issues. If it does not, then contact your MapInfo Representative for further assistance MapInfo Corporation. All rights reserved. 20 Envinsa40_Patch02_Notes.pdf