WebCenter Installation Tips

Licenses

WebCenter Licenses
To install WebCenter 16.1, you will need to request WebCenter 16.1 licenses. The old WebCenter 14.x or 12.x licenses will not work anymore.
WebCenter supports two types of licensing models. You can have counted licenses in the Named User Model and Concurrent License Model where you can have licenses that are taken up during a log-in sessions.
- Named User Licenses: A named user license is an exclusive licensure of rights assigned to a single software user. This License model lets you pay for the number of users you want to create in WebCenter. This means that the purchased number of licenses (per type of users) limit the number of users that can be created. Read more in: Licensing and Users and in this FAQ.
- Concurrent Licenses:
  In this model, you can create as many users as you want. The number of users who may use the system at the same time is determined by your Concurrent Licenses. The licensing model distinguishes between three types of users: guaranteed users, concurrent users, and editor users.
  
  Note:
  Since WebCenter 14.0.2, large installations from 50 concurrent users require a WebCenter Advanced License. A special 'advanced' variant of the concurrent user licenses is also needed in this case.

Network Licensing Tool

For WebCenter 16.1, you need to install ArtiosCAD Enterprise 16.0.1, this installation includes the required Network License Manager.

To know more about Network Licenses, click here..

Server Configuration

Ports
The required ports for WebCenter 12 and later are 1099, 2500, 4444 and 3873.

In case the Viewer service is installed with the option External (new since WebCenter 14), 3 extra ports will need to be opened between the Application and Web Server: 11099, 12500 and 14444.
Database
The database shipped as default with WebCenter 16.1 is MSSQL 2012 Express.
OBGE
In case the OBGE 16.1 is installed on the Web Server (not recommended), make sure to stop the EG Web Server service before starting Tomcat.

Note: Since 16.1, Automation Engine no longer uses Hot Folders explicitly, but you can now configure the FileStore JDF Hot Folder by creating an Access Point which is described in Create a JDF Hot Folder (Access Point) for WebCenter.
IIS

If you move to WebCenter 16.1 from WebCenter 12.x, leaving the installation of IIS intact, a change to IIS may be needed. In IIS, go to Application Pools and open the Advanced Settings for DefaultAppPool. Make sure that ‘Enable 32-Bit Applications’ is set to ‘False’. After changing the setting, click ‘Recycle…’.
Simple or Advanced Installation

Since WebCenter 14, it is possible to choose between a Simple or Advanced installation. If the Advanced installation mode is selected, the memory size allocated for the JBoss service on the Application Server and the TomCat service on the Web Server need to be specified. Choosing the Extra Large option is recommended for servers that are expected to experience a heavy load and high concurrent user access.
Internal or External Viewer

In case of an Advanced installation, the Viewer service can be set to Internal or External. Selecting External will make the Viewer service run as a separate process. Note that choosing External requires extra ports to be opened between the Application and Web Server: 11099, 12500 and 14444.
Database user

In case of an Advanced installation, it is possible to set a custom password for the WebCenter database user.
Boards

Previously, in older versions of ArtiosCAD, the Boards needed to be installed by running a .bat file after the WebCenter installation. Since ArtiosCAD 14.0, you can install the Boards automatically during the ArtiosCAD installation, this is highly recommended.

Servicing

Admin Console
Since WebCenter 14, it is possible to inspect JBoss by going to: http://yourhost:8086/admin-console.
Services
Since WebCenter14, you will only see the following services:
- JBoss
- Tomcat
- CAD-X
The App-X and Search Crawler services are no longer needed since WebCenter 12.

Note: In order to run the services interactively, open the command prompt and go to ..\Esko\Artios\WebCenter\ApplicationServer\NAMEOFSERVICE\bin for each service, and run wcr_nameofservice_srv_cmdrun.bat. For example: C:\Esko\Artios\WebCenter\ApplicationServer\JBoss\bin\wcr_jboss_srv_cmdrun.bat.