Hi John, So you are looking to integrate a server at a corporate location (non DoD) to the Navy's network? That is most likely going to really limit your options. Any connections that you are going to make will have to be on a Navy approved port (unless you can get an exception or use a VPN). Web services may very well be a good option 1) because it is built into Remedy and 2) it can run on port 443 which is an approved port. ARSXML will also run on port 443 and is similar to DSO (some would say better than DSO) however with your budgetary limits this probably isn't an option (Navy pricing was 10-13k if I remember right).
Do you know if the Navy system you wanting to connect to is part of the Shared Data Environment (SDE)? If so they will already have a form setup with the common data elements and already be using DSO or ARSXML with other ARS servers in the Navy. I was working on a project where we implemented ITSM 6 for the Navy and integrated with DSO to their custom built Help Desk form on another server. Both systems had a copy of the DSO form and then we used DSO to keep our Help Desk forms synchronized with that form on the same server (this way field 1 kept the prefix for the site where it originated). Instead of completely reworking the ITSM Help Desk form to meet the Navy's specs (upgrade nightmare), we created fields on the Help Desk that received the DSO data and then filters that would correctly translate that data in to OOB Help Desk data (ex. priorities were reversed, custom Navy Status values to ITSM status, etc.). HTH, Jason On Tue, Jun 24, 2008 at 10:53 AM, Reiser, John J <[EMAIL PROTECTED]> wrote: > ** Roger, Rick and Robert, > > Thanks for the replies. > Yes it is vague. > Yes it will be a challenge. > Especially since the other system is a US Navy system and I am sure > security will be tight. > > Right now this is "pie-in-the-sky" but that never stopped them before;^> > > > Robert, I have a question about your DSO statement. I thought the idea > behind DSO was also to allow you to connect to a different form structure > and still pass relevant data. > We are purchasing DSO for another project and they use ITSM, we use our > home grown Helpdesk. We just need to pass Ticket ID's as reference data as > well as problem summary and user info. This was suggested to us by the > Developers on the ITSM site. > > Thanks, > > John J. Reiser > Software Development Analyst > Remedy Administrator/Developer > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - paraphrased by > me > > > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Rick Cook > *Sent:* Tuesday, June 24, 2008 11:31 AM > *To:* [email protected] > *Subject:* Re: Integrating with another company's ARSystem > > ** Excellent point about DSO. I think the key here is being able to > establish either a secure gateway between the two AR servers or a common > middle ground (which means server, forms, etc.). Since you have zero > dollars to spend on hardware, it looks like you should be investigating how > to tunnel from one AR server to the other in some way, like Robert said, > using some common data forms, assuming that the data is common enough to > make that possible. Do you know anything about the other AR System and it's > applications? If not, now would be a great time to start finding out, so > that you have the answers before anyone asks more questions and defines > unrealistic expectations for you. > > Or, you could bypass AR System altogether, and create SQL views into the > DBs, and view them from a web page or something. Like I said, until you are > given a better definition of what they want, it's really premature to design > the solution for it. > > From a business perspective, there are two tacks you can take: > 1) Tell them that "Yes, it's probably possible", then toss it back to them > for a better definition of what they want. > 2) Define the rules yourself by telling them the means by which this can > most likely be done, and then ask them to fit what they want into that. > > Rick > > On Tue, Jun 24, 2008 at 8:11 AM, Robert Molenda <[EMAIL PROTECTED]> > wrote: > >> ** I agree with Rick... Could be easy - could be next to impossible... >> >> DSO is OK provided that the systems are configured the same - same fields >> - same configuration data - same-same... >> >> Web Services is probably the best method to do "Ticket Passing" which is >> what I have to assume you are referring to between the two companies. Works >> fine over a secure vpn tunnel as well. Only issue is host-name-resolution... >> >> You must create a common "interface" that will be used on 'both sides' to >> send / receive the data and then custom workflow on each end to 'store the >> data' in the appropriate form + format + field definitions. >> >> More 'details' would be helpful - you could actually get away with not >> even transfering the tickets - however using web-services to create a remote >> view into the other system, etc. All depends upon the requirements. >> >> HTH >> >> Robert Molenda >> >> On Tue, Jun 24, 2008 at 7:50 AM, Rick Cook <[EMAIL PROTECTED]> wrote: >> >>> ** John, "integration" is, as you said, pretty vague. Perhaps once you >>> have a better idea of its scale and definition, we might be able to give >>> better answers. Could be anything from very simple to you-gotta-be-kidding. >>> >>> >>> >>> Rick >>> >>> >>> On Tue, Jun 24, 2008 at 7:40 AM, Reiser, John J <[EMAIL PROTECTED]> >>> wrote: >>> >>>> Hello Listers, >>>> >>>> Current configuration >>>> ARS 6.3 Patch 014 >>>> Midtier 6.3 Patch 021 >>>> MS SQL Server 2000 >>>> >>>> Upgrade path >>>> ARS 7.1 >>>> Midtier 7 >>>> MS SQL Server 2000 maybe higher >>>> >>>> I know this is a long shot but has anyone put together an integration >>>> between two different ARSystem servers in two different companies? >>>> I'm guessing the only real solution would be to use webservices. I don't >>>> have anymore details other than " we must be able to transfer >>>> information between systems. >>>> >>>> Oh, did I mention that we can only spend labor dollars to accomplish >>>> this? >>>> >>>> I am just getting a taste of webservices inside one company and haven't >>>> gotten too far. >>>> Are there any issues with webservice publishing/consuming through the >>>> security firewalls? >>>> >>>> Sorry to be so general and I understand that the basic answer is >>>> probably "yes". I need to get a rough order of magnitude for such a >>>> requirement. >>>> >>>> TIA, >>>> >>>> >>>> >>>> John J. Reiser >>>> Software Development Analyst >>>> Remedy Administrator/Developer >>>> Lockheed Martin - MS2 >>>> The star that burns twice as bright burns half as long. >>>> Pay close attention and be illuminated by its brilliance. - paraphrased >>>> by me >>>> >>>> >>>> >>>> _______________________________________________________________________________ >>>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >>>> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >>>> >>> >>> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >>> html___ >> >> >> >> >> -- >> If it were not for the gutter, my mind would be homeless! __Platinum >> Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ > > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
