Jump to content

ISAPI Host Application


SergioFeitoza

Recommended Posts

I have a very basic question regarding the difference between Standalone and ISAPI modes. I have my code (Delphi + Unigui) named as App.dproj

In STANDALONE mode I have no doubt. After compiling (without commenting the first line of the source) I generate the file MyApp.exe. I just click and see it running in browse. I use as “autostart” (if localhost) the line of code

ExploreWeb ('http: // localhost: 8077').

The doubt is In  

ISAPI mode .  To create the DLL by  the first time, I commented the first line of the source. When I compiled App.dproj the message (attachment) came that it was necessary to first define a Host Application in RUN / PARAMETERS. As my standalone App.exe was already in the directory I typed in the browser line App.exe (the standalone). It worked and the DLL was created.

My question is the following. Instead of using the (large) App.exe generated in the standalone as a Host Application, I could use any small “empty” program, since everything is already in the DLL?

Does anyone have an example of how the code for this simple Host Application could be? I didn't find us

P.S: in ISAPI mod  I use  ExploreWeb ('http: // localhost: 80').    (instead of 8077)

Comments are very welcome

HostApplicationISAPI.png

Link to comment
Share on other sites

App.exe is not the host application. App.exe IS the application. By host application they mean IIS or Apache or any other web server that can run ISAPI dll-s. My advice is to develop and debug by generating exe app and when finished recompile as ISAPI dll and install it in the production enviroment ( IIS or Apache ). There is enough documentation on the site how to do it.

Link to comment
Share on other sites

3 hours ago, adragan said:

App.exe is not the host application. App.exe IS the application. By host application they mean IIS or Apache or any other web server that can run ISAPI dll-s. My advice is to develop and debug by generating exe app and when finished recompile as ISAPI dll and install it in the production enviroment ( IIS or Apache ). There is enough documentation on the site how to do it.

Thanks, Adragan. Your answer is very useful for me. It is the first time I read this single explanation written after 3 weeks  reading documentation in many sites. As above,,  what you recommend is more or less what I am doing..

To conclude, please help me understand the following: When I use the standalone version, the triggering of the process to see the app screens is done by double-clicking on the file App.exe. When using ISAPI I have a DLL. If I click on it, nothing will happen. Who triggers the process for the screens to appear? After they are activated, I understand that to use them I just need to type in the browser like http://MySiteIP/MyAlias/MyCodeDLL.dll. How to start the screens?
If I'm talking nonsense please correct me.

Thanks in advance

Link to comment
Share on other sites

8 hours ago, alfr said:

Have you looked at http://www.unigui.com/doc/online_help/isapi_module.htm

and the 7.0 sub page? If not this is a good start. 

Thank you Alfr    ….  I did read this link several times before but only now I think I understood it. However  I still have a doubt. I use Apache 2.4.41

THE INSTRUCTION IN YOUR LINK is centered in the file      HTTPD.CONF      doing the following:

1)       Uncomment the line:    LoadModule isapi_module modules/mod_isapi.so

2)       Associate .dll files with ISAPI module by adding the following line:  AddHandler isapi-handler .dll

3)       Add your module directory to Apache directory entries. Modify <Directory /> section as :

<Directory "C:/MyApps">

    Options Indexes FollowSymLinks ExecCGI

    AllowOverride None

    Require all granted

</Directory>

4)       Create a new Alias for your directory like   …..    Alias /MyApps "C:/MyApps"

5)       Restart your Apache server after making the necessary modifications to httpd.conf file.

 

IN ANOTHER PLACE I FOUND A SUGGESTION FOCUSED IN THE FILES “HTTPD-VHOSTS.CONF”  AND   “HOSTS”,

1º – Acess Wamp DIRECTORY “apache\conf\extra” file “httpd-vhosts.conf” . Add or each sub domain (each app)

<VirtualHost *:80>

DocumentRoot “C:\Wamp\htdocs\SuaPasta”    (       C:/MyApps  ???????  )

ServerName MyApps.localhost.com

</VirtualHost>

“DocumentRoot” is the directory of my site   “ServerName” is the name of the subdomain,

 2º – Acess “C:\Windows\System32\drivers\etc”.   Open file  “HOSTS” and ADD for each subdomain the line

127.0.0.1      MyApps.localhost.com

THE DOUBT IS : Should I do one of the two alternatives above  OR should I do BOTH

 

 

 

 

Link to comment
Share on other sites

In very profane words here is how it goes:

Classes presented by UniGui include a TCP server somewhere ( ServerModule actually ).

When you compile as an app you compile the server inside the app + all the stuff you developed.

Click on the app and it runns in the backgroud. You can see it in the task bar.

If you run the browser and input http://localhost:8080 basically you request a connection to that TCP server from the app on port 8080 on protocol http. 

Now let't take Apache. Apache has some internel functions that let you bind external libruaries to it. Actually all Apache is a collection of libruaries with various functions.

What Unigui does is to create a dll that has an entry point that can be called by Apache. That's why you put in the browser  http://192.168.1.1/your_app.dll . You ask Apache to connect to the TCP server from your_app and present whatever your MainForm shows. 

Don't play too much with http.conf. You can mess it up easily.

You can do without VirtualHost. First variant is the simplest.

Link to comment
Share on other sites

53 minutes ago, adragan said:

In very profane words here is how it goes:

Classes presented by UniGui include a TCP server somewhere ( ServerModule actually ).

When you compile as an app you compile the server inside the app + all the stuff you developed.

Click on the app and it runns in the backgroud. You can see it in the task bar.

If you run the browser and input http://localhost:8080 basically you request a connection to that TCP server from the app on port 8080 on protocol http. 

Now let't take Apache. Apache has some internel functions that let you bind external libruaries to it. Actually all Apache is a collection of libruaries with various functions.

What Unigui does is to create a dll that has an entry point that can be called by Apache. That's why you put in the browser  http://192.168.1.1/your_app.dll . You ask Apache to connect to the TCP server from your_app and present whatever your MainForm shows. 

Don't play too much with http.conf. You can mess it up easily.

You can do without VirtualHost. First variant is the simplest.

Thank you Adragan. Very clear words and is what I needed to know. I will implement the deployment

Link to comment
Share on other sites

I've been trying to run my ISAPI DLL program on localhost for days. I use Apache (Wamp) and not IIS. Standalone works fine but I need to use ISAPI . I tried to modify the httpd.conf file, but I must be missing something because there was an error “This is not a valid Windows program”. The directory where the DLL is located is C: \ SWDweb. I would like to use Alias /SWDweb/

QUESTIONS:

1) Are the following lines spelled correctly or are there any / or \ errors? If wrong please show me the right way

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Alias / SWDweb "C:/SWDweb"

<Directory "C:/SWDweb">

    Options Indexes FollowSymLinks ExecCGI

    AllowOverride None

    Require all granted

</Directory>

Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

2) What I  write in Delphi --- RUN / PARAMETERS. If I don't write something in Host Application, the DLL do not compile. In “Host Application” should I write a call to Apache ***? like C:\wamp\wampmanager.exe?

3) What address should I type in the browser to access the DLL?

4) If I put the following text in the TUniServerModule.UniGUIServerModuleBeforeInit (Sender: TObject) it may be a problem.?

if ExtractFileExt (ExtractFileName (ParamStr (0))) = '. exe' then

                 ShellExecute (0, 'open', 'http: // localhost: 8077', nil, nil, SW_SHOWNORMAL)

  end;

--------------------------------------------------------------------

COMPLEMENTING

  My file httpd-vhots.cnf is

# Virtual Hosts
#
<VirtualHost *:80>
  ServerName localhost
  ServerAlias localhost
  DocumentRoot "${INSTALL_DIR}/www"
  <Directory "${INSTALL_DIR}/www/">
    Options +Indexes +Includes +FollowSymLinks +MultiViews
    AllowOverride All
    Require local
  </Directory>
</VirtualHost>

-----------------------------------------------------------------

and in my HOSTS file C:\Windows\System32\drivers\etc\hosts
it is written

#    127.0.0.1 localhost
#    ::1 localhost
# 127.0.0.1 localhost
# ::1 localhost
# 127.0.0.1 local.host
# 127.0.0.1 SWDweb.localhost.com

127.0.0.1 localhost
::1 localhost

-------------------------------------------------------------

Link to comment
Share on other sites

I need help. I made detailed text to be useful to other beginners, like me, in the "deploy". After 15 days trying to deploy my program (ISAPI + Apache) I believe I am close to achieving it. I created the "VirtualHosts" and "Alias" and I hope that httpd.conf, httpd-vhosts.conf (Apache) Host files are correct (or almost).

hosts.txt

httpdSEM.conf

httpd-vhosts.conf

WrongScreen.png

Link to comment
Share on other sites

You should edit httpd.conf and not httpd-vhosts.conf as you have listed.

Also make sure you reference the DLL file and not EXE as you seem to have done in the browser.

What you have in your Directory setup seems to be correct, except for the space between "/" and the alias name, in the alias declaration.
And you may add the line "DirectoryIndex swdweb.dll" as default file to load if you want to avoid having to specify the filename:

 

Alias /SWDweb "C:/SWDweb"
<Directory "C:/SWDweb">
    Options Indexes FollowSymLinks ExecCGI
    AllowOverride None
    Require all granted
    DirectoryIndex swdweb.dll
</Directory>

 

Link to comment
Share on other sites

Just now, Ron said:

You should edit httpd.conf and not httpd-vhosts.conf as you have listed.

Also make sure you reference the DLL file and not EXE as you seem to have done in the browser.

What you have in your Directory setup seems to be correct, except for the space between "/" and the alias name, in the alias declaration.
And you may add the line "DirectoryIndex swdweb.dll" as default file to load if you want to avoid having to specify the filename:

 


Alias /SWDweb "C:/SWDweb"
<Directory "C:/SWDweb">
    Options Indexes FollowSymLinks ExecCGI
    AllowOverride None
    Require all granted
    DirectoryIndex swdweb.dll
</Directory>

 

Thank you Ron  I will check this ( I think the spaces after /  did not occur there ). I will also replace the wampserver 64 bits by 32bits. Actualy I knew minutes ago about some more easu to use webservers like OmniSecure or OmniHttpd  . I will check everything  Thanks again

Link to comment
Share on other sites

It should not be an issue with the server, so there should be no reason to replace apache.

If the apache server is setup correctly and is able to serve any html page, it should work fine with Unigui, and if not you have a config issue.

Also, I do not use the WAMP packages, but download the apache windows binaries and install it manually - not much work at all.
Basically you just download, unzip and run one single line to install the httpd as a windows service, and that's it.

Link to comment
Share on other sites

Just now, Ron said:

It should not be an issue with the server, so there should be no reason to replace apache.

If the apache server is setup correctly and is able to serve any html page, it should work fine with Unigui, and if not you have a config issue.

Also, I do not use the WAMP packages, but download the apache windows binaries and install it manually - not much work at all.
Basically you just download, unzip and run one single line to install the httpd as a windows service, and that's it.

Thank you Ron ... I will consider your words  Kind Regards

 

 

Link to comment
Share on other sites

18 hours ago, SergioFeitoza said:

Thank you Ron ... I will consider your words  Kind Regards

 

 

With Xamp and a good video was easier .

This video is the best one I found about “Delphi / uniGUI: ISAPI application with Apache Server. Simple and Practical”. With it and Xamp I could finally deploy my program. Coul be in the  site / manual

https://www.youtube.com/watch?v=krSKLEt6KMY

Link to comment
Share on other sites

In that video he moves the documentroot and adds index.dll as default file.

Of course it works, but it is not the preferred way, as you have to rename your apps to index.dll.

The manual way should work fine, and you can also there add the app as the index file without renaming it,
and it leaves the documentroot for other files you might want to serve, e.g. PHP files for quick backend access.

But I am happy that you found a solution, and things will get a lot easier as you continue experimenting :)

Link to comment
Share on other sites

Just now, Ron said:

In that video he moves the documentroot and adds index.dll as default file.

Of course it works, but it is not the preferred way, as you have to rename your apps to index.dll.

The manual way should work fine, and you can also there add the app as the index file without renaming it,
and it leaves the documentroot for other files you might want to serve, e.g. PHP files for quick backend access.

But I am happy that you found a solution, and things will get a lot easier as you continue experimenting :)

Thanks Ron for your time and answer..

Actually, I did not succeeded yet as explained in this post of yesterday. No answer yet.. http://forums.unigui.com/index.php?/topic/14899-error-500-in-deploying-isapi-xampp/

In these last 3 weeks I am trying without success to deploy an ISAPI + Apache code.

I am disappointed because after two years converting a source to Unigui I was successful only to make it work in Standalone mode which does not attend my needs.

I could not imagine how difficult would be to deploy this ISAPI with Apache. The documentation is made for experts in deployment and not for people which is deployng by the first time. Documentation is the only weak point of the excelent Unigui.

 If I knew I would have these difficults in deploying,  two years ago, before doing the conversion VCL to Unigui,  I would certainly adopt another alternative like learning JS and to re-make my code. I have now a a rare engineering software, possibly unique in the World, which works standalone but I am loosing a lot of money because I can not put the service to work in the browser..

Link to comment
Share on other sites

Just now, SergioFeitoza said:

Thanks Ron for your time and answer..

Actually, I did not succeeded yet as explained in this post of yesterday. No answer yet.. http://forums.unigui.com/index.php?/topic/14899-error-500-in-deploying-isapi-xampp/

 

In these last 3 weeks I am trying without success to deploy an ISAPI + Apache code.

 

I am disappointed because after two years converting a source to Unigui I was successful only to make it work in Standalone mode which does not attend my needs.

 

I could not imagine how difficult would be to deploy this ISAPI with Apache. The documentation is made for experts in deployment and not for people which is deployng by the first time. Documentation is the only weak point of the excelent Unigui.

 

 If I knew I would have these difficults in deploying,  two years ago, before doing the conversion VCL to Unigui,  I would certainly adopt another alternative like learning JS and to re-make my code. I have now a a rare engineering software, possibly unique in the World, which works standalone but I am loosing a lot of money because I can not put the service to work in the browser..

 

Hi Ron     Seems that worked when I added 64 bits  platsorm. I will do more tests today an to inform here

I got  info about this here http://unigui.com/doc/online_help/creating-a-new-apache-project.htm

I am suggesting to Unigui team to add this to the Manual (about 32-64 bits) in the first line part "Deploying with Apache"

Link to comment
Share on other sites

I am sorry to hear about your struggle to find a solution. People generally do not have such issues, is my impression.

I have installed apache manually on several machines and have never had any problems that were not solved rather quickly on this ISAPI solution by configuration.

As the manual suggests, only a few configurations in the httpd.conf are needed, and whether you run 32 or 64 bits version should be irrelevant.

I personally prefer the apache solution because it is so easy to setup, with just a few quick modifications.

I have made an example project, with windows binaries of Apache 2.4 from ApacheLounge, in the attached file.

1) Unzip Apache24.zip to C:\Apache24

2) Go to \bin subdir and run httpd.

3) Open http://localhost:81/test in browser, to load test.dll project in \test subdir.

 

The only mods to the httpd.conf that I did was

1) For the mime section: AddHandler isapi-handler .dll   

2) <Directory "C:/apache24/test">
    Options FollowSymLinks ExecCGI
    AllowOverride None
    DirectoryIndex test.dll
    Require all granted
</Directory>
Alias /test "C:/apache24/test"

3) Set port to 81, to not conflict with your WAMP server, if you have it running.

The ISAPI module was already activated in the httpd.conf. It took me about ten minutes to make this example project.

You can also download Apache binaries directly from https://www.apachelounge.com/download/VC15/
and just use my modified httpd.conf file and compile the test.dll yourself from the project.

https://home.apache.org/~steffenal/VC15/binaries/httpd-2.4.46-win32-VC15.zip

Apache24.zip

test.zip

Link to comment
Share on other sites

14 hours ago, Ron said:

I am sorry to hear about your struggle to find a solution. People generally do not have such issues, is my impression.

I have installed apache manually on several machines and have never had any problems that were not solved rather quickly on this ISAPI solution by configuration.

As the manual suggests, only a few configurations in the httpd.conf are needed, and whether you run 32 or 64 bits version should be irrelevant.

I personally prefer the apache solution because it is so easy to setup, with just a few quick modifications.

I have made an example project, with windows binaries of Apache 2.4 from ApacheHaus, in the attached file.

1) Unzip to C:\Apache24

2) Go to \bin subdir and run httpd.

3) Open http://localhost:81/test in browser, to load test.dll project in \test subdir.

 

The only mods to the httpd.conf that I did was

1) For the mime section: AddHandler isapi-handler .dll   

2) <Directory "C:/apache24/test">
    Options FollowSymLinks ExecCGI
    AllowOverride None
    DirectoryIndex test.dll
    Require all granted
</Directory>
Alias /test "C:/apache24/test"

3) Set port to 81, to not conflict with your WAMP server, if you have it running.

The ISAPI module was already activated in the httpd.conf. It took me about ten minutes to make this example project.

 

Apache24.zip

test.zip

Dear Ron

Thank you very much and congratulations  for the high quality and didactics of the material that you included in this post. It will be very useful for me to clean up  and to  adjust what I have done after 3 weeks trying to deploy ISAPI + Apache.

I have two small doubts in the file httpd.conf:

a)      In the # DirectoryIndex part is written

b)      <IfModule dir_module>

c)          DirectoryIndex index.html

d)      </IfModule>

 

·         Should I include      “DirectoryIndex index.dll … before….  index.html  ?

·         If , instead of the directory C:/apache24/test"  I had  two directories (two apps) named  testA and testB and including testA.dll and testB.dll , could I , instead of naming index.dll,  to write something like:  ….   Directory testA.dll testB.dll  index.dll    ….  ?

 

As finding the right post in the forum  is frequently difficult, in the middle of so many posts,

 I suggest to  FMSOFT team to  put these files and text  in the first line of the page of the Manual :

  http://www.unigui.com/doc/online_help/apache_2_2.htm

 

 READ FIRST THE FILES:

C:\Apache24\INSTALL.txt

C:\Apache24\conf\httpd.conf

In this post from Ron, there is an example project, with windows binaries of Apache 2.4 from ApacheHaus, in the attached file.

1) Unzip to C:\Apache24

2) Go to \bin subdir and run httpd.

3) Open http://localhost:81/test in browser, to load test project in \test subdir.

 The only modifications to the httpd.conf that I did was

1) For the mime section: AddHandler isapi-handler .dll   

2) <Directory "C:/apache24/test">
    Options FollowSymLinks ExecCGI
    AllowOverride None
    DirectoryIndex test.dll
    Require all granted
</Directory>

Alias /test "C:/apache24/test"

P.S: The ISAPI module was already activated in the httpd.conf. It took about ten minutes to make this example project.

Thanks again Ron,   I owe you this

Link to comment
Share on other sites

On 8/6/2020 at 7:19 PM, SergioFeitoza said:

Dear Ron

Thank you very much and congratulations  for the high quality and didactics of the material that you included in this post. It will be very useful for me to clean up  and to  adjust what I have done after 3 weeks trying to deploy ISAPI + Apache.

I have two small doubts in the file httpd.conf:

a)      In the # DirectoryIndex part is written

b)      <IfModule dir_module>

c)          DirectoryIndex index.html

d)      </IfModule>

 

·         Should I include      “DirectoryIndex index.dll … before….  index.html  ?

·         If , instead of the directory C:/apache24/test"  I had  two directories (two apps) named  testA and testB and including testA.dll and testB.dll , could I , instead of naming index.dll,  to write something like:  ….   Directory testA.dll testB.dll  index.dll    ….  ?

 

As finding the right post in the forum  is frequently difficult, in the middle of so many posts,

 I suggest to  FMSOFT team to  put these files and text  in the first line of the page of the Manual :

  http://www.unigui.com/doc/online_help/apache_2_2.htm

 

 READ FIRST THE FILES:

C:\Apache24\INSTALL.txt

C:\Apache24\conf\httpd.conf

In this post from Ron, there is an example project, with windows binaries of Apache 2.4 from ApacheHaus, in the attached file.

1) Unzip to C:\Apache24

2) Go to \bin subdir and run httpd.

3) Open http://localhost:81/test in browser, to load test project in \test subdir.

 The only modifications to the httpd.conf that I did was

1) For the mime section: AddHandler isapi-handler .dll   

2) <Directory "C:/apache24/test">
    Options FollowSymLinks ExecCGI
    AllowOverride None

    
DirectoryIndex test.dll
    Require all granted
</Directory>

Alias /test "C:/apache24/test"

P.S: The ISAPI module was already activated in the httpd.conf. It took about ten minutes to make this example project.

Thanks again Ron,   I owe you this

Making your DLL the default indexer is not such a good idea. And again, OmniSecure, despite  being old, works at the same level of performance as Apache HTTPd (even better and more stable).You had some headaches trying to do that configuration with just one server, imagine doing that with dozens, mixing PHP and ISAPI, admin panels, domains and folder alias, prefix etc...  etc. .

There is a lot of hype about Apache not justified nowadays. All windows professional and up versions  has IIS by default. And since your probably will end up running  in a cloud in a Windows Server X version, better do in IIS at once.

The Apache module to load ISAPI is a third party project not very stable.  Just in version  2.2 and newer became more reliable. But I'm tired of it since I have a lot of free HTTPd available more well documented and stable.

TL;DR: I've had a lot of problems with Apache for Windows using ISAPI and never had the same problems with same ISAPI using IIS. Even thought using CGIExpert, IntraWeb,  , uniGUI, Delphi ISAPI in the same computers with a lot of projects. Never saw a big project for ISAPI using Apache for windows. Except in Linux distro's. Since we´re not going to use Linux, there is no competition here just misinformation.

Link to comment
Share on other sites

Hi Fred. Thank you for your always useful vision and comments. It arrived in the right moment that I need to try to use ISS. I started with Apache by the same reason why most people use  MSWord. It was the first I had contact for deployment.  This is the first time I use Isapi  DLLs with browser although I have  experience with VCL.

I need to do it because now I learned that standalone mode do not attend my need of putting the code  as a service.  

If I understood this 2 years ago, I would go directly to Isapi  and not use my time with Standalone. For Standalone  my “big” calculations code is ready and running well. However, it is useless to run as a service ( licenses, etc…).

About Isapi + Apache I succeeded – in part - do deploy the code. The initial doubts and errors are superseded, and I  deployed successfully  a part of the code. However, I arrived at the point of my post of yesterday “Size of ISAPI DLL may be a problem even  if works well as Standalone?”

The calculations code uses  many variables. I could deploy it  using a “less heavy”  MainForm, with a much lower number of variables. I am using exactly the same  MainModule (30 TMyQueries) , ServerModule and LoginPage are exactly the same.  After many tests and without compilation / build errors, when I run in the browser  I continue  having  the ERROR 500 when using the complete MainForm I in the figure attached)

So, before trying with IIS, I would enjoy to have your view on the following:

1.       From the point of view of size, if it works properly in standalone, should work well as ISAPI ? . The codes are exactly the same except for the “first line”

2.       Is there a way to increase the stack or something like this ?

3.       Of I use IIS the performance may be better than Apache

Any suggestion is welcome. I think there is very few possibilities for the optimization of the “weight” of the  code. The size of the DLL is around 20 MB

Link to comment
Share on other sites

Dear Sergio,

We have an Unigui Application  / 64 bits :

- with 16 Mo  size   (exeFile)

- Working as Service / HyperServer 64 

- On Windows Server 2016 / 64 bits

wich works like a charme, Stable during  2 years.

 

We choose Service, as it's very simple to deploy (you can see my Easy_Install_3.0)  in Samples Section. 

But, for our futur works, we are thinking to go with IIS (Pooling technics). I have read some good things about IIS  :)

Best Reagrds.

 

 

Link to comment
Share on other sites

55 minutes ago, Abaksoft said:

Dear Sergio,

We have an Unigui Application  / 64 bits :

- with 16 Mo  size   (exeFile)

- Working as Service / HyperServer 64 

- On Windows Server 2016 / 64 bits

wich works like a charme, Stable during  2 years.

 

We choose Service, as it's very simple to deploy (you can see my Easy_Install_3.0)  in Samples Section. 

But, for our futur works, we are thinking to go with IIS (Pooling technics). I have read some good things about IIS  :)

Best Reagrds.

 

 

Thank you very much Abaksoft. I will check about   Service and Easy_Install_3.0 . I wll write soon ....

 

Link to comment
Share on other sites

On 8/10/2020 at 5:03 PM, Abaksoft said:

Dear Sergio,

We have an Unigui Application  / 64 bits :

- with 16 Mo  size   (exeFile)

- Working as Service / HyperServer 64 

- On Windows Server 2016 / 64 bits

wich works like a charme, Stable during  2 years.

 

We choose Service, as it's very simple to deploy (you can see my Easy_Install_3.0)  in Samples Section. 

But, for our futur works, we are thinking to go with IIS (Pooling technics). I have read some good things about IIS  :)

Best Reagrds.

 

 

Dear Abaksoft  ... your installer is  great. I started to use it but as the Isapi + Alache solution worked I will come back  to it more ahead. The information below may be useful to other people in the  forum ........................ 

Dear Daniel.

You found the error and the solution using Isapi + Xampp. As you wrote above, the error occurred because of the x86 ISAPI module running into an x64 compile Apache ISAPI module. Then I removed the 64 bits version and installed the XAMP 7.3.2 x86 . So, I went to the code and deployed as x86 (32-bit Windows) ISAPI module. Now it is running well in the local host (see the figure). Now I will clean some small parts and deploy in the web through my provider.

After the service is available in the web – I hope by next week – I will try to do the same with IIS and Windows. Actually, I did a fast trial with them this morning. However, your solution worked first.

Thanks to all of you which helped me açong these weeks , specialty to Daniel, Fred, Abaksoft and Silvio

Deployed.png

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...