Upgrading from eView513 to eView 6 quick tips
How to migrate from eView513 to eView 6.
1. Create a Master Index project in NB6 via MDM wizard.
2. Overwrite master.xml, object.xml, mefa.xml, query.xml, update.xml, validation.xml in NB6 project with corresponding files from 5.x project.
- edm.xml has changed considerably since there will be entirely new EDM. We are working on the details for upgrade.
- there are some new options in master.xml regarding XA, that should be taken into consideration when overwriting.
3. Ensure that Master Index source classes in these xml configuration files, uses new package prefix (com.sun.mdm.index) - So overwrite 5.x class prefix "com.stc.eindex" with "com.sun.mdm.index"
4. If there are any plugin classes in 5.x, move them over to $Project-ejb/source-packages. Ensure new Master Index class name prefix is used in these plugin classes.
5. Use Sun Application server JDBC connection pool configuration instead of Oracle/SQLserver eways. Connection pool configuration is same as in 5.1.3
6. Outbound Topic - In Sun Appserver, create a topic of naming convention <ObjectName>Topic. During run time, this will then publish outbound messages to this topic.
7. 5.x OTD methods (that are invoked from BPEL/JCD) - During Master Index project generation, An <ObjectName>EJB webservice is created during generate.
Use these methods in the old BPEL/JCD, if these need to be invoked in 5.x environment.
8. Matching - replace the matchconfigfile.cfg with 5.x matchconfigfile.cfg.
9. Standardization - If there is no modification in standardization stuff, then does not require any changes.
Otherwise more details will be spelled out.
10. Generate and deploy to Glassfish.
Additional Requirements:
1. Use MI wizard to create a new Master Index project that mirrors the old eView project, e.g "Person".
2. Copy old edm.xml contents to midm.xml, change 3 edm references to midm:
<edm xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="schema/EDM.xsd">
</edm>
<midm xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="schema/midm.xsd">
</midm>
3. Bring up MI Configuration Editor, make changes to force "Save" action. Conversion will occur in save action.
4. Check what are converted:
<node-xxxx> -> <node> <name>xxxx</name>
<field-xxxx> -> <field> <name>xxxx</name>
<dashboard> added
<eo-search> -> <record-details>
<create-eo> removed
<history> -> <transactions>
<matching-review> -> <duplicate-records> and <assumed-matches>
<source-record> added
<reports> -> <reports> //with sub screens
<audit-log> -> <audit-log> //with more atributes
For more details see http://developers.sun.com/docs/javacaps/upgrading/jcapsupgrd.jcapsupgrd.html
