Page tree
Skip to end of metadata
Go to start of metadata

This page includes descriptions on how to deploy Aptify Web, e-Business 5.5.3, or e-Business 6 without using an installer.

Why?

Sometimes it's just simpler to do so. Maybe you can't find the installer, or the installer won't work for some reason, or the installer runs, but it is crashing out midway through.

This page includes instructions on how to manually deploy the websites, as well as what/where settings need to be changed to get it to work. 

Note

All of these assume you have the requisite IIS and server settings already setup and for e-Business 6, the database component installed.

See the Quick List for Setting up and Troubleshooting Aptify Infrastructure page for more details on environment installs (.NET 3.5, .NET 4.5, MVC4, for example) and Windows Features for IIS that are necessary depending on Aptify Web or E-Business:  You should have a basic "Default Web Site" in your IIS.

How to setup the Aptify Web 6.0, 6.1, or 6.2 website

In addition to the IIS and server settings mentioned previously, make sure to have installed SQLSysClrTypes.msi and ReportViewer.msi. If you are setting this server up for the first time, you must also install MVC 4 framework.

You may need to add an HTTPS binding to the Default Web Site, if one doesn't exist. In IIS, select Default Web Site and then click Bindings in the far right menu:

If one doesn't appear for HTTPS, add a new one:


The SSL Certificate you use here may be client-specific or you may want to generate a self-signed certificate for testing purposes.

Creating the Application Pools

  1. Go to IIS Manager and select Application Pools. Create two new ones.

  • Aptify_HTML5Web:

Right-click on the Aptify_HTML5Web Application Pool and click Advanced Settings. Scroll down to Identity, and open the record.

Change the Application Pool Identity from ApplicationPoolIdentity to LocalSystem.

Aptify_SOAWeb

Right-click on the Aptify_HTML5Web Application Pool and click Advanced Settings. Scroll down to Identity, and open the record. Select Custom account and set:

Enter the username (with domain) and password for the user you want to use as an app pool user for Aptify Web and Aptify Web services.


This user must also exist in Aptify and have AptifySOAAppPoolGroup group permissions.

Aptify recommends against using the same account to service Aptify Web SOA as either e-Business Classic, e-Business 6, or your Async Service. It is ok to do so for dev/test purposes, but otherwise the accounts should all be different. Each requires different levels of permissions and it's recommended to limit each to the minimum-required permissions.

Click OK.

Deploying the pages

Unzip or copy your existing AptifyWeb website to the server. Copy the AptifyServicesAPI and Aptify folders into your C:\inetpub\wwwroot location. (You can change this location to somewhere else if preferred)

When you refresh the Default Web Site, you should see them there now. Right click on Aptify and select Convert to Application.

Change the Application pool to Aptify_HTML5Web. You can otherwise leave as is, unless you put the physical path somewhere else. Click OK.

Right click on the AptifyServicesAPI site and select Convert to Application. Change the Application Pool to Aptify_SOAWeb. Click Test Settings- This will verify your app pool user has access to that folder.

If you have a specific hostname for this site with a DNS entry (e,g, testaptifyweb.aptify.com) you can fill that in the Host Name.

It should as long as it's in the IIS_IUSRS Windows group.


Changes to update to your environment

Go to the AptifyServicesAPI/web.config file. Using NotePad++ or something similar, do a find-and-replace.

Replace the other server's name (in this screenshot APTIFYDEV) with either your new server name or if you used a Host Name in the binding, the Host Name. Replace All.

If you have multiple HTTPS sites without a different DNS entry, you may need specify the port number if it is different from default value of 443. (This can be found in the Site's binding) If the port was listed as 446, for example, I would replace the value with servername:446


Change the below attribute to point to the database you wish to connect Aptify Web to- replace the. with the server and instance name.

<add key="Aptify.Framework.LoginServices.AptifyLogin.Server" value="." />

Change the Object Repository path to wherever you have the Aptify client installed, typically C:\Program Files\Aptify 5.0. It is this attribute:

<add key="Aptify.Framework.ObjectRepository.AptifyObjectRepository.DefaultObjectCachePath" value="C:\Program Files\Aptify 6.1" />

If you need to change the folder/location for Aptify Web uploads, change the upload path of this attribute:

<add key="Aptify.Framework.UploadsPath" value="C:\inetpub\wwwroot\AptifyServicesAPI\Uploads" />

Save the web.config file. To ensure your changes were processed, open it in Notepad and verify. If they did not, save a copy to the Desktop, edit there, and then copy over the AptifyServicesAPI version.

If using Aptify 6.2, verify your find-and-replace of the AptifyServicesAPI\services web.config changed the values of the Redirect and Login attributes, as well as the CORS values. The attributes that need to be changed start with :

  • <add key="AuthenticatedRedirectLocation" (usually around line 74)
  • <add key="InterfaceURL" under <Provider lookupName="DomainWithContainer" attribute (usually line 80)
  • <add key="InterfaceURL" under <Provider lookupName="SQLNeedsInputWithContainer" attribute (usually line 83)
  • <add key="Aptify.Services.CORS.AllowedDomains (usually around line 146)


Go to the Aptify\script\Aptify\configuration Aptify.Framework.Configuration.External.js  file. Using NotePad++ or something similar, do a find-and-replace just as you did before in the web.config. (Remember to specify port number if it previously applied.)


Save the Aptify.Framework.Configuration.External.js file. To ensure your changes were processed, open it in Notepad and verify. If they did not, save a copy to the Desktop, edit there, and then copy over the Aptify\script\Aptify\configuration version.

If Using Aptify 6.2

Go to the Aptify\web.config file. Using NotePad++ or something similar, do a find-and-replace just as you did before in the web.config. (Remember to specify port number if it previously applied.)

Note: Verify your find-and-replace changed the values of the Access-Control-Allow-Origin and Content-Security-Policy values. The attributes that need to be changed start with :

  • <add name="Access-Control-Allow-Origin" (usually around line 118)
  • <add name="Content-Security-Policy" attribute (usually line 127)
    (This one has multiple places in the value where it needs to be replaced.)


Go back to IIS. If you only have Aptify Web under your site, you can just select the overall site. However, if you have other sites under Default Web site, you will want to do this to the AptifyServicesAPI application and Aptify application separately.

Select the AptifyServicesAPI site, and click Authentication under the IIS section. Select Anonymous Authentication, and click Edit under Actions in the far right column.

Change it from a specific user to Application Pool identity. Go to the Aptify site and make the same change.

Restart IIS.

Post-deployment items

Once deployed, you may want to run several of the HTML5 Generator Process Flows, in particular the Entities and Views to generate this metadata appropriate to your database and system.

If you have any custom .dlls, Crystal Reports, or other objects that need to be run out of Aptify Web, you'll need to copy those into the AptifyServicesAPI\bin folder.

Confirm it's deployed and working. First, go to https://servername/AptifyServicesAPI/services/checkconnection to verify the app pools are running and services are working. It should just return a date/time stamp.

Then, go to https://servername/Aptify to confirm you can login to Aptify Web.


How to setup the e-Business 5.5.3 website

Creating the Application Pool

Go to IIS Manager and select Application Pools. Create one new one.


AptifyEbusiness:

Right-click on the AptifyEbusiness app pool and click Advanced Settings. Scroll down to Identity, and open the record. Select Custom account and set:

Enter the username (with domain) and password for the user you want to use as an app pool user for e-Business services.

This user must also exist in Aptify and have User and Basic group permissions, as well as have an e-Business license.
Aptify recommends against using the same account to service e-Business Classic as either Aptify Web SOA, e-Business 6, or your Async Service. It is ok to do so for dev/test purposes, but otherwise, the accounts should all be different. Each requires different levels of permissions and it's recommended to limit each to the minimum-required permissions.

Click OK.

Deploying the pages

Unzip the Ebiz553.zip file and copy the folder into your desired location.

Important

For security reasons, Aptify recommends against putting the e-Business Classic site in the default inetpub\wwwroot location.

When you refresh the Default Web Site, you should see it there now. Right click on ebiz553 and select Convert to Application.

Enter where you copied the files as your location for the physical path. Click ok.

Right click on the ebiz553 site and select Convert to Application. Change the Application Pool to AptifyEbusiness. Click Test Settings- This will verify your app pool user has access to that folder.

It should as long as it's in the IIS_IUSRS Windows group.


Changes to update to your environment

Go to the Ebiz553/web.config file. Using NotePad++ or something similar, change the below attribute to point to the database you wish to connect Aptify Web to- replace the. with the server and instance name.

<add key="AptifyDBServer" value="." />

The other attributes can remain as it is unless you have deployed this to a different location. Then you should modify the following attribute to point to the correct location:

<add key="Aptify.Framework.ObjectRepository.AptifyObjectRepository.DefaultObjectCachePath" value="E:\inetpub\wwwroot\ebiz553\bin" />

Go back to IIS. Select the Ebiz553 Application, and click Authentication under the IIS section. Select Anonymous Authentication, and click Edit under Actions in the far right column.

Change it from a specific user to Application Pool identity. Go to the Aptify site and make the same change.

Restart IIS.

Go to http://servername/Ebiz553 to confirm it's working. (note that it's HTTP, not HTTPS)


How to setup the e-Business 6 GA website

e-Business 6 installer does install some backend updates and framework that are required. Thus, this can only be used currently if you are deploying it on a database that has already had e-Buiness 6 backend installer run on it.

e-Business 6 can be deployed to the same server as Aptify Web. If so, you'll need to create a new site other than Default Web Site in IIS named e-Business 6. Right click on IIS and select Add Web Site:

Specify the path where your website will live:

Click OK.

You'll need to specify a different port for HTTP (e,g, 81) and HTTPS (e,g, 446) if you have Aptify Web/e-Business 5.5.3 on this server and you do not have separate domain names.

Whether using the Default Web Site or e-Business 6 site, you may need to add an HTTPS binding to the Default Web Site/e-Business 6 site, if one doesn't exist. 


In IIS, select Default Web Site (or e-Business 6) and then click Bindings in the far right menu:


If one doesn't appear for HTTPS, add a new one:


  1. If you are creating an e-Business 6 site alongside Aptify Web on Default Web Site, you will want to change your port to something other than 443, like 444.
  2. If you have a specific hostname for this site with a DNS entry (e,g, testebusiness.aptify.com) you can fill that in the Host Name.
  3. The SSL Certificate you use here may be client-specific or you may want to generate a self-signed certificate for testing purposes.

Creating the Application Pools

Go to IIS Manager and select Application Pools. Create two new ones.


Aptify_EBusinessWeb:

Right-click on the Aptify_e-Business Web Application Pool and click Advanced Settings. Scroll down to Identity, and open the record.

Change the Application Pool Identity from ApplicationPoolIdentity to LocalSystem.


Aptify_EbusinessSOAWeb

Right-click on the Aptify_EbusinessSOAWeb Application Pool and click Advanced Settings. Scroll down to Identity, and open the record. Select Custom account and set:

Enter the username (with domain) and password for the user you want to use as an app pool user for e-Business 6 and e-Business 6 services.

This user must also exist in Aptify and have AptifySOAAppPoolGroup group permissions.
Aptify recommends against using the same account to service e-Business 6 as either Aptify Web SOA, e-Business Classic, or your Async Service. It is ok to do so for dev/test purposes, but otherwise the accounts should all be different. Each requires different levels of permissions and it's recommended to limit each to the minimum-required permissions.

Click OK.

Deploying the pages

Unzip the Ebusiness6.zip file and copy the SOA and UI folders into your C:\inetpub\wwwroot location. (You can change this location to somewhere else if preferred)


When you refresh the Default Web Site (or the ebusiness6 site if you set up a separate one), you should see them there now. Right click on UI and select Convert to Application.

Change the Application pool to Aptify_EbusinessWeb. You can otherwise leave as is, unless you put the physical path somewhere else. Click OK.

Right click on the SOA site and select Convert to Application. Change the Application Pool to Aptify_SOAWeb. Click Test Settings- this will verify your app pool user has access to that folder.

It should as long as it's in the IIS_IUSRS Windows group. If you put your ebusiness6 folder somewhere other than inetpub\wwwroot, you may need to add IIS_IUSRS Security Group to the permissions of that folder.


Changes to update to your environment

Go to the SOA/web.config file. Using NotePad++ or something similar, do a find-and-replace.

Replace the other server's name, (in this screenshot APTIFYDEV) with either your new server name or if you used a Host Name in the binding, the Host Name. Replace All.

If you have multiple HTTPS sites without a different DNS entry, you may need specify the port number if it is different from default value of 443. (This can be found in the Site's binding) If the port was listed as 446, for example, I would replace the value with servername:446

Change the below attribute to point to the database you wish to connect E-Business 6 to- replace the . with the server and instance name.

<add key="Aptify.Framework.LoginServices.AptifyLogin.Server" value="." />

If you need to change the folder/location for Ebusiness uploads, change the upload path of this attribute:

<add key="Aptify.Framework.UploadsPath" value="C:\inetpub\ebusiness6\SOA\Uploads" />

If your Aptify Desktop client is installed somewhere different on this server, you will need to update this attribute line as well with the correct location:

<add key="Aptify.Framework.ObjectRepository.AptifyObjectRepository.DefaultObjectCachePath" value="C:\Program Files\Aptify 5.0" />

Save the web.config file. To ensure your changes were processed, open it in Notepad and verify. If they did not, save a copy to the Desktop, edit there, and then copy over the SOA version.


Go to the UI\js\configuration folder and open ebConfig.js file. Using NotePad++ or something similar, do a find-and-replace just as you did before in the web.config. (Remember to specify port number if it previously applied.)

Save the ebConfig.js file. To ensure your changes were processed, open it in Notepad and verify. If they did not, save a copy to the Desktop, edit there, and then copy over the UI\js\configuration version.

Go back to IIS. If SOA/UI are the only applications under your website, you can just select e-Business6 here and proceed. Otherwise, apply this to both the SOA and UI sites.

Select the SOA site, and click Authentication under the IIS section. Select Anonymous Authentication, and click Edit under Actions in the far right column.

Change it from a specific user to Application Pool identity. Go to the UI site and make the same change.

Restart IIS.

Post deployment items

Confirm it's deployed and working. First, go to https://servername/SOA/Services/CheckConnection to verify the app pools are running and services are working. It should just return a date/time stamp. (If you set this up under a different port, make sure to go to https://servername:444/SOA/Services/CheckConnection)

Then, go to https://servername/UI/  to confirm you can login to the e-Business 6 home page. (If you set this up under a different port, make sure to go to https://servername:444/UI/)


This page includes descriptions on how to deploy Aptify Web, e-Business 5.5.3, or e-Business 6 without using an installer.

Why?

Sometimes it's just simpler to do so. Maybe you can't find the installer, or the installer won't work for some reason, or the installer runs, but it is crashing out midway through.

This page includes instructions on how to manually deploy the websites, as well as what/where settings need to be changed to get it to work. 

All of these assume you have the requisite IIS and server settings already setup and for e-Business 6, the database component installed.

See the Quick List for Setting up and Troubleshooting Aptify Infrastructure page for more details on environment installs (.NET 3.5, .NET 4.5, MVC4, for example) and Windows Features for IIS that are necessary depending on Aptify Web or E-Business:  You should have a basic "Default Web Site" in your IIS.


How to setup the Aptify Web 6.0/6.1 website

In addition to the IIS and server settings mentioned previously, make sure to have installed SQLSysClrTypes.msi and ReportViewer.msi. If you are setting this server up for the first time, you must also install MVC 4 framework.

You may need to add an HTTPS binding to the Default Web Site, if one doesn't exist. In IIS, select Default Web Site and then click Bindings in the far right menu:


If one doesn't appear for HTTPS, add a new one:


The SSL Certificate you use here may be client-specific or you may want to generate a self-signed certificate for testing purposes.

Creating the Application Pools

Go to IIS Manager and select Application Pools. Create two new ones.


Aptify_HTML5Web:

Right-click on the Aptify_HTML5Web Application Pool and click Advanced Settings. Scroll down to Identity, and open the record.

Change the Application Pool Identity from ApplicationPoolIdentity to LocalSystem.


Aptify_SOAWeb

Right-click on the Aptify_HTML5Web Application Pool and click Advanced Settings. Scroll down to Identity, and open the record. Select Custom account and set:

Enter the username (with domain) and password for the user you want to use as an app pool user for Aptify Web and Aptify Web services.

This user must also exist in Aptify and have AptifySOAAppPoolGroup group permissions.
Aptify recommends against using the same account to service Aptify Web SOA as either e-Business Classic, e-Business 6, or your Async Service. It is ok to do so for dev/test purposes, but otherwise, the accounts should all be different. Each requires different levels of permissions and it's recommended to limit each to the minimum-required permissions.

Click OK.

Deploying the pages

Unzip or copy your existing AptifyWeb website to the server. Copy the AptifyServicesAPI and Aptify folders into your C:\inetpub\wwwroot location. (You can change this location to somewhere else if preferred)

When you refresh the Default Web Site, you should see them there now. Right click on Aptify and select Convert to Application.

Change the Application pool to Aptify_HTML5Web. You can otherwise leave as is, unless you put the physical path somewhere else. Click ok.

Right click on the AptifyServicesAPI site and select Convert to Application. Change the Application Pool to Aptify_SOAWeb. Click Test Settings- this will verify your app pool user has access to that folder.

If you have a specific hostname for this site with a DNS entry (e,g, testaptifyweb.aptify.com) you can fill that in the Host Name.

It should as long as it's in the IIS_IUSRS Windows group.

Changes to update to your environment

Go to the AptifyServicesAPI/web.config file. Using NotePad++ or something similar, do a find-and-replace.

Replace the other server's name (in this screenshot APTIFYDEV) with either your new server name or if you used a Host Name in the binding, the Host Name. Replace All.

If you have multiple HTTPS sites without a different DNS entry, you may need specify the port number if it is different from default value of 443. (This can be found in the Site's binding) If the port was listed as 446, for example, I would replace the value with servername:446


Change the below attribute to point to the database you wish to connect Aptify Web to- replace the . with the server and instance name.

<add key="Aptify.Framework.LoginServices.AptifyLogin.Server" value="." />

Change the Object Repository path to wherever you have the Aptify client installed, typically C:\Program Files\Aptify 5.0. It is this attribute:

<add key="Aptify.Framework.ObjectRepository.AptifyObjectRepository.DefaultObjectCachePath" value="C:\Program Files\Aptify 6.1" />

If you need to change the folder/location for Aptify Web uploads, change the upload path of this attribute:

<add key="Aptify.Framework.UploadsPath" value="C:\inetpub\wwwroot\AptifyServicesAPI\Uploads" />

Save the web.config file. To ensure your changes were processed, open it in Notepad and verify. If they did not, save a copy to the Desktop, edit there, and then copy over the AptifyServicesAPI version.


Go to the Aptify\script\Aptify\configuration Aptify.Framework.Configuration.External.js  file. Using NotePad++ or something similar, do a find-and-replace just as you did before in the web.config. (Remember to specify port number if it previously applied.)


Save the Aptify.Framework.Configuration.External.js file. To ensure your changes were processed, open it in Notepad and verify. If they did not, save a copy to the Desktop, edit there, and then copy over the Aptify\script\Aptify\configuration version.


Go back to IIS. If you only have Aptify Web under your site, you can just select the overall site. However, if you have other sites under Default Web site, you will want to do this to the AptifyServicesAPI application and Aptify application separately.

Select the AptifyServicesAPI site, and click Authentication under the IIS section. Select Anonymous Authentication, and click Edit under Actions in the far right column.

Change it from a specific user to Application Pool identity. Go to the Aptify site and make the same change.

Restart IIS.

Post-deployment items

Once deployed, you may want to run several of the HTML5 Generator Process Flows, in particular the Entities and Views to generate this metadata appropriate to your database and system.

If you have any custom .dlls, Crystal Reports, or other objects that need to be run out of Aptify Web, you'll need to copy those into the AptifyServicesAPI\bin folder.


Confirm it's deployed and working. First, go to https://servername/AptifyServicesAPI/services/checkconnection to verify the app pools are running and services are working. It should just return a date/time stamp.


Then, go to https://servername/Aptify to confirm you can login to Aptify Web.


How to setup the e-Business 5.5.3 website

Creating the Application Pool

Go to IIS Manager and select Application Pools. Create one new one.


AptifyEbusiness:

Right-click on the AptifyEbusiness app pool and click Advanced Settings. Scroll down to Identity, and open the record. Select Custom account and set:

Enter the username (with domain) and password for the user you want to use as an app pool user for e-Business services.

This user must also exist in Aptify and have User and Basic group permissions, as well as have an e-Business license.
Aptify recommends against using the same account to service e-Business Classic as either Aptify Web SOA, e-Business 6, or your Async Service. It is ok to do so for dev/test purposes, but otherwise the accounts should all be different. Each requires different levels of permissions and it's recommended to limit each to the minimum-required permissions.

Click OK.

Deploying the pages

Unzip the Ebiz553.zip file and copy the folder into your desired location.


Important

For security reasons, Aptify recommends against putting the e-Business Classic site in the default inetpub\wwwroot location.

When you refresh the Default Web Site, you should see it there now. Right click on ebiz553 and select Convert to Application.

Enter where you copied the files as your location for the physical path. Click ok.

Right click on the ebiz553 site and select Convert to Application. Change the Application Pool to AptifyEbusiness. Click Test Settings- This will verify your app pool user has access to that folder.

It should as long as it's in the IIS_IUSRS Windows group.


Changes to update to your environment

Go to the Ebiz553/web.config file. Using NotePad++ or something similar, change the below attribute to point to the database you wish to connect Aptify Web to- replace the . with the server and instance name.

<add key="AptifyDBServer" value="." />

The other attributes can remain as is, unless you have deployed this to a different location. Then you should modify the following attribute to point to the correct location:

<add key="Aptify.Framework.ObjectRepository.AptifyObjectRepository.DefaultObjectCachePath" value="E:\inetpub\wwwroot\ebiz553\bin" />

Go back to IIS. Select the Ebiz553 Application, and click Authentication under the IIS section. Select Anonymous Authentication, and click Edit under Actions in the far right column.

Change it from a specific user to Application Pool identity. Go to the Aptify site and make the same change.

Restart IIS.

Go to http://servername/Ebiz553 to confirm it's working. (note that it's HTTP, not HTTPS)


How to setup the e-Business 6 GA website

The e-Business6 installer does install some backend updates and framework that are required. Thus, this can only be used currently if you are deploying it on a database that has already had the Ebsuiness 6 backend installer run on it.

e-Business 6 can be deployed to the same server as Aptify Web. If so, you'll need to create a new site other than Default Web Site in IIS named ebusiness6. Right click on IIS and select Add Web Site:

Specify the path where your website will live:

Click OK.

You'll need to specify a different port for HTTP (e,g, 81) and HTTPS (e,g, 446) if you have Aptify Web/Ebiz553 on this server and you do not have separate domain names.

Whether using the Default Web Site or e-Business 6 site, you may need to add an HTTPS binding to the Default Web Site/ebusiness6 site, if one doesn't exist. 


In IIS, select Default Web Site (or ebusiness6) and then click Bindings in the far right menu:


If one doesn't appear for HTTPS, add a new one:


  1. If you are creating an ebusiness6 site alongside Aptify Web on Default Web Site, you will want to change your port to something other than 443, like 444.
  2. If you have a specific hostname for this site with a DNS entry (e,g, testebusiness.aptify.com) you can fill that in the Host Name.
  3. The SSL Certificate you use here may be client-specific or you may want to generate a self-signed certificate for testing purposes.


Creating the Application Pools

Go to IIS Manager and select Application Pools. Create two new ones.


Aptify_EBusinessWeb:

Right-click on the Aptify_EBusinessWeb Application Pool and click Advanced Settings. Scroll down to Identity, and open the record.

Change the Application Pool Identity from ApplicationPoolIdentity to LocalSystem.


Aptify_EbusinessSOAWeb

Right-click on the Aptify_EbusinessSOAWeb Application Pool and click Advanced Settings. Scroll down to Identity, and open the record. Select Custom account and set:

Enter the username (with domain) and password for the user you want to use as an app pool user for Ebusiness6 and Ebusiness 6 services.

This user must also exist in Aptify and have AptifySOAAppPoolGroup group permissions.
Aptify recommends against using the same account to service e-Business 6 as either Aptify Web SOA, e-Business Classic, or your Async Service. It is ok to do so for dev/test purposes, but otherwise the accounts should all be different. Each requires different levels of permissions and it's recommended to limit each to the minimum-required permissions.

Click OK.


Deploying the pages

Unzip the Ebusiness6.zip file and copy the SOA and UI folders into your C:\inetpub\wwwroot location. (You can change this location to somewhere else if preferred)


When you refresh the Default Web Site (or the ebusiness6 site if you set up a separate one), you should see them there now. Right click on UI and select Convert to Application.

Change the Application pool to Aptify_EbusinessWeb. You can otherwise leave as is, unless you put the physical path somewhere else. Click ok.

Right click on the SOA site and select Convert to Application. Change the Application Pool to Aptify_SOAWeb. Click Test Settings- this will verify your app pool user has access to that folder.


It should as long as it's in the IIS_IUSRS Windows group. If you put your ebusiness6 folder somewhere other than inetpub\wwwroot, you may need to add IIS_IUSRS Security Group to the permissions of that folder.


Changes to update to your environment

Go to the SOA/web.config file. Using NotePad++ or something similar, do a find-and-replace.

Replace the other server's name, (in this screenshot APTIFYDEV) with either your new server name or if you used a Host Name in the binding, the Host Name. Replace All.

If you have multiple HTTPS sites without a different DNS entry, you may need specify the port number if it is different from default value of 443. (This can be found in the Site's binding) If the port was listed as 446, for example, I would replace the value with servername:446

Change the below attribute to point to the database you wish to connect E-Business 6 to- replace the . with the server and instance name.

<add key="Aptify.Framework.LoginServices.AptifyLogin.Server" value="." />

If you need to change the folder/location for Ebusiness uploads, change the upload path of this attribute:

<add key="Aptify.Framework.UploadsPath" value="C:\inetpub\ebusiness6\SOA\Uploads" />

If your Aptify Desktop client is installed somewhere different on this server, you will need to update this attribute line as well with the correct location:

<add key="Aptify.Framework.ObjectRepository.AptifyObjectRepository.DefaultObjectCachePath" value="C:\Program Files\Aptify 5.0" />

Save the web.config file. To ensure your changes were processed, open it in Notepad and verify. If they did not, save a copy to the Desktop, edit there, and then copy over the SOA version.



Go to the UI\js\configuration folder and open ebConfig.js file. Using NotePad++ or something similar, do a find-and-replace just as you did before in the web.config. (Remember to specify port number if it previously applied.)

Save the ebConfig.js file. To ensure your changes were processed, open it in Notepad and verify. If they did not, save a copy to the Desktop, edit there, and then copy over the UI\js\configuration version.

Go back to IIS. If SOA/UI are the only applications under your website, you can just select Ebusiness6 here and proceed. Otherwise, apply this to both the SOA and UI sites.

Select the SOA site, and click Authentication under the IIS section. Select Anonymous Authentication, and click Edit under Actions in the far right column.

Change it from a specific user to Application Pool identity. Go to the UI site and make the same change.

Restart IIS.

Post-deployment items

Confirm it's deployed and working. First, go to https://servername/SOA/Services/CheckConnection to verify the app pools are running and services are working. It should just return a date/time stamp. (If you set this up under a different port, make sure to go to https://servername:444/SOA/Services/CheckConnection)

Then, go to https://servername/UI/  to confirm you can login to the Ebusiness 6 home page. (If you set this up under a different port, make sure to go to https://servername:444/UI/)


  • No labels