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. |
Request for Question Clarification by
passive-ga
on
29 May 2002 14:51 PDT
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.
|
Clarification of Question by
ebarker-ga
on
29 May 2002 15:54 PDT
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.
|
Clarification of Question by
ebarker-ga
on
29 May 2002 15:56 PDT
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!
|
Request for Question Clarification by
webadept-ga
on
30 May 2002 00:24 PDT
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.
|
Clarification of Question by
ebarker-ga
on
04 Jun 2002 06:53 PDT
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!
|
