The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
How to create a primary key for SLX table from outside SLX
Posted: 19 Jun 06 11:38 AM
|
symbicort side effects symbicort asthma dose fiogf49gjkf0d Hi there,
We have a problem in our SLX Developmet. We will appreciate it if somebody could give us some advices.
Our network structure:
(1) The SalesLogix Server and SQL Server including Databases “OurDB” and “SalesLogix” are not in the same network domain.
(2) The Web Server and SQL Server are on the same physical machine.
(3) For the safe reason, the SalesLogix Server is in a separate domain from our Web Server and SQL Server.
Our requirement:
From a classic ASP page on the Web Server, in some cases, we need to add a new contact into the SLX Contact table.
Our Issue:
We couldn't create a Primary Key (12-character length string) with type "SLX Standard ID" for a new contact record from outside SalesLogix based on our network structure. Furthermore, we need to create a connection to SLX database by using SLX Provider and then execute the Virtual Stored Procedure “slx_dbids” through the connection to get a special Primary Key. We installed the SLX Provider on the Web Server but the SLX Provider couldn't talk with the SLX Server which is in a separate domain.
We have a solution
Using a function which could create a 12-character length string.
When we need to add a new contact, we will use that function to create a 12-character length string and then check if it is existed in SLX Contact table. If it is in the SLX Contact table already, create a new one and check it again until we get a unique one. We insert the contact info into SLX Contact table by using the 12-character length string (as its Primary Key) through a regular connection based on ADODB.Connect.
-- In this way, the format of the 12-character length string is not consistent to the format of Type “SLX Standard ID” created by SLX Component.
What we'd like to know is that: if we use the way, that is using the 12-character length string as Primary Key, are there potential troubles for the existed data or the new data in the future?
Is there better solution else?
Thanks in advance,
Jordan |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 19 Jun 06 8:53 PM
|
buy abortion pill online uk buy abortion pill online cheap fiogf49gjkf0d I'm not sure I understand. Why are you not using the SLX OLE-DB Provider? If the differing network domains is your answer, I still don't understand.
If you can use the SLX OLE-DB provider, you can execute the slx_DBIDs stored procedure to generate new ID values for the specified table. (Refer to the LAN Developer Reference Guide for more info.) |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 7:51 AM
|
fiogf49gjkf0d Check your DNS entries. If the host names resolve (see if you can PING each machines Host Name from the other machine) and IP Port 1706 is not being blocked by some network/security device, then it seems like it should work. |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 9:14 AM
|
fiogf49gjkf0d Hi Jon,
Thanks for your reply.
I indeed installed a SLX Provider on the Web Server. From the asp page on the Web Server, I tried to open a connection (ADODB.Connect) by using the SLX Provider and then execute the slx_DBIDs, but I got a message which said the SLX Server couldn't be found. Because of safe reason, our SLX Server is in the other domain.
In the other words, the asp page neither could uses the SLX Provider on the Web Server beacuse it could not found a SLX Server nor could talks with the SLX Provider on the SLX Server. As I mentioned above, we could not install a SLX Server in the domain where the Web server resides because the safe season.
What I'd like to know is that if we use the solution in my first post, that is use our own function to create a 12-character-length unique string for contact table and use a connection opened by regular OLEDB provider to add a new record in SLX Contact table, are there any potential troubles for the existed data and/or new data in the future.
Are there some solutions else?
By the way, our company doesn't use Synchronize Server. We are using SLX 6.2 Client Server + Service Pack 3.
Thanks again
Jordan
|
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 9:29 AM
|
is naloxone and naltrexone the same naloxone vs naltrexone fiogf49gjkf0d Hi Frank,
Thanks for your reply.
I describled our issue again in the reply to Jon. It is that the SLX Provider on the Web Server could not find/talk with the SLX Server in the other domain. Based on your experience, are there another solutions else?
Thanks,
Jordan |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 11:29 AM
|
fiogf49gjkf0d Jordan,
Your solution should work as long as you do not generate IDs that confict with the IDs that Slx genetates. However I still not sure it is necessary. Guess I am not understanding your setup. Are the Slx WebHost components installed on the WebServer that is on the SQL Server?
Also, since you can only have one Slx Provider (ie. SlxServer) talking to your database I am not sure what you mean when you say that you "installed a SLX Provider on the Web Server". Can you explain?
|
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 11:52 AM
|
naltrexone vs naloxone usmle narcan vs naltrexone fiogf49gjkf0d Hi Frank,
Thanks so much for the advice.
Our network structure is as follows
(1) The SalesLogix Server and SQL Server including Databases “OurDB” and “SalesLogix” are not in the same network domain.
(2) The Web Server and SQL Server are on the same physical machine.
(3) For the safe reason, the SalesLogix Server is in a separate domain from our Web Server and SQL Server.
Right now, we just use SLX Client Server application. The Web Server hosts our own website. What we want to do is to add a new contact into SLX Contact table from a classic asp page. Our employees use the SLX Server to manapulate SLX DB.
If there is only one SLX Provider which can connect the same SLX DB, we shouldn't install a SLX Provider on the web Server to be used by web page because we do need to use the SLX Provider on the SLX Server to connect SLX DB, right?
What did you mean "do not generate IDs that confict with the IDs that Slx genetates"? If we create a 12 character-length string and make sure it is unique in a SLX table, and for Contact table, we even can set the string to begin with "C" something. Is it what you meant "do not generate IDs that confict with the IDs that Slx genetates"?
Thanks again.
Jordan
|
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 1:18 PM
|
fiogf49gjkf0d One caveat to rolling this in your own stored procedure (there are MANY examples of this out there) is that you HAVE to update the SiteKeys table. If you're just looking at the last ID in the table and adding a 1 to it, that is the wrong way of going about it. You always have to pull the last record from the SiteKeys table and then increment that as well, otherwise when SalesLogix goes to create it's valid ID it will get an "already exists" exception in the DB and because of that it most likely won't increment, sending it in a loop. This is what Frank means by "conflicting IDs".
The SiteKeys table does define what goes in front of the 12 character ID. Contacts get C, Accounts A, Other (Attachments, your custom tables) gets Q, UserNotification gets n, etc etc. I do think there's a list out there somewhere but all you have to do is look at a valid ID in the tables to see how SalesLogix creates them.
Regarding the provider I thought that was what created the OleDB profile on the machine. You can create the connection string using the File.udl approach on the machine with the provider and just use that string to connect from anywhere. As long as you can connect to port 1706/1705 (it uses 2 ports next to each other but I can't remember if it's 1707 or 1705). |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 1:30 PM
|
fiogf49gjkf0d It is port 1707.
Since his SlxServer is already talking on port 1433 to the SQL database, that is on the same system as the Web Server, it seems to me like he should be able to connect to the SlxServer using ADO as long as ports 1706 and 1707 are open. |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 1:45 PM
|
fiogf49gjkf0d Hi Jeremy,
Thanks for the info.
What I still want to know is that: if we get a key which doesn't confict with the IDs that Slx genetates and ues a connection created by ADODB.Connect and opened by regular MS OLE DB Provider to maniplutae a SLX table from outside SLX, are there any potential troubles on the existed data and/or new data in the future.
Now, we just use SLX 6.2 Client Server application and don't use Synchronization Server.
Thanks again.
Jordan |
|
|
| |
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 2:01 PM
|
fiogf49gjkf0d If sync isn't an issue you could even use a native SQL connection but if you can, it's always best to use the provider mainly because of the UTC date conversions and other quirks the provider takes care of for you. The time you spend adding all of the extra hoops to make the data valid, you could just use the provider and save yourself some time.
If you're on 6.2.3 or higher I would suggest using the SLX Profiler.exe to profile creating a record from scratch. Gather up all of the SQL and then try to duplicate it EXACTLY. Inserting a Contact/Account has a lot of extra hoops than just a record in the contact or account table so using the profiler would be invaluable. You'll also want to run the Integrity Checker in intervals just to make sure you're not creating any orphans.
As far as the data goes if you create it correctly the future shouldn't be a problem. If you ever get remotes those records will be created when their database is first cut. You would have to modify this to take advantage of synchronization eventually, which is why it's usually a good idea to just use the provider up front. |
|
|
| |
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 20 Jun 06 2:23 PM
|
fiogf49gjkf0d You are correct. As long as you can connect to the ports you can use the provider. The biggest "problem", if you even want to call it that, is creating the connection string to connect to the right location. You can only use the dropdowns on the machine with the provider installed but if you're super spiffy with connection strings you could manually cobble one together just as easily.
Just as an example I've been creating an external C# app that connects using the connection string. I'm testing this across a VPN but I could just as easily expose the server to the public and connect to that (I wouldn't for security reasons). One caveat to being on a different subnet is that slx_GetServerList() stored procedure flat out doesn't work across subnet boundaries but other than that every other stored procedure functions just as easily from the other side of the room or the other side of the world. |
|
|
| |
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 21 Jun 06 6:30 AM
|
fiogf49gjkf0d Our requirement:
From a classic ASP page on the Web Server, in some cases, we need to add a new contact into the SLX Contact table.
I'm just throwing this out as a suggestion. Scribe Migrate is designed to do exactly what you want to do and more. You would create your classic ASP page that saves the contact info to be placed into SLX in some format - XML, CSV, etc... Scribe will pick this file up and do all the necessary data transformations into SLX - including all the necessary IDs. Thats one of the nicest things about Scribe is it does alot of work for you.
Just my .02
John G. |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 21 Jun 06 11:43 AM
|
fiogf49gjkf0d Hi,
In 2001 one of my clients www.tradebonds.com was launched. We use SQL Server/Saleslogix and ASP. We generate our own key with our own sequence and have never run it to a conflict issue (no sync server either). When the site was launched (it's a bit dated now), I used the saleslogix api and followed what I was told to have it generate the proper keys (account, address, contact, contact address) and it was working until we upgraded to V6 and everything broke (this is when they added the providor). Now we just use a stored proc now and its fine.
If you are going to be migrating data, I love the using Customer FX Toolkit. One of my clients is a very large real estate firm and I import data from all different places and it works really well. Plus I am a SQL programmer and this tool is a natural fit. We do import data here from a web site (hosted off our domain) and run the dts package every 15 minutes (real time is not required like it was for the bond trading site).
Good luck.
Paul
Paul |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 21 Jun 06 12:18 PM
|
ventolin over the counter uk ventolin over the counter philippines news.noerskov.dk fiogf49gjkf0d Hi Jeremy,
Assume that we can connect the port of SLX Provider/SLX Server in the other domain from our web server, can the connection created by ADODB.Connect in a ASP page on our web server be opened by the SLX Provider in the other domain?
Thanks,
Jordan |
|
|
| |
| |
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 21 Jun 06 1:06 PM
|
fiogf49gjkf0d You are connecting using OleDb which is basically the "protocol" (such as HTTP, etc). As long as you can connect to the ports, domains don't even come into consideration.
It's a little weird to grasp at first, especially when SalesLogix has to install to a domain or workgroup initially. This brings up the fact that if you wanted to deny SalesLogix access based on domain or other permissions you would have to use a firewall to deny access to those ports. It's generally a good idea to change the sysdba password and RWPass in the connection manager for the very rare possibility that someone on your network knows SalesLogix enough to create a direct connection to the database, bypassing any existing domain permissions barriers. |
|
|
| |
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 22 Jun 06 1:56 AM
|
benadryl and pregnancy third trimester benadryl and pregnancy fiogf49gjkf0d Whoa, holy cow what a thread this became overnight.
Jordan, ..
Originally posted by Jordan
I indeed installed a SLX Provider on the Web Server. From the asp page on the Web Server, I tried to open a connection (ADODB.Connect) by using the SLX Provider and then execute the slx_DBIDs, but I got a message which said the SLX Server couldn't be found. Because of safe reason, our SLX Server is in the other domain.
|
|
As others stated, I don't think this has anything to do with your network domain. Check your WINS settings. Either the IP cannot be found (in which case you can add the database server hostname to your web server's c:\windows\system32\drivers\etc\hosts file) or the SalesLogix application port is blocked.
- Jon |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 22 Jun 06 9:38 AM
|
fiogf49gjkf0d Jon,
I agree with you. These are the items I raised in my "20 Jun 06 7:51 AM" post above.
Let's not forget that the "SalesLogix Server" process has a connection to the database which is on the same system as the WebServer (this is probably happening on SQL's default port 1433). Now we want to open a OLEDB connection from the WebServer to the SlxServer.
Lastly, Jordan's comments lead me to believe that the WebServer/SQLServer is in a DMZ (ie Secured Network). Ports and DNS (ie IP Address/Hostname resolution) are usually locked down in a DMZ.
|
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 22 Jun 06 10:46 AM
|
fiogf49gjkf0d Thanks to everybody.
I'd like to confirm the following:
Besides the SLX Provider on the SLX Server, can we install the other SLX Provider on the Web Server which is also used to open the same SLX Database?
Thanks,
Jordan
|
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 23 Jun 06 2:19 PM
|
fiogf49gjkf0d I think it creates unnecessary duplication simply because the connection string will be the same if it's ran on the web server or the slx server. The only time it'll ever differ is if the connection manager is installed and you can define aliases on your web server. It's installed in admin tools or a remote client but I don't believe it's installed with the client provider msi file. If it is installed then you can have independent connections from your server that would still work if your slx server went down (provided the db was on another machine of course). This also brings a liability in that your aliases may not be secured with a rwpass or may differ from the slx server. This could create a backdoor that only a clever individual could access but it's still a backdoor.
I may be completely wrong as the concept still seems foreign. I don't need the OLE Db Provider if I can talk to the SLX server on my network. I do need the provider if I can't talk to the server but I can talk to the db directly. I think that's right but there are variables that make either method moot, such as the slx server and db being on the same machine. |
|
|
|
Re: How to create a primary key for SLX table from outside SLX
Posted: 27 Jun 06 9:27 AM
|
fiogf49gjkf0d Hi all,
We selected the solution that we recofigured the network and firewall - open the port 1706 to our web server. In addition, we installed SLX Client on the web server. After doing so, the classic asp page on the web srevre can get the connection to SLX database by using the SLX provider on the web server through SLX server which in the other domain.
Thanks for everyone's help. The information from you all is very valuable.
Jordan |
|
|
|