Configuration tasks for certain OS

This section outlines the installation process that are required to be carried out only by the users who use the
following operating systems:

• Microsoft Windows 8

• Windows 8.1

• Windows server 2012

• Windows server 2012 R2

Sections of this chapter:

1.1 Enabling Internet Information Services (IIS) and Windows process
Ac­tivation Services (WAS) 

1.2 Setting up web code 

1.3 Configuring Internet Information Services (IIS) 

1.4 Updating Web.config file 

1.1 Enabling Internet Information Services (IIS) and Win­dows
process Activation Services (WAS)

1. Open the Run window, enter appwiz.cpl and click OK to open Programs and Features
window.

2. On the left pane of the Programs and Features window, click Turn
Windows Features on or off link to open Windows Features pop-up win­dow.

3. In the pop-up window, check Internet Information
Services and Win­dows process Activation Service boxes and
click Ok.

 If IIS and WAS has sub-fields
expand them and check all.

1.2 Setting up web code

1. Open the Run window, enter cmd and click Ok to open the
Command Prompt window.

2. In the Command Prompt window, type whoami and press enter to
gen­erate an output.

3. Username is the output that appears in the following format: Organiza­tion name\User name.

4. Right click AxpertWeb folder and select Properties.
    

5. In the properties window, navigate to the Security tab
and click the Edit button > Add button to open a window to add users.

 > symbol
indicates the sub-folder or file location in the parent folder (Folder name written on the left hand side of the
> symbol).

6. Enter the object names (username, IIS_IUSRS, IUSR) one by one in the text box, click the Check
Names button and click Ok. The added users ap­pear in the Group or
user names section in the same window.

7. Select a newly added user and; in the Permissions for user section,
check Allow box corresponding to Full control field to provide full access rights for
the selected user.

8. Provide full control for all the newly added users and click Apply and Ok.

9. Right click AxpertWebScripts folder and select Properties.

10. Repeat Steps from 5 to 8.

1.3 Configuring Internet Information Services (IIS)

1. Open the Run window, enter inetmgr and click Ok to open
a IIS man­ager/Application pools window.

2. Expand the computername in left pane.

3.On the left pane, right click on Application Pools and select Add
Appli­cation Pool option to open a corresponding window.

4. In the Add Application Pool window, enter Axpert Webscripts in the Name field.

5. Select v2.0.50727 from the .NET CLR Version drop-down.

6. Select Integrated option from the Managed Pipeline Mode drop-down.

7. Check Start Application Pool Immediately box and click Ok.

8. On the right pane of IIS manager/Application pools window, click Ad­vanced
Settings link under Actions section to open a corresponding pop-up window.

9. Under the General section, highlight Enable 32-Bit Applications option and select
True from drop-down list and click Ok.

10. Right click Application Pools in Left Pane and select Add
Applica­tion Pool option.

11. Enter the Name as Axpert Web 10.

12. Select v4.0.30319 from the .NET CLR Version drop-down
list.

13. Repeat Steps from 6 to 9.

14. Expand Sites folder from Left Pane.

15. Right click Default Web Site and select Add Application option.

16. Enter AxpertWebScripts in Alias field.

17. Click the Select button to open Select Application Pool window.

18. From the Application Pool field,
select AxpertWebScripts from the drop-down and click Ok.

19. Click the Browse button adjacent to Physical Path field to select the location of
AxpertWebScripts folder and click Ok.

20. Expand Default Web Site in the left pane and click AxpertWebScripts sub Folder to open Axpert Webscripts Home
pane in the centre.

21. Double click Open Handler Mappings from the center pane.

22. Check if CGI-exe is Enabled,then Go to Step 26 or else, follow further steps.

23. Click CGI-exe in the center pane.

24. Click Edit Feature Permissions in right pane to open a pop-up win­dow.

25. In that pop up window,
select Read, Script and Execute check
boxes and click Ok.

26. Check if ISAPI-dll is Enabled in Center Pane, If enabled Goto Step 29.

27. Click ISAPI-dll in center pane

28. Repeat Steps 24 and 25.

29. Click Computername on the left pane.

30. Open ISAPI and CGI Restrictions in center pane.

31. Click Add in the Right Pane in the Actions window to open a pop up window Add
ISAPI or CGI Restriction.

32. In the pop-up window, click Browse and select ISAPI or CGI path as Webscripts >
ASBAction.dll.

33. In the pop-up window, enter Description as ASBAction.

34. Check Allow extension path to execute box and click Ok.

35. On the right pane of the Actions window, click Add to open a pop up window Add
ISAPI or CGI Restriction.

36. Click Browse ISAPI or CGI path as Webscripts > ASBDefine.dll

37. Enter Description as ASBDefine

38. Repeat step 34.

39. On the right pane of the Actions window, click Add to open a pop up window Add
ISAPI or CGI Restriction.

40. Browse ISAPI or CGI path as Webscripts > ASBIView.dll

41. Enter Description as ASBIView

42. Repeat step 34.

43. On the right pane of the Actions window, click Add to open a pop up window Add
ISAPI or CGI Restriction.

44. Browse ISAPI or CGI path as Webscripts > ASBMenu.dll

45. Enter Description as ASBMenu

46. Repeat step 34.

47. On the right pane of the Actions window, click Add to open Add ISAPI
or CGI Restriction pop up window.

48. Browse ISAPI or CGI path as Webscripts > ASBTStruct.dll

49. Enter Description as ASBTStruct

50. Repeat step 34.

51. On the right pane of the Actions window, click Add to open a pop up window Add ISAPI or CGI Restriction.

52. Browse ISAPI or CGI path as Webscripts > ASBUser.dll

53. Enter Description as ASBUser

54. Repeat step 34.

55. On the right pane of the Actions window, click Add to
open Add ISAPI or CGI Restriction pop up window.

56. Browse ISAPI or CGI path as Webscripts > ASBUtils.dll

57. Enter Description as ASBUtils

58. Repeat step 34.

59. Expand Sites from Left Pane

60. Right Click Default Web Site link and select Add Application option to open Add
Application pop-up window.

61. Enter AxpertWeb in Alias field.

62. Select AxpertWeb from Application Pool drop-down list
and click Ok.

63. Click the browse button adjacent to Physical Path, give the path of Ax­pertWeb
folder and click Ok.

1.4 Updating Web.config file

1. Edit web.config file from AxpertWeb folder in notepad or any other code editor.

2. Find the following keys to update their path :

a) ScriptsPath : Full Path to webScripts Folder ending with “\”

    Eg: <add key=”ScriptsPath” value=”c:\inetpub\wwwroot\AxpertWebScripts\” />

 The
installation directory path which is captured in between two semi­colons (that is ” and “)is dynamic and
represents the Webscripts folder path that the user chose)

b) ScriptsUrlPath : “http://localhost/<Recently added webscripts in iis>/”

    Eg: <add key=”scriptsUrlPath” value=”http://localhost/AxpertWebScripts/” />

c) cloudFilePath : “http://localhost/<Recently added webscripts in iis>/”

    Eg: <add key=”cloudFilePath” value=”http://localhost/Axpert WebScripts/” />

d) ASBIView.ASBIViewservice : “http://localhost/<Recently added web­scripts in
iis>/ASBIView.dll/soap/ASBIView”

     Eg: <add key=”ASBIView.ASBIViewservice” value=”http://localhost/Axpert
WebScripts/AS­BIView.dll/soap/ASBIView” />

e) ASBAction.ASBActionservice : “http://localhost/<Recently added webscripts in
iis>/ASBAction.dll/soap/ASBAction”

     Eg: <add key=”ASBAction.ASBActionservice” value=”http://localhost/Axpert
WebScripts/AS­BAction.dll/soap/ASBAction” />

f) ASBDefine.ASBDefineservice : “http://localhost/<Recently added webscripts in
iis>/ASBDefine.dll/soap/Asbdefine”

    Eg: <add key=”ASBDefine.ASBDefineservice” value=”http://localhost/Axpert
WebScripts/ASB­Define.dll/soap/Asbdefine” />

g) ASBUtils.ASBUtilsservice : “http://localhost/<Recently added web­scripts in
iis>/ASBUtils.dll/soap/ASBUtils”

    Eg: <add key=”ASBUtils.ASBUtilsservice” value=”http://localhost/Axpert
WebScripts/AS­BUtils.dll/soap/ASBUtils” />

h) ASBMenu.ASBMenuservice : “http://localhost/<Recently added web­scripts in
iis>/ASBMenu.dll/soap/ASBMenu”

     Eg: <add key=”ASBMenu.ASBMenuservice” value=”http://localhost/Axpert
WebScripts/ASB­Menu.dll/soap/ASBMenu” />

i) ASBUser.ASBUserservice : “http://localhost/<Recently added web­scripts in
iis>/ASBUser.dll/soap/ASBUser”

   Eg: <add key=”ASBUser.ASBUserservice” value=”http://localhost/Axpert
WebScripts/ASBUs­er.dll/soap/ASBUser” />

j) ASBTStruct.ASBTStructservice : “http://localhost/<Recently added webscripts in
iis>/ASBTStruct.dll/soap/ASBTStruct”

   Eg: <add key=”ASBTStruct.ASBTStructservice” value=”http://localhost/Axpert
WebScripts/ASBT­Struct.dll/soap/ASBTStruct” />

k) ASBTStruct.ASBRapidTStructservice : “http://localhost/<Recently added webscripts
in iis>/ASBRapidTStruct.dll/soap/ASBRapidTStruct”

    Eg: <add key=”ASBTStruct.ASBRapidTStructservice” value=”http://localhost/Axpert
Web­Scripts/ASBRapidTStruct.dll/soap/ASBRapidTStruct” />