Screenshots

Step 1.
Create a new user in 2003 for permissions that the ArmA Manager will need. The name is not important, other than you will need to remember which user you used. Have your systems administrator lock down the user from being able to log in remotely or other features you do not want it to have.

Set the permissions for the ArmA folder to allow the new user to have Full Control over the directory.

Add the new user to the Windows/Temp folder permissions (standard permissions are fine).

Step 2.
Create a new Application Pool in IIS. Set the Identity to the new user.

Step 3.
Run "Arma Web Manager Service.msi". Designate the new application pool as the required setting.

Step 4.
Change the settings in the newly created Web Service file "web.config" in IIS.

Location of Mission Files
<add key="FileSaveToLocation" value="D:\ArmA\MPMissions" />

Armed Assault directory
<add key="ArmaLocation" value="D:\ArmA" />

server template to use (place a copy from the Web Service / Resources directory to this specified location so that there is a backup)
<add key="TemplateName" value="server.cfg.Template"/>

File name for the Manager generated config file (will be wiped out every server start, don't place any information in this file)
<add key="ConfigName" value="server.cfg"/>

Location of server profiles for server startup configuration
<add key="ProfileLocation" value="d:\ArmA\"/>

Profile Name to use
<add key="ProfileName" value="server"/>

Step 5.

Restart IIS in order to recycle the application pools.


To verify that the application is running correctly, go to the Manager folder in IIS and 'browse' on 'service1.asmx'.

It should list the possible operations that the web service has available to it.

Last edited Mar 30, 2011 at 2:03 AM by Frankandlolas, version 2

Comments

No comments yet.