SQL Server and Groupwise Integration Best answer on the web

Author: jack     07 13th, 2010 in xn--00t609f.com     edit

  • Where would I go to find step-by-step instructions on how to integrate Novell Groupwise into Microsoft SQL Server 2000? I want a two-way integration - if I add items in Groupwise, I want them to update into SQL Server, and if I add items in SQL Server, I want them to update into Groupwise.


  • Okay, all some good questions, but allow me to clarify a bit. There are three parties in this situation, me (Vendor A), the GroupWise vendor (Vendor B), and the client (Client C). Vendor A has written a SQL Server 2000 database. When Client logs into GroupWise (provided and supported by Vendor B), and adds an item into their calendar, we want to integrate that into the SQL database provided by Vendor A. Now, we can do almost anything in SQL, but the big holdup has been Vendor B - they seem to be most unhelpful. Vendor A has developed some solutions on our own, with success, but I'd still like to cast my net wide on this and make sure the Client has the best possible solution. So, I'm going to revise my question a little, and extend the deadline: Where would I go to find out specifics on GroupWise, specifically: In a default (as in out-of-the-box, basic) Groupwise installation, what are the file names of the data files, their location and structure of the files (SQL, DB, some other data file type), ODBC specifications (if any)? Thanks everyone!


  • The reason I don't post it as an answer is because I'm afraid you won't like it - but that's the answer (and I wouldn't mind getting $100 for explaining that to you ;-)
    Microsoft doing as much as they can to obstacle anyone who uses different calendars as theirs and this is no exception, especially considering the fact that Novell is a main competitor in these fields. Messing with the protocols is not advisable, unless you have a MS programmer.


  • Ack, I reversed that. Sorry. Basic functionality: Enter event in Groupwise, it goes out and updates SQL Server. Optional functionality: Enter event in SQL Server, and it goes out and updates Groupwise. Everything else is correct. Thanks!


  • Okay, here's some answers: Database A is in SQL Server 2000. Database B is in Groupwise. In the basic scenario, when you enter an event in Database A (SQL Server), it would go out and update Database B (Groupwise). This is the basic functionality that is required. Optionally, it would also be nice if you enter an event in Database B (the Groupwise calendar), it would go out and update Database A (SQL Server 2000). Both databases are set up already. The goal is to have them contain identical data at all times (or within a few seconds of each other, given network latency). Both products need to be maintained separately, using the SQL database for Groupwise is not an option now. The user will be responsible for choosing which application to update, and will not try to update both applications with the same event data.


  • In regards to fugitive-ga's comment, such a "bridge" could probably easily be created with PHP. I personally am familiar with PHP, Perl and ASP. I have never used Groupwise with an internet application, but I would assume you can interface with it online or than an intranet.
    I would just like to point out that you can easily find a high quality PHP programmer for even $20-$30/hr. This (assuming Groupwise works online) seems like it would be a relatively easy project.
    Just looking to back up fugitive and post my own two cents.
    xemion-ga


  • I've figured out how this would work, but need to ask a few more questions to get you the step by step instructions you are looking for. 1) Do you have or are you personally a programmer? 2) Which database information are you trying to update (emails, customer information, fax information, all?) 3) Can you post, some where, the schema for your SQL database? 4) If the SQL database was updated every hour, would that satisfy the demand or do you need the information live? What about every 15 mins? 5) Are the two machines connected via TCP/IP or are you using SMB or some other protocal to network these together. 6) Is the connection local or remote? 7) If step by step instructions are needed then I need to know where I'm stepping. Also these two programs are databases basically. They don't talk on their own, so you are going to have to implement a "glue" programming language, something that can talk to both. The reading I've done so far suggests there are a few answers for this. Perl is one, and some of the other scripts can work. But the bottom line here is that someone needs to code the bridge. Do you have that type of resource available? and would they be able to follow coding instructions if I post them here? Thanks for the question, it created some fun learning time.


  • Just chiming in with a possible direction to pursue.

    In general, what you need is not going to be an easy thing to answer without getting one's hands on the actual systems - there are just too many variables to consider. If I were faced with this issue, my general approach would be to look into writing a custom "bridge" application in something like PHP. I would choose PHP because a) I know it, and b) if it doesn't have a relevant API, given that PHP is open source means one could write one.
    Given that consultants charging $100-$200 per hour would be hard pressed to solve your problem on site in one hour ($100/hr figure = $100 to answer this question) if you DO get an answer that works consider yourself fortunate. I think it would be really cool that you would get an answer that works!


  • http://www.kroeker.net/published/infostructure/infostructure_1_5.pdf

    I realise that this is not an answer to your question, but wondered if this groupwise plug-in for Outlook solved your problem at all. It allows Outlook users to continue to access email, calendaring and collaboration functions of Groupwise.
    If it does I'll accept the $100 :-)


  • Could you provide a bit more detail on what data you would like to integrate? Are both systems already set up? Effectively, you want to maintain two seperate databases, and have them contain identical data at all times? If it were possible to force Groupwise to use SQL Server as it's database, would that be an acceptable solution? Or are there other factors that necessitate maintaining both products seperately, and simply having them communicate with each other? How precise does this need to be, is it possible that two of the same pieces of data will be changed at the same time on both systems, meaning they would try to update each other, and probably end up with the wrong data? As much information as you can give would be helpful.


  • This is a really hard answer to research. It's hard to search for specifically what you're looking for, if that makes sense. The keywords just don't work well. I have not been able to find an answer (I honestly doubt it's possible without writing a software program or website to manage the whole system).
    Hopefully someone here knows the answer or knows better how to obtain it than me. If not, I suggest you try contacting some database experts. Maybe authors of some books on SQL Server or Groupwise.
    Thanks for using Google Answers!

    xemion-ga









    • #If you have any other info about this subject , Please add it free.#
    Your name:
    E-mail:
    Telphone:

    Your comments:


    If you have any other info about SQL Server and Groupwise Integration , Please add it free.