Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

These instructions were tested on a clean Windows Server 2012 R2 server


Deploying Artemis On-Premise
Add Server Role
Create a New Website


Anchor
DeployArtemis
DeployArtemis
Deploying Artemis On-Premise

Add Server Role

  1. Add Server RoleWeb Server(IIS).
  2. Under .NET Framework 4.5 Features:
    1. Add ASP.NET 4.5.
    2. CF Services: Add Http activation.
  3. Under Web Server Role (IIS), locate Role Services.
  4. Add Application Development/ASP.NET 4.5. This automatically adds:
    • .NET Extensibility 4.5
    • ISAPI Extensions
    • ISAPI Filters
  5. Install DotNetCore Windows server Hosting.
  6. From Command Prompt, execute net stop was /y followed by net start w3svc.
  7. Remove Default Web Site in IIS Manager.
  8. Create a folder called c:\Artemis.
  9. Create a folder called c:\Artemis\logs.

...

  1. In IIS Manager, create a new website.
    Site name: Artemis
    Physical Path: c:\Artemis
    Hostname: blank 
  2. Edit the new Artemis App Pool.
  3. Change .NET CLR version to No Managed Code.
  4. Extract contents of Artemis.zip to c:\Artemis.
  5. Paste Artemis.zip onto desktop.
  6. Right-click and select Extract All.

    Info

    Files will be extracted to the folder c:\Artemis.


  7. Click Extract.
  8. Edit c:\Artemis\appsettings.json (with Notepad)
    1. Under Application Settings, set WebRoot to appropriate URL to which you will be binding.
    2. Set RequireHttps to True if you will be using HTTPS. If using HTTP, leave it False.

    3. Change LogFilename to c:\\artemis\\logs\\log-{Date}.txt.

      Note

      Note the double backslashes. This is a JSON file, so backslashes have to be escaped like this.


    4. Under ConnectionStrings, change connection string for Artemis to the appropriate connection string to connect to your SQL Server.
      1. If you will be connecting to SQL Server using an Application Pool in IIS that is mapped as a login in SQL Server, Trusted_Connection: True.
      2. If you will be connecting using SQL Auth, use User Id: myUsernamePassword: myPassword instead of Trusted_Connection: True.

Start

...

Artemis

  1. Start the Artemis website.

    Note

    If the website was already running, first stop it.


  2. Browse to http://localhost/sysadmin/Login and login with the initialtinf initiating Username and Password provided by Support.
    1. If you have already created a BLANK Artemis database when you setup your connection string, you will get an error “Invalid object name ‘INFO’” .  Click Initialize Database.
    2. If you do not have a blank database created, you will get an error indicating that it cannot connect to the database.  Click Create Database to create one.
  3. After creating/initializing your database, click Upgrade Database.  You will be prompted for an HPS user account to be the first super-user of the new database. 
  4. If you want to change the sysadmin username or password, click Compute New Password hash and follow the prompts.  You will be given a new password hash. Copy the value, paste it into appsettings.json, and restart the website for it to take effect.
  5. Logout of the sysadmin area using Logout button.
  6. Use the Login button on the main webroot.  You will be redirected to Heartland SSO page. 
  7. Log in using your HPS credentials.

    Info

    Login credintials credentials must be the username you entered above as the initial super-user, but you don’t need the HPS\ prefix or anything, just login as you normally would any Heartland SSO site.


...

Artemis is setup is now complete. 

If Aretmis Artemis is used in conjunction with Vendovation, you will need to follow the next steps to setup the Vendnovation Service wedge.

...