06-06-2015 02:58 PM
I am trying to log into act premium for wev v17 database using the above code:
ActFramework ACTFM= new ActFramework();
The login process takes about 9 seconds-extremely slow. Is there any other method to call for login that can be faster?8 or 9 seconds are normal?
06-07-2015 02:46 AM - edited 06-07-2015 03:13 AM
I tried Logon with the Demo database and it takse around 7,5 seconds. That is a long time as well. Is that the normal logon process time?Or am i doing something wrong? The database and the project are in the same host-so there is no ip-communication delay added.
To prvide you with more info: I have a windows server 2012 with sql 2014 installed and Act-premium for web, Act installed a new instance of act7 , sql 2008 r2 instance-if I am not wrong (highly possible that I am wrong just Act poped up this message during installation). Could it be that my configuration is causing a problem?Specially sql server 2014?Should i have sql server installed or better not and let Act decide all about the sql server and instances?
06-07-2015 11:22 AM
I haven't timed it but I think that's pretty normal. You could monitor what Act! is doing when you logon and see if you need to unblock some website addresses, etc.
06-07-2015 12:14 PM
So i suppose the apfw website that comes with the act for web takes also 7,5 seconds to log in into a demodatabase and 10-20 seconds to logon to a database full fo data? Is there a work around for this ?What do you mean by unblocking website addresses?
06-07-2015 12:25 PM
When you log into an Act! database it has to verify that the user is allowed to log in. It does this by using a service called Protexis which talks to the licensing website. If the system you are on is preventing Protexis from checking in you will have some timing issues. There are other websites that are accessed when Act! is launched. I haven't tried to see what websites are accessed when you login from an app instead of from the Act! app. The few seconds it takes to come up hasn't been that significant for any of the projects I've worked on and there have been quite a few. Why does a 7.5 second delay cause concern for you? Not criticizing just curious.
06-07-2015 01:04 PM
Thank you for the info, really enlightening. 7,5 seconds is only for demo database-for my database is 10-12 seconds and that time for the web is really unacceptable. Is there any work arround to get to 2,3 seconds or I should give up trying?
06-07-2015 05:32 PM
You can open the database and leave it open. The second person to connect should be able to connect more quickly. What are you doing that 7.5 seconds is too long? It seems like pretty much every web service I log into takes that long except web services that are specifically designed for fast responses to the initial connection.
06-08-2015 05:28 AM
I am building a RESTful api on top of act. This connects to a website that must have immediate responses. In every request that is being sent from the website, the api must fetch data from the act database. Since the connection is lost after each request is processed, for every new request a new LogOn is required.
So if the LogOn takes 6-8 seconds to load that will mean that the webpage which is waiting for the data of the api (that connects to the act database) ALSO waits for 6-8 seconds at least to load. That means that in the scenario every request to the api takes 6-8 seconds to complete.
Is there a way to lower the timings in the process I have mentioned?
If not, do you propose a different architecture?
06-08-2015 10:23 AM
Create a web service publisher and install it on the system hosting the Act! database. Log into the Act! database with the web service publisher service and leave the connection open. Then use your api to talk to your web service app. You'll have an initial login of 6-8 seconds but subsequent requests to the web service should be dependent on how well the code was written and how good the hardware is. You could get the response down to several milliseconds if you wanted. You could eliminate the 6-8 second delay by prelaunching the web service publisher and leaving it running. If you want help writing it I can help you out but my time would be billable. Feel free to send me a private message or contact me by getting my email address from the website in my signature.
06-08-2015 03:03 PM
thank you for replying. Within the same application two consecutive LogOn calls take approximately the same time (7-8 seconds) to load. That means that when the second logOn call is made, the connection is still open and yet it still takes 8 seconds to load again. In this context, I dont see how your solution would help bring down the timing of the logon. Am I mistaken?