Monday Jul 22, 2013

Limitations in client side styles (for Vector Layers/FOI) in the V2 API

The V2 API (in MapViewer versions 11.1.1.7.0 and 11.1.1.7.1) currently has some limitations in styles that can be used for vector layers (aka FOI). That is, some styles which can be defined in MapBuilder and used for FOI with the V1 API cannot be used for vector layers in V2.

The current limitations are:

LINE styles in v2 have these limitations:
   1. no dash support (on any part of the line style)
   2. no marker-pattern or built-in arrow head on LINE style

AREA styles that use image as fill pattern: not supported 

TEXT styles:  some labeling hints are not supported, such as sticky, multi-line auto-wrap

DOT density style: not supported in v2



Connecting to a 12c database instance with MapViewer 11.1.1.7.x

The the jdbc connection string (or jdbc url) for a 12c database now requires a service name instead of a SID.

In MapViewer 11.1.1.7.1 the jdbc info in the map_data_source element in the mapviewer configuration file accepts a service name but requires a different syntax. The relevant details (from the README) are

MapViewer native (non-container) data sources can now use database service name in place of SID. 
To supply a db service name, you will use the same jdbc_sid attribute, but specify the service name 
with double slashes in front, e.g.:

  <map_data_source name="myds"
    jdbc_host="foo.com" 
    jdbc_sid="//mypdb1.foo.com" 
    jdbc_port="1522" 
    ... ...
  />

If you're using 11.1.1.7.0 then you need to use a container data source to connect to a 12c instance.

i.e. instead of using

<map_data_source name="my_12c_test"

                   jdbc_host="mydbinstance"
                   jdbc_sid="//pdborcl12c.foo.com"
                   jdbc_port="1522"
                   jdbc_user="mytestuser"
                   jdbc_password="m2E7T48U3LfRjKwR0YFETQcjNb4gCMLG8/X0KWjO00Q="
                   jdbc_mode="thin"
                   number_of_mappers="6"
                   allow_jdbc_theme_based_foi="false"
                   editable="false"
   />
use
  <map_data_source name="my_12c_test"
                   container_ds="jdbc/db12c"
                   number_of_mappers="6"
                   allow_jdbc_theme_based_foi="false"
                   editable="false"
   />

In my case the Glassfish 3.1.2.2 JDBC connection pool definition was:
Property
url  jdbc:oracle:thin:@mydbinstance:1522/pdborcl12c.rest_of.service.name

Uncheck the Wrap JDBC Objects option in Advanced panel, i.e. the Edit JDBC Connection Pool Advanced properties page.
Add a JDBC resource for that newly created pool and use that in mapviewerconfig.xml as above

About

Official blog for Oracle FMW MapViewer and related products.

Search

Categories
Archives
« July 2013 »
SunMonTueWedThuFriSat
 
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
23
24
25
27
28
29
30
31
   
       
Today