View Single Post
  #2 (permalink)  
Old November 6th, 2007, 06:40
chrisplough's Avatar
chrisplough chrisplough is offline
Site Moderator
 
Join Date: Jun 2006
Location: West Chester, PA
Posts: 821
Blog Entries: 7
Thanks: 53
Thanked 200 Times in 121 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 10
chrisplough has a spectacular aura aboutchrisplough has a spectacular aura aboutchrisplough has a spectacular aura about
Send a message via AIM to chrisplough
Re: Options for integrating with a FAX server

Paul,

Currently OTM only supports integration with GFI FAXmaker and Captaris RightFax. Unfortunately, I'm not very familiar with FAXIS, but I have gotten OTM to integrate with home-grown and other fax servers. In order to do this, there are 2 options:

1) Configure OTM to integrate with FAXmaker, which will send specially-formatted email messages to a specified email box. Write a script to poll this email box and convert the emails into the format that FAXIS prefers. This has worked successfully several times in the past.

2) Another option is to utilize OTM's built-in FAX notification customizations via properties in the glog.properties file. This is covered in Chapter 5 of the OTM Administration Guide, under the heading FAX Generation in OTM.

------ Disclaimer: Oracle's Copyright, reproduced for informational purposes. ------
Quote:
Fax Generation in OTM
Fax generation is controlled via a plug-and-play interface, FaxHandler. Classes that implement this
interface support the following two methods:
public MailAddress getAddress();
// returns the mail address for fax generation
public void handle(MailEvent event, FaxTopic faxTopic);
// modifies our standard text e-mail to conform to outgoing fax
// specifications.
The fax handler is specified via the property glog.fax.handler=<fax handler class name>
OTM supplies a standard fax handler, glog.server.workflow.notify.DefaultFaxHandler, to support most
fax generation software. This handler embeds routing information into one of the following 3 mail
components:
• message body
• subject line
• to alias (i.e. the last name of the to party)
The embedding is accomplished with a picture string describing the modified format of the above
component. You can specify original information from the text email to use in the modified component
including:
• firstName
• lastName
• company
• phone
• rawPhone (punctuation or space)
• message
• subject
Replacements are represented by one of these identifiers surrounded by parenthesis; for example,
{firstName}. Newline characters are preserved. To transform an email message body to one
supporting FAXMaker, the picture string would be:
::{firstName},{company},{lastName},,{rawPhone}\n{m essage}
The following properties control the default fax handler:
glog.fax.defaultHandler.routingMode=<message|body| to> (default:
message)
glog.fax.defaultHandler.routingPicture=<picture string>
(default:
::{firstName},{company},{lastName},,{rawPhone}\n{m essage})
For RightFax, the properties default to:
glog.fax.defaultHandler.routingMode=to
glog.fax.defaultHandler.routingPicture=/name={lastName},
{firstName}/fax={rawPhone}/
glog.fax.email=fax@company.com
For FAXMaker, they default to:
glog.fax.defaultHandler.routingMode=message
glog.fax.defaultHandler.routingPicture=::{firstNam e},{company},{lastNam
e},, {rawPhone}\n{message}
glog.fax.email=fax@company.com
------ Disclaimer: Oracle's Copyright, reproduced for informational purposes. ------

Hope this helps!

--Chris
__________________
Chris Plough
MavenWire

www.MavenWire.com
Reply With Quote
The Following User Says Thank You to chrisplough For This Useful Post:
Paul Stevens (November 7th, 2007)