Upgraded PRIME to 3.8, see Upgrade Identity Manager.

The Jasper Reports framework, that is used in PRIME to create PDF documents for reporting, PIN letter, receipts, and so on, has been updated for PRIME 3.8 to version 6.5.1.

1. To create jasper report templates (.jrxml) for PRIME 3.8, make sure you use an updated report design tool, such as Jaspersoft Studio version 6.6 or later.

2. If binary data, for example photos, is used in the PDF templates, the following change needs to be done in the JRXML template:
   Change from:

   Code Block
   language xml title Old definition
   <field name="Person_Photo" class="net.sf.jasperreports.engine.JRRenderable"/>

   to:

   Code Block
   language xml title New definition
   <field name="Person_Photo" class="net.sf.jasperreports.renderers.Renderable"/>

   The change can also be done by editing the JRXML template in the updated report design tool.

   All other report functionalities will work without any further changes.

The html version of PRIME Explorer is the default front end for operators. The java webstart PRIME Explorer is still supported, but will soon become deprecated.

Customers who still want to use the PRIME Explorer java version instead of the html Version, must change the style settings on the PRIME Explorer server:

1. Open the file \prime_explorer\eclntjsfserver\config\sessiondefaults.xml for editing.

2. Change from:

   Code Block
   language xml title Old definition
   <sessiondefaults style="act3_risc"/>

   to:

   Code Block
   language xml title New definition
   <sessiondefaults style="act3 "/>

   
   

New settings were added in PRIME Explorer to avoid failure of JPKIEncoder download or CA connector calls during card production, if https client authentication is used.

If you use client authentication to log in to PRIME Explorer or User Self-Service Portal (USSP), such as browser-based smart card or soft token login, do the following:

1. Open the file \webapps\prime_explorer\WEB-INF\classes\system.properties for editing.

2. Make sure to specify https ports without client authentication for both JPKIEncoder download or CA connector calls:

   Code Block
   language text title JPKIEncoder download
   # if you use client-auth to log into PRIME/USSP you need to configure overrides to non-client-auth HTTPS ports here, # otherwise the CardSDK trying to download the JPKIEncoder or the JPKIEncoder calling an integrated CA connector will not be able to connect # # for JPKIEncoder download: #webappUrlInfo.httpsOverridePort=18443 # # for CA connector calls: #webServer.httpsOverridePort=18443

   
   

Server-side card production was revised with this release to overcome a couple of limitations in the old implementation.

Specifically, the task serverSideProductionPreviewTask.jsp was removed and service tasks for server-side production were changed. This means, custom processes using this feature need to be adapted accordingly.

Contact Nexus for further details, if you are using this feature.

All standard processes and custom processes using client-side card production, which is the default approach, will not be affected and can be used with PRIME 3.8 without any changes.

Application-based smart card login is now disabled by default, because it is only supported by the java webstart version of PRIME Explorer.

If you want to enable application-based smart card login, do the following:

1. Open the file \webapps\prime_explorer\WEB-INF\classes\system.properties for editing.

2. Set login.applicationBasedSmartCardLoginEnabled to true:

   Code Block
   language text title JPKIEncoder download
   login.applicationBasedSmartCardLoginEnabled=true

   
   

Customers using the standard processes for provisioning certificates to Personal Mobile must upgrade the configuration to the new 3.8 processes for the Personal Mobile use cases.

The configuration has changed significantly, new service tasks have been introduced due to major improvements and interface changes on Personal Mobile Messaging Server.