Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
3500:0600 [2026/08/13 00:55] – ↷ Page moved from docs:3500:0600 to 3500:0600 localdev3500:0600 [2026/08/13 01:10] (current) – external edit 127.0.0.1
Line 9: Line 9:
 To add a new document type to //**AwareIM**// follow the steps below: To add a new document type to //**AwareIM**// follow the steps below:
  
-  - Write the code for the component that will work with documents of the new type on the client side (see [[docs:3500:0600:0610]] for details). +  - Write the code for the component that will work with documents of the new type on the client side (see [[3500:0600:0610]] for details). 
-  - Write the code for the component that will work with documents of the new type on the server side (see [[docs:3500:0600:0620]] for details).+  - Write the code for the component that will work with documents of the new type on the server side (see [[3500:0600:0620]] for details).
   - Compile the source code of your components and package them in a jar file(s). Make sure that the jar file resides in the ''AwareIM/CustomJars'' directory (see section 2).   - Compile the source code of your components and package them in a jar file(s). Make sure that the jar file resides in the ''AwareIM/CustomJars'' directory (see section 2).
   - Add the definition of a new document type to the ''BASServer.props'' file located in the ''BIN'' directory of your //**AwareIM**// installation. You have to modify the line that sets the ''DocumentEngines'' property to add the fully qualified name of your server side component.  For example (note text ''com.mypackage.MyServerDocEngine''):<code>   - Add the definition of a new document type to the ''BASServer.props'' file located in the ''BIN'' directory of your //**AwareIM**// installation. You have to modify the line that sets the ''DocumentEngines'' property to add the fully qualified name of your server side component.  For example (note text ''com.mypackage.MyServerDocEngine''):<code>
 DocumentEngines=com.bas.basserver.documents.JasperReportsEngine,com.bas.basserver.documents.MSWordDocumentEngine,com.bas.basserver.documents.TextDocumentEngine,com.bas.basserver.documents.HtmlDocumentEngine,com.bas.basserver.documents.MSExcelDocumentEngine,com.mypackage.MyServerDocEngine</code> DocumentEngines=com.bas.basserver.documents.JasperReportsEngine,com.bas.basserver.documents.MSWordDocumentEngine,com.bas.basserver.documents.TextDocumentEngine,com.bas.basserver.documents.HtmlDocumentEngine,com.bas.basserver.documents.MSExcelDocumentEngine,com.mypackage.MyServerDocEngine</code>
  
-Note that you have to make sure that the jar file with your server side component as well as the modifications to ''BASServer.props'' file are available to the Aware server that hosts your application (see [[docs:1100_inst_guide|AwareIM Installation Guide]] for details).+Note that you have to make sure that the jar file with your server side component as well as the modifications to ''BASServer.props'' file are available to the Aware server that hosts your application (see [[:1100_inst_guide|AwareIM Installation Guide]] for details).
  
-If everything has been done correctly the new document type must appear in the list of document types displayed by the Document Template Property Editor (see [[docs:2500_config_apps:1300_add_edit_doctemp|Adding/Editing Document Templates]]).+If everything has been done correctly the new document type must appear in the list of document types displayed by the Document Template Property Editor (see [[2500_config_apps:1300_add_edit_doctemp|Adding/Editing Document Templates]]).
  
-{{simplenavi>:docs:3500:0600:}}+{{simplenavi>.:0600}}