Other Migration-Related Changes

Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
Service method="(GET|HEAD|POST)" type="*~magnus-internal/*" fn="send-file"
Service method="TRACE" fn="service-trace"
<If $uri =~ ".jsp$">
Output fn="set-variable" insert-srvhdrs="Content-type: text/html"
</If>
Error fn="error-j2ee"
AddLog fn="flex-log"
</Object>

<If  $code = "302" >
Output fn="set-variable" insert-srvhdrs="content-type:text/html"
</If>

<If $srvhdrs{'content-length'} = "0">
Output fn="set-variable" insert-srvhdrs="content-type:text/html"
</If>

JDBCRESOURCE and JDBCCONNECTIONPOOL element changes

The JDBCRESOURCE and JDBCCONNECTIONPOOL elements in server.xml have been consolidated into the jdbc-resource element.

For each existing JDBCRESOURCE, a corresponding jdbc-resource element will be created in the new server-instance/config/server.xml.

Element name changes in server.xml

The following element names have changed: 

• MAILRESOURCE is now mail-resource.

• CUSTOMRESOURCE is now custom-resource.

• EXTERNALJNDIRESOURCE is now external-jndi-resource, and most of the attribute names have also changed.

Element changes in server.xml

• SEARCH is now called search-app.

• SEARCHCOLLECTION is now called search-collection-copy-path.

• The PROPERTY subelement has been removed from SEARCHCOLLECTION.

• The WEBAPP subelement has been removed, a uri attribute has been added to point to the search web application, and most of the attribute names have changed.

search-collection-copy-path

Specifies the path to which search collection information will be copied when migrating search collections. The following migration scenarios are possible: If the Web Server 6.0 or 6.1 search collection path is outside the Web Server 6.0 or 6.1 instance, then the migrated search collection path will point to the Web Server 6.0 or 6.1 search collection path, and this option will be disregarded. If the Web Server 6.0 or 6.1 search collection path is within the Web Server 6.0 or 6.1 instance, and a valid path is specified for this option, then the search collection information will be copied to the following directory: searchCollectionPath/configName/virtualServerName/collectionName. If the specified path is not valid, an error message will be logged. If the Web Server 6.0 or 6.1 search collection path is within the Web Server 6.0 or 6.1 instance but no path is specified for this option, then the search collection information will not be copied. A message will be written to the migration log asking the user to manually copy the search collection information using the wadm add-search-docs command. In this case, the migrated search collection path will be the following: WebServer7Config-base/https-configName/config/collections/virtualServerName/collectionName.

SECURITY element moved and renamed security (all lower case)

In Web Server 6.1, the SECURITY element was under the JAVA element in server.xml. In Web Server 7.0, the JAVA element has been split into two elements: jvm and servlet-container. In Web Server 7.0, the security element is under the servlet-container element and is called security (all lower case) instead of SECURITY. The necessary changes are made in the new server_instance/config/server.xml.

Decode Cookies 

In Web Server 6.1, + in cookie values were not decoded. However, in Web Server 7.0 the plus + is decoded to spaces. The default value is false.

WEBAPP element changed in server.xml

The WEBAPP element is now called web-app and has been moved under the virtual-server element. The changes are made in the new install-dir/admin-server/config-store/config_name/config/server.xml. Changes are also be made in the sun-web.xml and web.xml files for the web applications. If the web application was located inside the old install-dir, it is physically migrated and changes are made in sun-web.xml and web.xml files of the web applications else, the web applications path element in the migrated server.xml is modified to point to the old web application directory. No changes will be made to sun-web.xml and web.xml. A warning message is recorded in the migration log file to manually edit these XML files.

Element changes in server.xml

• DAV is now called dav.

• DAVCOLLECTION is now called dav-collection.

• The PROPERTY subelement has been removed.

• The dav-collection subelement has been moved under the virtual-server element and most of the attribute names have changed. The necessary changes are made in server.xml.

Changes to obj.conf

Necessary modifications are made in the obj.conf file. Specifically:

• ACL and REPORTS are added in the default object's service-dav list of methods. For example:

  <Object name="default">
  ...
  Service fn="service-dav"
  method="(OPTIONS|PUT|DELETE|COPY
  |MOVE|PROPFIND|PROPPATCH|LOCK
  |UNLOCK|MKCOL|ACL|REPORT)"
  Error fn="error-j2ee"
  AddLog fn="flex-log"
  name="access"
  <Object>

• ACL and REPORTS are added in the dav object's service-dav list of methods. For example:

  <Object name="dav"
  PathCheck fn="check-acl"
  acl="dav-src"
  Service fn="service-dav"
  method="(GET|HEAD|POST|PUT|DELETE
  |COPY|MOVE|PROPFIND|PROPPATCH|LOCK
  |UNLOCK|MKCOL|ACL|REPORT)"
  </Object>

New ACL entry in default.acl

The following new ACL entry is added in default.acl only if the dav-src ACL exists in generated.https-server_id.acl:

acl uri=/magnus-internal/";
deny (all) user="anyone";
allow (list) user="all";