Skip to main content
Version: 1.1.4.1

Installation and Initialization

Prerequisites

Check the following before using BotManager .NET Agent.

  1. .NET Version

    • Requires at least .NET 4.0 or higher
    • Supports .NET 4.0 ~ 4.8 versions
  2. Application Architecture

    • Windows-based .NET environment
    • Environment using HTTP or HTTPS
  3. Server Configuration

    • Server must be able to communicate externally via HTTP/HTTPS
    • Network access to https://botmanager.stclab.com is required for communication with macro detection server

Installation Methods

1. Select Domain

Select the domain where you want to install the agent and check configuration values in the BotManager console.

2. Download ZIP File

Download the latest ZIP file from the link below:

Download Link

3. Add DLL File to Project

Add the BotManagerDotNetAgent.dll file from the downloaded botmanager-dotnet-agent.zip file directly to your project. For the Newtonsoft.Json.dll file, it is version 11.0.1, and you only need to add it if you are not using a different version of the file.

File Copy: Copy the BotManagerDotNetAgent.dll file to the project's bin folder (bin|bin/Debug|bin/Release). After copying, add the library through references.

When applying the Newtonsoft.Json.dll file, add the following to the Web.config file.

When Applying Downloaded File

<runtime> 
<assemblyBinding>
<dependentAssembly>
<assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed"/>
<bindingRedirect oldVersion="0.0.0.0-11.0.0.1" newVersion="11.0.0.1"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

When Using Higher Version File

<runtime> 
<assemblyBinding>
<dependentAssembly>
<assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed"/>
<bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="12.0.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

For <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="12.0.0.0"/>, match the oldVersion and newVersion values to the version you are currently using.

4. Initialization

Initialization is required to use BotManager. Add the configuration at application initialization time by referring to the code below.

Code Example:

using System.Web;
using System.Web.Mvc;
using System.Web.Routing;
using BotManagerDotNetAgent.Domain;
using BotManagerDotNetAgent.Config;

namespace MyApplication
{
public class MvcApplication : HttpApplication
{
protected void Application_Start()
{
BotManager.Initialize(new BotManagerConfig.Builder()
.TenantId("{tenant-id}") // Customer identification ID
.DomainName("{domain-name}") // Request domain
.ServerUrl("https://botmanager.stclab.com/api/v1/macro") // Detection server
.ProtectionUrl("https://cdn-botmanager.stclab.com") // Block page URL
.HttpRequestTimeout(1000) // HTTP request timeout (ms)
.LogLevel("ERROR") // Log level
.Build());
}
}
}

customId Configuration

customId is an optional configuration value that can be specified as a value that can identify users in the service page.

Examples:

  • User ID when logged in through login authentication
  • Session value when logged in through login authentication

Key Features and Benefits

  1. BotManager Accessor Management Console Integration:

    • When customId is set, you can check detection information based on specific users identifiable within the service.
  2. Multi-Device Blocking:

    • When a user using the same customId accesses through multiple devices, blocking settings are applied equally to those devices.
    • This prevents blocked users from using multiple devices.

Next Steps

After installation is complete, refer to the following documents: