Support 2

[Support 2]

Thanks for the additional background. The current Message Saver 2.0 applet does not work with the On Message Arrival event (received event). It may be possible for us to modify the solution to do so. The reason is that you must have a message selected before it will save it.

One work-around may be to write a another applet which:

• integrates with the On Message Arrival event
• selects the incoming message
• chains Message Saver

The only problem is that in a very busy client, the GroupWise event system may ‘lose’ events, thus potentially missing a message save. There are a number of approaches to help address this type of problem. One approach would be to mark/categorize a message once it is saved successfully, then run a process at some point to check that all messages are marked. If not, save the ones which were ‘missed’. This approach would require additional custom development of Message Saver 2.0 or ancillary applets.

quote:

---

In your product info for Message Saver Pack 2.0, under “Benefits” you mention:
“Import messages into GroupWise or other document management systems.”
Could you elaborate on this process and explain how Message Saver would be involved?

---

Message Saver is involved to the extent that in response to a user action, such as message selection and clicking the save button, it exports the GroupWise message(s) to one or more Advansys Portable Message disk files in a target output folder. This facilitates the import into external applications such as a DMS. As an example, you may define the default Message Saver output folder to be one which is periodically monitored by a DMS and imported automatically. In this simple example the DMS import would need to take care of metadata and profile generation.

In short, the current Message Saver solution alone will not achieve your objective. Apart from the Message Saver component, which would provide the most flexibility but more development on your part, there may be other approaches. We will discuss your latest post with the engineers to see what else can be done.

Regards,

Advansys Support

[Support 2]

At this stage Message Saver 2.0 cannot be integrated into a DMS beyond what is possible with the out-of-the-box features. However, the underlying technology which forms the basis of the product, the Advansys Message Saver Component for .NET, may be licensed by Advansys to approved customers.

The Message Saver Component is the core engine which accepts a GroupWise Message object and converts it to an Advansys Portable Message file (FML), which in turn can be displayed by the free Advansys Message Viewer. It can be used as a COM component from any COM compatible language, such as Formativ, Delphi, VB etc. or used as a native .NET assembly. As it is a developer component, it does provides core functionality and not the UI or file naming/management features which are written in the Message Saver 2.0 applet (which makes calls to the Message Saver component for .NET). This component must be licensed separately to other Advansys products on an organization-wide license basis.

quote:

---

2. Is Message Saver efficient in exporting individual messages from large inboxes (3000+)? I cannot easily test this on our test environment.

---

Not really sure how to answer this question. Efficiency and performance is relative. For the functionality it offers, we have made it as efficient as possible.

quote:

---

3. Would I be able to see a sample of the code by which Message Saver saves and converts messages to FML? Ideally we would like to program this functionality into a Formativ applet that runs on every incoming message.

---

We cannot provide Message Saver 2.0 code but if you think that you would like to explore the use of the Message Saver Component for .NET, we can provide a simple applet example which instantiates the component from Formativ. We have not tried implementing a solution which saves each incoming message (for a single user).

Regards,

Advansys Support

[Support 2]

We don’t think so but it would be best to check with Novell direct, the GroupWise documentation or the GroupWise Newsgroups.

I think from a token blocking perspective you can only prevent the Options dialog from appearing, which is usually not a practical option.

Regards,

Advansys Support

[Support 2]

No, there is not a function to print message notes. Apart from writing a specific solution, copying and pasting is the only way at this stage.

Regards,

Advansys Support

[Support 2]

Thanks for the feedback and glad to hear that it was of assistance.

Regards,

Advansys Support

[Support 2]

Thanks for the update and good news.

The ‘fix’ is interesting and not obvious from the symptoms you described. It’s good to have documented field experience for future reference.

Regards,

Advansys Support

[Support 2]

Yes it should be possible using ADO with the appropriate connection string. A simple example where SQL is used against a Microsoft Access database can be found on Formativ Applet Central:

12 Mar 2003 – SQL Example
This applet uses SQL to find records in a sample database and displays the results in a Formativ portal. Click here to download.

There are some other examples of using SQL with ADO in our BrainShare developer examples, available from our Formativ Resources page.

BrainShare 2005 Session TUT333 Developer Examples

BrainShare 2004 Session DHO340 Developer Examples

I hope this helps.

Regards,

Advansys Support

[Support 2]

As the problem is user specific, it may be either GroupWise account or workstation related (or both). If the problem occurs with the same account from different workstations, it is very likely to be account specific.

While we have not seen the error you mention, it can be corrupted data, which is why the first dialog recommends the GWCheck process. However, GWCheck may not always resolve the issue but is certainly the first step. Perhaps the stand-alone version of GWCheck should be tried also.

Are you using Enterprise or Local modes for the export? Does the problem occur in both modes?

What version of GroupWise are you using?

I would probably recommend that you try with Archive To Go 1.1, which includes some enhanced logging.

If you can reproduce the problem, can you email the log to support@advansyscorp.com for review.

Regards,

Advansys Support

[Support 2]

Thanks for the update. Archive To Go 1.1 should solve the viewer.exe problem.

If the Microsoft .NET Framework is not installed, you will not be able to use the Archive To Go Finder (i.e. Search button) or the Archive To Go Indexer.

With respect to obtaining the full version of 1.1, we have just sent the information to customers for whom we have contact details. From my initial review, it appears that we don’t have contact information on file for your organization. Please contact your reseller, who will in turn contact us, or write directly to sales@advansyscorp.com and we will email the access details.

Regards,

Advansys Support

[Support 2]

You are correct in your understanding that the Archive To Go Viewer should run without the need for the Microsoft .NET Framework being installed on the target machine.

Which version of Archive To Go are you using?

Viewer.exe is a stub program which does some initial environment checking and then launches a2goview.exe, the Archive To Go Viewer application.

Instead of using viewer.exe, can you run the Archive To Go Viewer application directly by running the a2goview.exe program file located in the portable archive’s ..media-01_viewer folder?

Regards,

Advansys Support

[Support 2]

Great news and thanks for posting the update.

Regards,

Advansys Support

[Support 2]

Unfortunately we don’t have any suggestions at this point. As this has not been seen (yet?) by Advansys nor other customers using the API, we will probably need to be able to replicate the problem before we can understand what may be happening.

The intermittent nature of the problem suggests an issue which is sensitive to the environmental state, which may make it difficult to replicate, particularly as there are multiple applications involved.

We will get back to you when we have had an opportunity to consider the best plan of action.

Regards,

Advansys Support

[Support 2]

Are you using the latest download of the Personalized Emailer?

Can you advise us of the Personlized Emailer applet version listed in the Applets tab of the Formativ About dialog?

Regards,

Advansys Support

[Support 2]

Unfortunately we don’t know why the Novell files would fail to register in your environment. Perhaps the next step would be to try the Novell support newsgroups for some ideas.

Regards,

Advansys Support

[Support 2]

As we are not aware of any network specific issues apart from the known .NET security requirements, we cannot yet offer an explanation for the error.

Can you provide us with the full path, including any drive mapping, UNC details etc., to the a2gofinder.exe file?

If for some reason you would prefer not to post it to the forum, please send it direct to support@advansyscorp.com.

Regards,

Advansys Support

[Author]

Replies