Re: Alternatives to DSO for Data Transfer
> BMC said that it will likely offer this level in future releases (not sure if v7 is there yet or not). Not in 7.1.00, but use of FIPS-certified encryption modules within the Encryption products is tentatively targeted for the mid-2008 release. Thanks, -David J. Easter Sr. Product Manager, Service Management Business Unit BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lockemy (Serco North America) Sent: Thursday, October 18, 2007 8:29 AM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer Hi Axton, Thank you for the feedback... We looked into Remedy Encryption, but it didn't offer a FIPS compliant encryption algorithm, so it was not compliant with my customer's security requirements. BMC said that it will likely offer this level in future releases (not sure if v7 is there yet or not). Kind regards, Jeff -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Tuesday, October 02, 2007 7:48 PM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer STunnel can encrypt any tcp traffic between two machines on a given port. Just bear in mind that this is a method of transport relies on a sort of local proxy manages sessions between both end points. IPSec is another alternative; it operates at a lower level of the OSI model and will give you some added benefits depending on your security paradigm. Another alternative would be to look into the Remedy encryption products. This would in essence do the same thing as STunnel, but instead of relying on a separate process, it would be native to the arserver (a plugin or library if you will). There is also a base level of encryption that is included in the product. see http://arswiki.org/wiki/Securing_ARS#Remedy_Encryption_Products Axton Grams On 10/2/07, Jeff Lockemy (Serco North America) <[EMAIL PROTECTED]> wrote: > Thank you everyone for the suggestions. The easiest option for us > would be > doing data transfers over https/443, that's why we mentioned web services. > > > > However, a colleague of mine mentioned that they investigated using Stunnel > (www.stunnel.org), a universal SSL wrapper, to encrypt their DSO > communications between servers over 443. I am looking into it, and > will let > you know how it goes. If anyone else has done anything else with 443, > please let me know. > > > > Cheers, > > Jeff > > > > > > _ > > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lockemy (Serco North America) > Sent: Friday, September 28, 2007 4:27 PM > To: arslist@ARSLIST.ORG > Subject: Alternatives to DSO for Data Transfer > > ** > > Hello Listers, > > > > I am trying to find out what solutions are out there that folks might > be using as an alternate to DSO, to transfer Remedy tickets between > Remedy servers. > > > > My customer cannot use DSO due to port and encryption level restrictions. > Currently, we are using a solution provided to us by another group. > This solution uses IBM WebSphere MQ and a product called ARSXML (not > be to confused with ARXML, ARSXML is a product by N-Tuition, a Remedy > partner out > of Germany). This solution has some design pitfalls (on the ARSXML > side) that are proving to be a challenge to overcome. So we want to > see what other options out there might exist. > > > > One thought that was brought up several years back with this customer > was to > design and build a solution on Remedy Web Services, transferring > tickets through SOAP, Mid-Tier to Mid-Tier. I believe they had a > design prototype back then, but I was not involved in it, nor does anything exist of it. Has > anyone done this, or some other solution that they could share? > > > > Any ideas or input anyone has is much appreciated... > > > > Regards, > Jeff > > > > > > > > > > > > Jeff Lockemy > > Remedy Skilled Professional > > Serco North America > > (619) 524-2303 > > [EMAIL PROTECTED] > > > > > > > > > > > > __20060125___This posting was submitted with HTML > in it___ > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.ars
Re: Alternatives to DSO for Data Transfer
Hi Axton, Thank you for the feedback... We looked into Remedy Encryption, but it didn't offer a FIPS compliant encryption algorithm, so it was not compliant with my customer's security requirements. BMC said that it will likely offer this level in future releases (not sure if v7 is there yet or not). Kind regards, Jeff -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Tuesday, October 02, 2007 7:48 PM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer STunnel can encrypt any tcp traffic between two machines on a given port. Just bear in mind that this is a method of transport relies on a sort of local proxy manages sessions between both end points. IPSec is another alternative; it operates at a lower level of the OSI model and will give you some added benefits depending on your security paradigm. Another alternative would be to look into the Remedy encryption products. This would in essence do the same thing as STunnel, but instead of relying on a separate process, it would be native to the arserver (a plugin or library if you will). There is also a base level of encryption that is included in the product. see http://arswiki.org/wiki/Securing_ARS#Remedy_Encryption_Products Axton Grams On 10/2/07, Jeff Lockemy (Serco North America) <[EMAIL PROTECTED]> wrote: > Thank you everyone for the suggestions. The easiest option for us would be > doing data transfers over https/443, that's why we mentioned web services. > > > > However, a colleague of mine mentioned that they investigated using Stunnel > (www.stunnel.org), a universal SSL wrapper, to encrypt their DSO > communications between servers over 443. I am looking into it, and will let > you know how it goes. If anyone else has done anything else with 443, > please let me know. > > > > Cheers, > > Jeff > > > > > > _ > > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lockemy (Serco North America) > Sent: Friday, September 28, 2007 4:27 PM > To: arslist@ARSLIST.ORG > Subject: Alternatives to DSO for Data Transfer > > ** > > Hello Listers, > > > > I am trying to find out what solutions are out there that folks might be > using as an alternate to DSO, to transfer Remedy tickets between Remedy > servers. > > > > My customer cannot use DSO due to port and encryption level restrictions. > Currently, we are using a solution provided to us by another group. This > solution uses IBM WebSphere MQ and a product called ARSXML (not be to > confused with ARXML, ARSXML is a product by N-Tuition, a Remedy partner out > of Germany). This solution has some design pitfalls (on the ARSXML side) > that are proving to be a challenge to overcome. So we want to see what > other options out there might exist. > > > > One thought that was brought up several years back with this customer was to > design and build a solution on Remedy Web Services, transferring tickets > through SOAP, Mid-Tier to Mid-Tier. I believe they had a design prototype > back then, but I was not involved in it, nor does anything exist of it. Has > anyone done this, or some other solution that they could share? > > > > Any ideas or input anyone has is much appreciated... > > > > Regards, > Jeff > > > > > > > > > > > > Jeff Lockemy > > Remedy Skilled Professional > > Serco North America > > (619) 524-2303 > > [EMAIL PROTECTED] > > > > > > > > > > > > __20060125___This posting was submitted with HTML in > it___ > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Alternatives to DSO for Data Transfer
STunnel can encrypt any tcp traffic between two machines on a given port. Just bear in mind that this is a method of transport relies on a sort of local proxy manages sessions between both end points. IPSec is another alternative; it operates at a lower level of the OSI model and will give you some added benefits depending on your security paradigm. Another alternative would be to look into the Remedy encryption products. This would in essence do the same thing as STunnel, but instead of relying on a separate process, it would be native to the arserver (a plugin or library if you will). There is also a base level of encryption that is included in the product. see http://arswiki.org/wiki/Securing_ARS#Remedy_Encryption_Products Axton Grams On 10/2/07, Jeff Lockemy (Serco North America) <[EMAIL PROTECTED]> wrote: > Thank you everyone for the suggestions. The easiest option for us would be > doing data transfers over https/443, that's why we mentioned web services. > > > > However, a colleague of mine mentioned that they investigated using Stunnel > (www.stunnel.org), a universal SSL wrapper, to encrypt their DSO > communications between servers over 443. I am looking into it, and will let > you know how it goes. If anyone else has done anything else with 443, > please let me know. > > > > Cheers, > > Jeff > > > > > > _ > > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lockemy (Serco North America) > Sent: Friday, September 28, 2007 4:27 PM > To: arslist@ARSLIST.ORG > Subject: Alternatives to DSO for Data Transfer > > ** > > Hello Listers, > > > > I am trying to find out what solutions are out there that folks might be > using as an alternate to DSO, to transfer Remedy tickets between Remedy > servers. > > > > My customer cannot use DSO due to port and encryption level restrictions. > Currently, we are using a solution provided to us by another group. This > solution uses IBM WebSphere MQ and a product called ARSXML (not be to > confused with ARXML, ARSXML is a product by N-Tuition, a Remedy partner out > of Germany). This solution has some design pitfalls (on the ARSXML side) > that are proving to be a challenge to overcome. So we want to see what > other options out there might exist. > > > > One thought that was brought up several years back with this customer was to > design and build a solution on Remedy Web Services, transferring tickets > through SOAP, Mid-Tier to Mid-Tier. I believe they had a design prototype > back then, but I was not involved in it, nor does anything exist of it. Has > anyone done this, or some other solution that they could share? > > > > Any ideas or input anyone has is much appreciated... > > > > Regards, > Jeff > > > > > > > > > > > > Jeff Lockemy > > Remedy Skilled Professional > > Serco North America > > (619) 524-2303 > > [EMAIL PROTECTED] > > > > > > > > > > > > __20060125___This posting was submitted with HTML in > it___ > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Alternatives to DSO for Data Transfer
Thank you everyone for the suggestions. The easiest option for us would be doing data transfers over https/443, that's why we mentioned web services. However, a colleague of mine mentioned that they investigated using Stunnel (www.stunnel.org), a universal SSL wrapper, to encrypt their DSO communications between servers over 443. I am looking into it, and will let you know how it goes. If anyone else has done anything else with 443, please let me know. Cheers, Jeff _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lockemy (Serco North America) Sent: Friday, September 28, 2007 4:27 PM To: arslist@ARSLIST.ORG Subject: Alternatives to DSO for Data Transfer ** Hello Listers, I am trying to find out what solutions are out there that folks might be using as an alternate to DSO, to transfer Remedy tickets between Remedy servers. My customer cannot use DSO due to port and encryption level restrictions. Currently, we are using a solution provided to us by another group. This solution uses IBM WebSphere MQ and a product called ARSXML (not be to confused with ARXML, ARSXML is a product by N-Tuition, a Remedy partner out of Germany). This solution has some design pitfalls (on the ARSXML side) that are proving to be a challenge to overcome. So we want to see what other options out there might exist. One thought that was brought up several years back with this customer was to design and build a solution on Remedy Web Services, transferring tickets through SOAP, Mid-Tier to Mid-Tier. I believe they had a design prototype back then, but I was not involved in it, nor does anything exist of it. Has anyone done this, or some other solution that they could share? Any ideas or input anyone has is much appreciated... Regards, Jeff Jeff Lockemy Remedy Skilled Professional Serco North America (619) 524-2303 [EMAIL PROTECTED] __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Alternatives to DSO for Data Transfer
Ok, I'm very interested in how to setup replication say, from T215 on oracle 10gR2 to a secondary database. Is it simply SQL that copies the data or are you using Transactional Replication? Thanks, -Geoff On 10/1/07, Nall, Roger <[EMAIL PROTECTED]> wrote: > > It has worked very well for us. Not being a dba the biggest challenge I > can remember is declaring a primary key for each Remedy table. While we > all know that C1 is the primary key is not really declared at the db > level. This has to be done manually. > > From a Remedy stand point you need to remember have replication stopped > before making any changes that would alter the table. You would then > need to re-initialize the process when you are finished. There is also a > limit to the number of columns in a table you can replicate, 255. I > believe there is also a data limit per record. This can come into with > Diary fields when users start pasting garbage in the work log. > > I will send this to my dba to see if he comes up with anything I forgot. > > HTH. > > Roger A. Nall > Manager, OSSNMS Remedy > T-Mobile USA > Desk: 813-348-2556 > Cell: 973-652-6723 > FAX: 813-348-2565 > sf49fanv AIM IM > RogerNall Yahoo IM > > > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Hall Chad - chahal > Sent: Monday, October 01, 2007 3:02 PM > To: arslist@ARSLIST.ORG > Subject: Re: Alternatives to DSO for Data Transfer > > Roger, > That's very interesting. I had been told by support in the past that > Remedy would not work correctly with replication but that they would > support it in a 7.x release. I'd be interested in how you've implemented > it, how well it works for you, and what you've learned along the way. > > Thanks, > > Chad Hall > (501) 342-2650 > > > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger > Sent: Monday, October 01, 2007 12:10 PM > To: arslist@ARSLIST.ORG > Subject: Re: Alternatives to DSO for Data Transfer > > If you are using SQL Server you are not dependent on the Remedy version > to institute transactional replication. We have been using this since > ARS 4.5. > > Thanks, > > Roger A. Nall > Manager, OSSNMS Remedy > T-Mobile USA > Desk: 813-348-2556 > Cell: 973-652-6723 > FAX: 813-348-2565 > sf49fanv AIM IM > RogerNall Yahoo IM > > -----Original Message- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Hall Chad - chahal > Sent: Friday, September 28, 2007 8:57 PM > To: arslist@ARSLIST.ORG > Subject: Re: Alternatives to DSO for Data Transfer > > What backend database are you running? And what version of ARS? > > I've been told that either 7.0.1 or 7.1 (can't remember which) will > support transactional replication. So for example you could setup SQL > Server replication on the tables you want to keep in sync. I plan to do > this for our separate reporting server some day. That may not fit your > needs if you only want some transferred and not all. But it should be > more efficient and reliable than DSO if you simply need to copy all > ticket data. > > Web services might work well for you. Although I would worry about how > it would handle high volumes. I haven't been down that road with > Remedy's web services but I've seen others that simply weren't a good > fit for high volume interfaces. > > Chad Hall > 501-342-2650 > > > > From: Action Request System discussion list(ARSList) on behalf of Jeff > Lockemy (Serco North America) > Sent: Fri 9/28/2007 6:27 PM > To: arslist@ARSLIST.ORG > Subject: Alternatives to DSO for Data Transfer > > > ** > > Hello Listers, > > > > I am trying to find out what solutions are out there that folks might be > using as an alternate to DSO, to transfer Remedy tickets between Remedy > servers. > > > > My customer cannot use DSO due to port and encryption level > restrictions. Currently, we are using a solution provided to us by > another group. This solution uses IBM WebSphere MQ and a product called > ARSXML (not be to confused with ARXML, ARSXML is a product by N-Tuition, > a Remedy partner out of Germany). This solution has some design > pitfalls (on the ARSXML side) that are proving to be a challenge to > overcome. So we want to see what other options out there might exist. > > > > One thought that was brought up several years back with this customer > was to design and build a solution on Remedy Web Services, tr
Re: Alternatives to DSO for Data Transfer
It has worked very well for us. Not being a dba the biggest challenge I can remember is declaring a primary key for each Remedy table. While we all know that C1 is the primary key is not really declared at the db level. This has to be done manually. >From a Remedy stand point you need to remember have replication stopped before making any changes that would alter the table. You would then need to re-initialize the process when you are finished. There is also a limit to the number of columns in a table you can replicate, 255. I believe there is also a data limit per record. This can come into with Diary fields when users start pasting garbage in the work log. I will send this to my dba to see if he comes up with anything I forgot. HTH. Roger A. Nall Manager, OSSNMS Remedy T-Mobile USA Desk: 813-348-2556 Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Hall Chad - chahal Sent: Monday, October 01, 2007 3:02 PM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer Roger, That's very interesting. I had been told by support in the past that Remedy would not work correctly with replication but that they would support it in a 7.x release. I'd be interested in how you've implemented it, how well it works for you, and what you've learned along the way. Thanks, Chad Hall (501) 342-2650 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger Sent: Monday, October 01, 2007 12:10 PM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer If you are using SQL Server you are not dependent on the Remedy version to institute transactional replication. We have been using this since ARS 4.5. Thanks, Roger A. Nall Manager, OSSNMS Remedy T-Mobile USA Desk: 813-348-2556 Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Hall Chad - chahal Sent: Friday, September 28, 2007 8:57 PM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer What backend database are you running? And what version of ARS? I've been told that either 7.0.1 or 7.1 (can't remember which) will support transactional replication. So for example you could setup SQL Server replication on the tables you want to keep in sync. I plan to do this for our separate reporting server some day. That may not fit your needs if you only want some transferred and not all. But it should be more efficient and reliable than DSO if you simply need to copy all ticket data. Web services might work well for you. Although I would worry about how it would handle high volumes. I haven't been down that road with Remedy's web services but I've seen others that simply weren't a good fit for high volume interfaces. Chad Hall 501-342-2650 From: Action Request System discussion list(ARSList) on behalf of Jeff Lockemy (Serco North America) Sent: Fri 9/28/2007 6:27 PM To: arslist@ARSLIST.ORG Subject: Alternatives to DSO for Data Transfer ** Hello Listers, I am trying to find out what solutions are out there that folks might be using as an alternate to DSO, to transfer Remedy tickets between Remedy servers. My customer cannot use DSO due to port and encryption level restrictions. Currently, we are using a solution provided to us by another group. This solution uses IBM WebSphere MQ and a product called ARSXML (not be to confused with ARXML, ARSXML is a product by N-Tuition, a Remedy partner out of Germany). This solution has some design pitfalls (on the ARSXML side) that are proving to be a challenge to overcome. So we want to see what other options out there might exist. One thought that was brought up several years back with this customer was to design and build a solution on Remedy Web Services, transferring tickets through SOAP, Mid-Tier to Mid-Tier. I believe they had a design prototype back then, but I was not involved in it, nor does anything exist of it. Has anyone done this, or some other solution that they could share? Any ideas or input anyone has is much appreciated... Regards, Jeff Jeff Lockemy Remedy Skilled Professional Serco North America (619) 524-2303 [EMAIL PROTECTED] __20060125___This posting was submitted with HTML in it___ * The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any disseminat
Re: Alternatives to DSO for Data Transfer
Roger, That's very interesting. I had been told by support in the past that Remedy would not work correctly with replication but that they would support it in a 7.x release. I'd be interested in how you've implemented it, how well it works for you, and what you've learned along the way. Thanks, Chad Hall (501) 342-2650 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger Sent: Monday, October 01, 2007 12:10 PM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer If you are using SQL Server you are not dependent on the Remedy version to institute transactional replication. We have been using this since ARS 4.5. Thanks, Roger A. Nall Manager, OSSNMS Remedy T-Mobile USA Desk: 813-348-2556 Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Hall Chad - chahal Sent: Friday, September 28, 2007 8:57 PM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer What backend database are you running? And what version of ARS? I've been told that either 7.0.1 or 7.1 (can't remember which) will support transactional replication. So for example you could setup SQL Server replication on the tables you want to keep in sync. I plan to do this for our separate reporting server some day. That may not fit your needs if you only want some transferred and not all. But it should be more efficient and reliable than DSO if you simply need to copy all ticket data. Web services might work well for you. Although I would worry about how it would handle high volumes. I haven't been down that road with Remedy's web services but I've seen others that simply weren't a good fit for high volume interfaces. Chad Hall 501-342-2650 From: Action Request System discussion list(ARSList) on behalf of Jeff Lockemy (Serco North America) Sent: Fri 9/28/2007 6:27 PM To: arslist@ARSLIST.ORG Subject: Alternatives to DSO for Data Transfer ** Hello Listers, I am trying to find out what solutions are out there that folks might be using as an alternate to DSO, to transfer Remedy tickets between Remedy servers. My customer cannot use DSO due to port and encryption level restrictions. Currently, we are using a solution provided to us by another group. This solution uses IBM WebSphere MQ and a product called ARSXML (not be to confused with ARXML, ARSXML is a product by N-Tuition, a Remedy partner out of Germany). This solution has some design pitfalls (on the ARSXML side) that are proving to be a challenge to overcome. So we want to see what other options out there might exist. One thought that was brought up several years back with this customer was to design and build a solution on Remedy Web Services, transferring tickets through SOAP, Mid-Tier to Mid-Tier. I believe they had a design prototype back then, but I was not involved in it, nor does anything exist of it. Has anyone done this, or some other solution that they could share? Any ideas or input anyone has is much appreciated... Regards, Jeff Jeff Lockemy Remedy Skilled Professional Serco North America (619) 524-2303 [EMAIL PROTECTED] __20060125___This posting was submitted with HTML in it___ * The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank you. * ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Alternatives to DSO for Data Transfer
If you are using SQL Server you are not dependent on the Remedy version to institute transactional replication. We have been using this since ARS 4.5. Thanks, Roger A. Nall Manager, OSSNMS Remedy T-Mobile USA Desk: 813-348-2556 Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Hall Chad - chahal Sent: Friday, September 28, 2007 8:57 PM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer What backend database are you running? And what version of ARS? I've been told that either 7.0.1 or 7.1 (can't remember which) will support transactional replication. So for example you could setup SQL Server replication on the tables you want to keep in sync. I plan to do this for our separate reporting server some day. That may not fit your needs if you only want some transferred and not all. But it should be more efficient and reliable than DSO if you simply need to copy all ticket data. Web services might work well for you. Although I would worry about how it would handle high volumes. I haven't been down that road with Remedy's web services but I've seen others that simply weren't a good fit for high volume interfaces. Chad Hall 501-342-2650 From: Action Request System discussion list(ARSList) on behalf of Jeff Lockemy (Serco North America) Sent: Fri 9/28/2007 6:27 PM To: arslist@ARSLIST.ORG Subject: Alternatives to DSO for Data Transfer ** Hello Listers, I am trying to find out what solutions are out there that folks might be using as an alternate to DSO, to transfer Remedy tickets between Remedy servers. My customer cannot use DSO due to port and encryption level restrictions. Currently, we are using a solution provided to us by another group. This solution uses IBM WebSphere MQ and a product called ARSXML (not be to confused with ARXML, ARSXML is a product by N-Tuition, a Remedy partner out of Germany). This solution has some design pitfalls (on the ARSXML side) that are proving to be a challenge to overcome. So we want to see what other options out there might exist. One thought that was brought up several years back with this customer was to design and build a solution on Remedy Web Services, transferring tickets through SOAP, Mid-Tier to Mid-Tier. I believe they had a design prototype back then, but I was not involved in it, nor does anything exist of it. Has anyone done this, or some other solution that they could share? Any ideas or input anyone has is much appreciated... Regards, Jeff Jeff Lockemy Remedy Skilled Professional Serco North America (619) 524-2303 [EMAIL PROTECTED] __20060125___This posting was submitted with HTML in it___ * The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank you. * ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Alternatives to DSO for Data Transfer
Hi Chad, We are running SQL Server 2000 with ARS 6.3. However, my customer just got ARS 7 approved, so we will be planning an upgrade to SQL Server 2005 with ARS 7.1. Not sure what the timing will be at this point for that upgrade. Thank you for the suggestion. My customer is a government/defense entity with strong restrictions for WAN communications. Getting approval for replication at the data tier across the WAN would be a challenge, but might be possible. To be compliant, we would have to do things like: 1. Put restrictions on the firewall to open the SQL port only between the trusted server IP addresses 2. Use a FIPS compliant type and level of encryption 3. Do server PKI certificate trusts at both ends 4. Use application authentication Not sure if SQL Server replication would support things like these, but it is worth looking into. Kind regards, Jeff -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Hall Chad - chahal Sent: Friday, September 28, 2007 5:57 PM To: arslist@ARSLIST.ORG Subject: Re: Alternatives to DSO for Data Transfer What backend database are you running? And what version of ARS? I've been told that either 7.0.1 or 7.1 (can't remember which) will support transactional replication. So for example you could setup SQL Server replication on the tables you want to keep in sync. I plan to do this for our separate reporting server some day. That may not fit your needs if you only want some transferred and not all. But it should be more efficient and reliable than DSO if you simply need to copy all ticket data. Web services might work well for you. Although I would worry about how it would handle high volumes. I haven't been down that road with Remedy's web services but I've seen others that simply weren't a good fit for high volume interfaces. Chad Hall 501-342-2650 From: Action Request System discussion list(ARSList) on behalf of Jeff Lockemy (Serco North America) Sent: Fri 9/28/2007 6:27 PM To: arslist@ARSLIST.ORG Subject: Alternatives to DSO for Data Transfer ** Hello Listers, I am trying to find out what solutions are out there that folks might be using as an alternate to DSO, to transfer Remedy tickets between Remedy servers. My customer cannot use DSO due to port and encryption level restrictions. Currently, we are using a solution provided to us by another group. This solution uses IBM WebSphere MQ and a product called ARSXML (not be to confused with ARXML, ARSXML is a product by N-Tuition, a Remedy partner out of Germany). This solution has some design pitfalls (on the ARSXML side) that are proving to be a challenge to overcome. So we want to see what other options out there might exist. One thought that was brought up several years back with this customer was to design and build a solution on Remedy Web Services, transferring tickets through SOAP, Mid-Tier to Mid-Tier. I believe they had a design prototype back then, but I was not involved in it, nor does anything exist of it. Has anyone done this, or some other solution that they could share? Any ideas or input anyone has is much appreciated... Regards, Jeff Jeff Lockemy Remedy Skilled Professional Serco North America (619) 524-2303 [EMAIL PROTECTED] __20060125___This posting was submitted with HTML in it___ * The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank you. * ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Alternatives to DSO for Data Transfer
What backend database are you running? And what version of ARS? I've been told that either 7.0.1 or 7.1 (can't remember which) will support transactional replication. So for example you could setup SQL Server replication on the tables you want to keep in sync. I plan to do this for our separate reporting server some day. That may not fit your needs if you only want some transferred and not all. But it should be more efficient and reliable than DSO if you simply need to copy all ticket data. Web services might work well for you. Although I would worry about how it would handle high volumes. I haven't been down that road with Remedy's web services but I've seen others that simply weren't a good fit for high volume interfaces. Chad Hall 501-342-2650 From: Action Request System discussion list(ARSList) on behalf of Jeff Lockemy (Serco North America) Sent: Fri 9/28/2007 6:27 PM To: arslist@ARSLIST.ORG Subject: Alternatives to DSO for Data Transfer ** Hello Listers, I am trying to find out what solutions are out there that folks might be using as an alternate to DSO, to transfer Remedy tickets between Remedy servers. My customer cannot use DSO due to port and encryption level restrictions. Currently, we are using a solution provided to us by another group. This solution uses IBM WebSphere MQ and a product called ARSXML (not be to confused with ARXML, ARSXML is a product by N-Tuition, a Remedy partner out of Germany). This solution has some design pitfalls (on the ARSXML side) that are proving to be a challenge to overcome. So we want to see what other options out there might exist. One thought that was brought up several years back with this customer was to design and build a solution on Remedy Web Services, transferring tickets through SOAP, Mid-Tier to Mid-Tier. I believe they had a design prototype back then, but I was not involved in it, nor does anything exist of it. Has anyone done this, or some other solution that they could share? Any ideas or input anyone has is much appreciated... Regards, Jeff Jeff Lockemy Remedy Skilled Professional Serco North America (619) 524-2303 [EMAIL PROTECTED] __20060125___This posting was submitted with HTML in it___ * The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank you. * ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Alternatives to DSO for Data Transfer
Hello Listers, I am trying to find out what solutions are out there that folks might be using as an alternate to DSO, to transfer Remedy tickets between Remedy servers. My customer cannot use DSO due to port and encryption level restrictions. Currently, we are using a solution provided to us by another group. This solution uses IBM WebSphere MQ and a product called ARSXML (not be to confused with ARXML, ARSXML is a product by N-Tuition, a Remedy partner out of Germany). This solution has some design pitfalls (on the ARSXML side) that are proving to be a challenge to overcome. So we want to see what other options out there might exist. One thought that was brought up several years back with this customer was to design and build a solution on Remedy Web Services, transferring tickets through SOAP, Mid-Tier to Mid-Tier. I believe they had a design prototype back then, but I was not involved in it, nor does anything exist of it. Has anyone done this, or some other solution that they could share? Any ideas or input anyone has is much appreciated. Regards, Jeff Jeff Lockemy Remedy Skilled Professional Serco North America (619) 524-2303 [EMAIL PROTECTED] ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
