Professional Documents
Culture Documents
2016
Installation and Administration
Guide
This is a publication of Sage Software, Inc.
Sage, the Sage logos, and the Sage product and service names mentioned herein are registered
trademarks or trademarks of Sage Software, Inc. or its affiliated entities. All other trademarks are
the property of their respective owners.
Business Objects® and the Business Objects logo, BusinessObjects®, and Crystal Reports® are
trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in
other countries. Business Objects is an SAP company.
Microsoft ®SQL Server®, Windows Vista® and the Windows logo are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or in other countries.
The names of all other products and services are property of their respective owners.
Your use of this document and the Sage product(s) described herein is governed by the terms and
conditions of the Sage End User License Agreement ("EULA") or other agreement that is provided
with or included in the Sage product. Nothing in this document supplements, modifies or amends
those terms and conditions. Except as expressly stated in those terms and conditions, the information
in this document is provided by Sage "AS IS" and Sage disclaims all express, implied or statutory
warranties of any kind, including but not limited to the warranties of merchantability, fitness for a
particular purpose or of non-infringement. No implied license is granted to you under any Sage
intellectual property or trade secret right. Sage reserves the right to revise, supplement or remove
information in this document at any time without notice to you or others.
Chapter 1: Introduction
System Requirements ..................................................................... 1–1
Network Configuration ..................................................................... 1–2
Typical Network Configurations ........................................................ 1–3
Where To Now? ............................................................................ 1–7
iv Sage 300
Chapter 7: Licensing Sage 300
Licensing Products and Users .............................................................. 7–1
LanPak Licenses ........................................................................ 7–2
Creating a Temporary LanPak License ..................................................... 7–2
Requesting Activation Codes ............................................................... 7–4
Updating Your Sage 300 Licenses ......................................................... 7–5
Viewing License Information ........................................................... 7–7
Monitoring LanPak Activity ................................................................. 7–7
System Requirements
Before you can install Sage 300, your hardware and your operating
system must be correctly configured and fully operational.
Network Configuration
You can configure Sage 300 in a number of ways. The best configuration
for your company depends on the number of users who need to use Sage
300 programs and data concurrently, and your network setup.
• Server — The computer that hosts the Sage 300 data, and optionally,
Sage 300 programs.
Sage 300 works with the Microsoft SQL Server database engine only.
− Site folder.
− User folder.
− Data.
− Company folder.
• Single computer.
• Client-server network.
If more than two users require concurrent access to Sage 300 data or
programs, the workstation acting as the server should be dedicated. You
may encounter performance issues if you run Sage 300 on the server at
the same time as other users are accessing Sage 300 from their
workstations.
The optional Terminal Server may also reside on the same physical server.
Note:On each workstation that will run Sage 300 programs locally,
you must install System Manager and the accounting applications.
• If you use a Citrix server, there are some special considerations. For
more information, see the Sage 300 Intelligence Reporting Citrix
Installation Guide.
When you deploy Sage 300 on the Web, all Sage 300 programs are
installed on a Web server, and data is typically stored on a separate
server.
For more information about deploying Sage 300 on the Web, see
Chapter 8 in this guide.
In the illustration below, we’ve shown Web deployment, with the Sage
300 Web server and the Sage CRM Web server on separate computers.
Note:The Sage 300 and Sage CRM Web server can reside on the
same computer. Typically, one database server stores both the
Sage CRM and Sage 300 data.
Recommendation For better security and performance, do not store shared data on the Web
server.
For more information about integrating Sage 300 with Sage CRM, see the
Sage CRM Integration Guide.
Where To Now?
You are now ready to install Sage 300.
Installation Considerations
Read the following sections before you install Sage 300.
• If more than two users require concurrent access to Sage 300 data or
programs, the workstation acting as the server should be dedicated.
You may encounter performance issues if you run Sage 300 on the
server at the same time as other users are accessing Sage 300 from
their workstations.
• On the workstation that will be acting as the server, share the Sage
300 Program and Shared Data folders, as follows:
Sage 300 is a 32-bit program. When you create a data source for Sage
300, you must use the 32-bit version of the ODBC Administrator.
You can bring the power of Sage 300 to your web browser with web
screens or the Portal — a program that provides a browser-based and
customizable interface for Sage 300, with graphical presentations of key
financial data.
Note: On any single server, you can install the web screens or the
Portal, but not both. To install the web screens and the Portal, you
must have two servers.
If you intend to install the Sage 300 web screens or Portal, you must first:
If IIS is not installed, install it before you attempt to install the Sage
300 web screens or Portal.
• After installing the Sage 300 Portal, you need to configure it to make it
secure. For more information, see Chapter 5, “Configuring the Sage
300 Web Screens or Portal.”
• General Ledger
• Accounts Receivable
• Accounts Payable
• Inventory Control
• Order Entry
• Purchase Orders
• Payroll (US or Canadian)
• Project and Job Costing
You can choose to install sample data when you install Sage 300.
6. Click the option to accept the license agreement, and then click Next.
7. Select the geographical region where you are installing the software,
and then click Next.
8. For the client information, enter your 7-digit or 10-digit client ID and
the company name to use for registration, and then click Next.
9. For the optional information, enter a contact person, your dealer, and
certified consultant, and then click Next.
10. Select the edition of Sage 300 you require, and then click Next.
11. Specify the names and locations of your program and data folders, and
then click Next.
Note: Be sure to install Sage 300 outside the default path (for
example, C:\Sage\Sage 300). Also, to use web screens, you must
specify the full path for the shared data folder (do not specify a
mapped drive) and a local path for the programs folder (do not
specify a mapped drive or a UNC path).
13. On the next screen, in the Program Folder field, type the location on
the Start menu where you want Sage 300 to appear, then click Next.
1. If you have activation codes for your Sage 300 programs, click the
Licenses tab, then, for each Sage 300 program:
a. Double-click in the Serial Number column, and then enter the serial
number.
If you don’t yet have activation codes, you can use the 30-day
temporary licenses created during installation, and record the
permanent code later, as described in Chapter 7, “Licensing Sage
300.”
Note: The system allows you to register only one LanPak license. If
a temporary LanPak license exists for this version, skip to step c,
and then follow the remaining instructions to enter your permanent
registration on the existing line.
a. Right-click the grid, and then select Insert from the menu that
appears. The new entry shows your current Sage 300 version and
edition.
b. In the new line, double-click the License Type column, and then
select LanPak from the list.
c. Double-click in the Count column, and then type the total number
of users who require Sage 300 access for this installation. (The
count is the sum of existing users plus the new users for whom
you’re adding LanPak licenses.)
If you have a permanent license for this version, and you are asked
if you want to overwrite the existing license, click Yes.
For Sage 300 Intelligence Reporting, one Report Manager license for
one user is free with Sage 300. If you have additional licenses for
Report Manager and Report Viewer, enter their activation codes in the
Activation Code column.
4. Click Close.
Setting Up Workstations
You must run Workstation Setup on each workstation that will run Sage
300 programs from a server, including programs opened through the Sage
300 Portal.
In this case, install Sage 300 System Manager and the accounting
applications on the workstation as described in Chapter 2 of this guide.
• The workstation is a Web client, and will access Sage 300 programs
and data through an Internet browser.
In this case, deploy Sage 300 on the Web and follow the client setup
instructions described in Chapter 7 of this guide.
Setting Up a Workstation
1. Share your Sage 300 program folder, with at least the following
permissions for users:
− Read
2. Share your Sage 300 data folder, with Full Control permission for
users.
a. Locate the setup.exe file for the utility. By default, it is in the Sage
300 program folder on the server where you installed Sage 300:
\\<server>\<program folder>\WSSetup\setup.exe
5. Enter the paths for your shared program folder and data folder.
If you use workstation setup, you must also run Sage 300 Intelligence
Reporting workstation setup (located in BX62A\WSSetup) on every
workstation where you will view and use Intelligence Reporting screens.
Where To Now?
New installation If you are installing Sage 300 for the first time, you need to create system
and company databases using supported database software, and then set
up the databases for use in Sage 300.
If you plan to use the Sage 300 web screens or Portal, you must also
create a portal database in Microsoft SQL format.
To get the most recent list of supported database versions, see the
Compatibility Guide:
https://support.na.sage.com/selfservice/viewdocument.do?externalId=26
777
After you have created the databases using your database software, use
the Database Setup utility to set up the databases for Sage 300.
Note that the portal database is shared by all companies in a Sage 300
installation, and you can set up only one Sage 300 Portal.
Database ID Sage 300 uses a Database ID to identify databases. Each ID is a unique
code of uppercase characters, consisting of letters from A to Z, or
numbers from 0 to 9, or any combination of letters and numbers.
For simplicity, we recommend that the Database ID, the database, the
folder for the database, and the Data Source Name (DSN) be identical.
3. Accept the Server name that is displayed (the name of the computer
you are currently working on).
6. In the Object Explorer panel, expand the folder tree for the SQL
Server, and then expand the Databases folder tree.
7. Right-click Databases, and then select New Database… from the menu.
8. In the Database name field, type the 6-character name for the system
database.
a. In the Initial Size column, specify the amount of disk space that
SQL Server will initially reserve for the Sage 300 database. For new
databases, use the default value.
2. Right-click Logins and then click New Login… from the right-click
menu.
3. In the Login name field, type a name for your new SQL Login ID.
In the Object Explorer, your new Login name appears within the
Logins folder.
a. In the Object Explorer, expand the Logins folder, and then double-
click the new Login name you created.
b. In the left pane, click Server Role, and in the right pane, select
sysadmin.
If you are using a DSN to connect to your SQL databases on the server,
on all client workstations, create an ODBC connection to your databases.
Important! If you do not create a Data Source (DSN) to connect to your databases,
Sage 300 can connect to the SQL Server directly using the server name
and default settings.
Sage 300 is a 32-bit application. When you create a data source for
Sage 300, you must use the 32-bit version of the ODBC Administrator.
3. Select SQL Server Native Client 11, and then click Finish.
Note: When creating the DSN for a portal database, if you specify
a named instance of SQL Server, be sure to append the database
port number, or you may have trouble printing reports from the
portal. For example, specify SERVER\INSTANCE,1433. (If you use a
nonstandard port, specify that number instead of 1433.)
c. In the Login ID field, type in the SQL Login ID and password that
you created in the previous section.
7. Click Next.
8. Select the option Change The Default Database To, and then select
Database For This Connection. Leave the other fields at their default
values.
9. Click Next, and then Finish to create the ODBC data source.
10. Click Test Data Source to test the connection to the database.
Where To Now?
Now that you have created system and company databases in your
database management system, you need to set them up for use with
Sage 300, as described in the section “Setting Up Company and System
Databases,” later in this chapter.
Change ADMIN After creating your databases and activating your applications,
password
change the ADMIN password to prevent unauthorized use of
Sage 300. It is important that other users do not have access to the
system administrator’s tasks.
4. In the Database ID field, enter the name of the DSN you created for
the system database.
6. Click OK.
7. Fill in the fields on the Edit Database Profile form that appears:
b. Click the Data Source option, and then select the data source name
from the Data Source field, or specify the server name for the
database in the Server field. (Only data sources you created on
your workstation appear in the list.)
Note that the names of the data sources must be consistent on all
workstations that use the same shared Data directories.
Remember, also, to type the name with the same capitalization
that you used to define it with the ODBC Administrator.
c. Enter the SQL Login ID that you created for all Sage 300 users.
Warning Make sure you enter the SQL Login ID correctly because you will
not be able to change it after you save the database profile.
d. Enter the Password for the Login ID you entered in the previous
field.
When users sign on to Sage 300, the System Manager verifies their
Sage 300 passwords, then logs onto SQL Server using the Login ID
and password specified here. Individual Sage 300 users do not
need Login IDs for SQL Server.
e. Enter the name of the database you created as the Sage 300
system database. Make sure you use the same capitalization that
you did when you defined it with the SQL Enterprise Manager.
g. Click OK.
On the Edit Database Profile form, you can change the color assigned to a
specific company, or turn off the company color option for that company.
If you want to clear all colors, click the Clear All Colors button on the
Database Setup form.
4. In the Database ID field, enter the name of the DSN you created for
the company database.
7. Click OK.
8. Fill in the fields on the Edit Database Profile form that appears:
b. Click the Data Source option, and then select the data source name
from the Data Source field, or specify the server name for the
database in the Server field. (Only data sources you created on
your workstation appear in the list.)
Note that the names of the data sources must be consistent on all
workstations that use the same shared Data directories.
Remember, also, to type the name with the same capitalization
that you used to define it with the ODBC Administrator.
c. Enter the SQL Login ID that you created for all Sage 300 users.
Warning Make sure you enter the SQL Login ID correctly because you will
not be able to change it after you save the database profile.
d. Enter the Password for the Login ID you entered in the previous
field.
e. Enter the name of the database you created as the Sage 300
company database. Make sure you use the same capitalization that
you did when you defined it with the SQL Enterprise Manager.
f. If you want to assign a color to the company, click the Select Color
button, and then select a color. This color appears in a border
around Sage 300 screens when you sign in to this company,
making it easier to see which company’s information you are
viewing and avoid data entry errors.
g. Click OK.
The options you set affect both company and system databases.
2. Sign in as ADMIN, and then click OK to open the Database Setup form.
The Database Setup form lists the system and company databases
that have been created.
Lock out user after [ ] attempts. Enter the number of times a user
can enter an invalid password before they are locked out of the
system. When a user is locked out, they can wait for the lockout
period to expire before attempting to log in again, or the System
Administrator can clear the option, allowing the user to attempt to log
in again.
Note: If you restrict the hours a user can sign in to Sage 300, it is
important to use a time server to maintain this security.
5. Click OK to save your changes and return to the Database Setup form.
Where To Now?
You can now sign on to your new company, create the company profile,
and activate your data for the current version.
If you set up a portal database (recall that you must use Microsoft SQL
Server — Express or full Edition, to create your portal database), you need
to configure it, as described in Chapter 5, “Configuring the Sage 300 Web
Screens or Portal.”
If you use 13 periods, decide which quarter will contain four fiscal
periods.
Functional currency • Your company’s functional currency — that is, the currency in which
your company keeps its books.
The functional currency applies to all Sage 300 applications for the
company (such as Accounts Receivable, Accounts Payable, and
Payroll).
Determine the rate type your company uses most often to convert
amounts entered in another currency to the functional currency
• If this is the first time you are using a new system database, Sage 300
prompts you to activate Administrative Services. The activation
process creates currency and security tables, installs standard
currency codes and rate types, and places the Administrative Services
icon on the Sage 300 desktop.
• The first time you open a new company, Sage 300 prompts you to
activate Common Services. When you activate Common Services, the
program creates tables to store company-wide information, displays
the Company Profile, and places the Common Services icon on the
Sage 300 desktop.
1. From the Windows Start menu, select All Programs > Sage 300 >
Sage 300. The Open Company form appears.
Sign on with the 2. In the User ID field, type ADMIN. This is the ID for the system
ADMIN user ID
administrator, the only person authorized to set up a new company.
3. If you selected the option Enable Application Security when you set up
the system database, enter the system administrator’s password.
Company 4. From the Company list, select the name of the new company.
The list contains the names of all company databases you created for
Sage 300, as well as the names of sample companies, if you installed
sample data.
Session date 5. In the Session Date field, type the date of your work session (or accept
the default). This date will be the default Fiscal Year Starting Date
when you activate Common Services for the company.
If the system database is being used for the first time, the following
form appears:
7. Type the starting date of your company’s current fiscal year in the
Fiscal Year Starting Date field, if it is different than the default date.
Sage 300 creates this fiscal year in your company calendar.
9. After Common Services has been created and initialized, the Common
Services Activation form appears, as follows:
If you click Cancel, you return to the Open Company form. When you
next start Sage 300 for this company, you are asked to activate
Common Services.
10. When you are satisfied with the company profile information, click OK.
• Address. Displays the database ID and the name of the company you
selected when you signed on. It includes fields for the address,
telephone and fax numbers, and contact name.
Doing Business As. Type the company’s name, exactly as you want
it to be on all reports, financial statements, customer statements, and
invoices. You can use up to 60 characters, including letters, digits,
symbols, and punctuation. The default entry is the description from
Database Setup.
City. Type the name of the city where the company is located.
Except for the database ID, you can change any of the entries on this
tab at any time.
Changing fiscal
periods later not IMPORTANT: If you change the number of fiscal periods, later, you
recommended will not be able to compare amounts between years that have
different numbers of fiscal periods.
Editing fiscal The number of fiscal periods you select determines the lengths of the
periods
default periods on the fiscal calendar. If your fiscal periods vary in
length, or if you have a 12-period fiscal year, which does not start on
the first day of the month, you need to edit the dates in the Fiscal
Calendar form after you create the company profile.
Locked Fiscal Period. Select None, Warning, or Error from the list. If
you select Error, subledgers and Bank Services prohibit transactions
from being entered or posted to a period that is locked.
Inactive G/L Account. Select None, Warning, or Error from the list.
If you select Error, subledgers and Bank Services prohibit entries to a
General Ledger account that has been flagged as Inactive.
Country Code and Branch. You can type six-character codes for
country and branch.
Multicurrency Multicurrency. Select this option if you will enter, retrieve, import,
ledgers
post, and report transactions in more than one currency.
To select from the list of supplied codes, click the Finder beside the
Functional Currency field, then double-click the code for your currency.
If the code for your functional currency is not in the list, click the New
icon beside the Finder, and then enter the international code for your
currency.
You cannot change
the functional Note: You cannot change the functional currency code after you
currency save the company profile.
3. If you selected the Multicurrency option, fill in the following fields that
appear on the Options tab:
Default Rate Type Default Rate Type. If you use multicurrency accounting, you must
select one of the rate types supplied with Sage 300, or add a new one.
To view a list of defined rate types, click the Finder beside the Default
Rate Type field, then double-click a rate type from the list.
Euro option Euro. Select the Euro option if your functional currency is the euro,
but your company wants to produce reports in the national currency of
a member country of the EMU.
Reporting currency Reporting Currency. If you selected the Euro option, you must enter
a currency code in this field. Reports will print in both the reporting
currency and the euro.
4. When you are satisfied with the company profile information, click OK.
b. Click the License Manager button, and then enter the required
serial numbers, activation codes, and expiry dates (if applicable)
on the licenses tab of the License Manager form.
2. When asked whether you are ready to proceed with activation, click
Yes.
3. Select the check box beside each application for which you want to
activate data.
The following form appears, showing the settings that will be used for
any options that are required to activate a program:
If you are unsure about a setting, and prefer not to activate the
program at this time:
b. Clear the check box for the program on the previous screen.
The following form appears, showing you the status of the applications
you selected for activation:
7. Click Activate.
Once you finish activating Sage 300 programs, we recommend that you
change the password for the ADMIN user to prevent unauthorized access
to your company data.
To restrict user access by password, you must first select the option to
Enable Security for the system database, if you have not already done so.
1. On the Windows Start menu, select All Programs > Sage 300 >
Database Setup.
2. In the Sign-On form that appears, type ADMIN for the password, and
then click OK.
3. In the Database Setup form, select the system database, and then
click Edit to display the Database Profile.
You can also change the password in the ADMIN user’s record once you
open the company:
2. Type the new password in the Password field, and then type it again in
the Verify field.
Where To Now?
You can now:
Note: On any single server, you can install the web screens or the
Portal, but not both. To install the web screens and the Portal, you
must have two servers.
Web screens Sage 300 web screens are modernized versions of the classic Sage 300
desktop screens, which you use in a web browser. Web screens and
desktop screens run in parallel.
Portal The Sage 300 Portal was designed to make Sage 300 easy to learn and to
use.
• Troubleshooting problems.
Overview
Before you can use the Sage 300 web screens or Portal, you must:
1. Install the current version of Sage 300, including the web screens or
portal components.
2. For the Portal only (this step is not required to use the web screens),
run Workstation Setup on each workstation that will use the Sage 300
portal, if:
And
3. Activate your company data for the Sage 300 programs you use.
The portal database stores files used by the Sage 300 web screens and
Portal. For the Portal, these include user preferences and passwords,
snapshot configurations, and other files that determine how the Portal
looks and functions.
If you create the portal database using SQL Server Express, you will
need to configure a TCP/IP connection manually in that program. For
more information, see, “Configuring a Microsoft SQL Server Express
Database,” later in this chapter.
IIS:
b. Turn on HTTPS by adding an HTTPS binding (in the binding you will
specify your SSL certificate).
Note: When you turn on HTTPS, all URLs for the portal are changed
to begin with https instead of http. This invalidates any existing
links to the portal.
Other:
• Use a firewall.
If you have any concerns about security, contact your Sage business
partner.
Then, you must configure the Portal to establish a connection to the portal
database.
1. From Windows’ Start menu, select All Programs > Sage 300 >
Database Setup.
3. On the Database Setup form that appears, click the Portal button to
open the Configure Portal form.
• Database ID. Enter the name specified for the portal database in
your database software.
5. Click OK, and then click Exit to close the Database Setup form.
Portal configuration The program saves the portal configuration to a file named
file
dbConnection.xml, located in the following folder under Program Files:
If you set up the portal database using SQL Server Express, follow the
steps in the next section, “Configuring a Microsoft SQL Server Express
Database.”
2. Under the SQL Server Network Configuration tree, click Protocols For
SQLEXPRESS.
If the TCP/IP connection is set up correctly, the screen will clear, and you
will be in a Telnet session with the SQL Server.
1. On the machine where the Sage 300 Portal is installed, click Start >
Search Programs And Files, and then type intl.cpl.
c. Click OK.
f. Click OK.
The user account must have access to the Sage 300 shared data folder.
Also note that the account’s regional settings will determine the language
in which some content and messages appear in Sage 300.
3. Select a company.
On the Windows Start menu, click All Programs > Sage 300 > Portal.
Troubleshooting
The Sage 300 installation program installs components that support the
Sage 300 web screens and Portal, and it sets properties that are required
in Internet Information Services (IIS). You shouldn’t have to change
them. The information and tips in this section are provided in case you
have problems with IIS after installation.
• Portal components are saved to the WebUIs subfolder of the Sage 300
program folder. These files support the Portal interface, and include
HTML, Javascript, CSS, and PNG files.
These instructions assume you need to create the Sage 300 application
pool and the Sage300ERP and SDataServlet applications. If these
components already exist in IIS, check to ensure that the configuration
settings are correct.
b. Click OK.
Set advanced 3. Select Application Pools > Sage 300 ERP App Pool, and then on
properties
the Actions panel, under Edit Application Pool, click Advanced
Settings.
Enable 32-bit a. Confirm that Enable 32-Bit Applications is set to True.
applications
Set ISAPI & CGI 4. In the Connections panel, select the current server, and then
Restrictions
double-click the ISAPI & CGI Restrictions icon.
a. Under Actions, click Add, and then on the form that appears:
b. Set the application pool to Sage 300 ERP App Pool, and then
click OK to return to the Add Application form.
c. Set the physical path to the Apache Tomcat Connecter, located at:
<Program Files>\Common Files\Sage\Sage 300
ERP\Tomcat\Jakarta.
d. Click OK.
Add the 8. On the Connections panel, right-click Default Web Site, and then
Sage300ERP
click Add Application. In the form that appears:
application
a. For the Alias, type Sage300ERP.
b. Set the application pool to Sage 300 ERP App Pool, and then
click OK to return to the Add Application form.
c. Set the physical path to the webuis subfolder in your Sage 300
program folder.
d. Click OK.
Add the ISAPI filter 9. On the Connections panel, select the Default Web Site, and then
double-click the ISAPI Filters icon.
d. Click OK.
Restarting IIS
Clicking Stop and Start IIS in Administrative Tools’ Internet Information
Services form does not restart IIS properly.
2. Right-click your IIS Service (for example, IIS Admin), and then click
Stop on the menu that appears.
3. Once the service has stopped, right-click, and then click Start.
2. Right-click the Sage 300 ERP Tomcat service, and then click Start.
One process that might be using port 80 is Skype. If this is the case, you
can re-configure Skype so that it will not use port 80 as its default, as
follows:
3. Click Connection.
5. Click Save.
2. On the Security tab, select Local Intranet zone or the Trusted Sites
zone, and then click the Sites button.
3. If you selected the Local Intranet zone, click the Advanced button on
the next screen that appears.
4. In the Add this Website to the Zone field, type name of your portal
server, and then click Add.
• Is the isapi dll set up correctly? Does it have execute and write
permissions?
Perform these procedures at any time after you have installed Sage 300
programs. Sign on as the ADMIN user at any server or workstation that
runs Sage 300.
Add Users
For each user, assign an ID and set up individual security options.
Note:If you select Timecard, you must create a security group for
employees who only enter timecards, later.
5. Select the language in which to display and print this user’s messages,
Help, reports, and forms.
Note: If you use Sage 300 web screens, users may need to select
this language in their web browser settings as the preferred
language for viewing web pages.
Sage 300 — allows the user to sign on using only their Sage 300 User
ID.
Windows — allows the user to sign on using their Windows User ID.
Both — allows the user to sign on using either their Windows User ID
or their Sage 300 User ID.
7. In the Job Role field, select the role that most resembles this user’s
job role. If you leave this field blank, the user is prompted to select a
role when they sign in to Sage 300.
You can click the Browse button to select from a list of Windows users
and domains.
When you type a password, Sage 300 displays asterisks. You must
enter a password in each user record. However, if security is not
turned on for the system database that the company uses, users are
not asked for the password when they start Sage 300.
10. Assign additional security to the password, selecting from the following
options:
Account Is Locked Out — locks out the user after they exceed the
maximum number of attempts specified in the advanced security
settings for the system database. The system assigns this status, and,
depending on the security settings, can clear this status after a certain
period. The ADMIN user can also clear this status.
11. If you selected the option to restrict the user’s account, in the Valid
Times section, specify the days of the week and the hours that the
user can sign on to Sage 300.
13. Select the User receives e-mail from Sage with information
relevant to job role option to indicate that this user consents to
receive e-mail from Sage.
Normally, when a user signs on to Windows with their user name, domain,
and password, the server uses this information to authenticate the user. If
the user then signs on to Sage 300 with the same ID and domain, they do
not need to provide a password.
The following fields are not available in the User record when you select
Windows as the authentication method:
If you are changing the authentication method for an existing user, any
previously assigned passwords are cleared, and therefore no longer valid.
• A field for the Windows Domain name. (This field appears only if the
particular user’s record specifies Windows authentication.)
If the Sage 300 authentication method is assigned to all users, the Open
Company dialog box displays the Windows Authentication check box, but
it is not available to any users, including the ADMIN user, from the
Sage 300 desktop. (On the Sage 300 Web desktop, this option is always
available.)
Sage 300
Authentication
Method Option disabled
When a user selects the Windows Authentication option, the Domain field
appears, as follows:
Windows
Authentication
option selected,
Domain field
displayed
By default, the Domain and User ID fields display the domain and user ID
for the currently logged-in Windows user, if their Sage 300 User ID has
been mapped to a Windows user account.
Password fields The Password field and the Change Password button are always disabled
disabled
for Windows Authentication.
The Both authentication setting allows a user to sign on to Sage 300 using
either their Sage 300 ID and password or their Windows User ID.
When you create security groups, you specify the tasks that each group
can perform. All companies using the same system database share
security groups.
• To remove a task that has already been selected, click the check
box to clear it.
5. Click Add.
Now, you can users to these security groups, as described in the next
section.
Authorizing Users
You assign each user to one security group for each application. All users
in the same group can perform the tasks defined for the group. The same
user can be assigned to different groups within the same company.
3. For each application to which you want to allow access for this user:
5. When you have finished assigning security groups to all users, click
Close.
1. Determine the fields a user will not need when using certain forms and
dialog boxes.
3. Create your User IDs. (See previous sections for the steps.)
4. Open the form that you are customizing for a user. (In our following
examples, we chose Currency Codes.)
The Customize screen displays a list of the controls that can be hidden
for the dialog box or form that you started from (for our example, the
Currency Codes dialog box). To hide some of these controls for users,
you must either select an existing profile or create a new one. In the
following steps, we explain how to create a new profile.
8. Click checkmarks beside the controls for the fields to hide. The
checkmarks disappear, as shown next:
Field to be hidden
9. Click Save, then click OK to return to the dialog box you customized.
(In our example, we return to Currency Codes.)
After creating a UI Profile ID, you assign users to it. You can create as
many Profiles as you need, and assign each user to a different Profile. You
can assign more than one user to each Profile ID.
If you have not assigned any UI Profiles to users, the Assign UI Profiles
form has no entries in the grid, as shown below:
2. Click the Finder in the User ID column, highlight a User ID from the
list, and click Select.
3. Click the Finder in the Profile ID column to choose a Profile from the
list.
Each time you open the Assign UI Profiles screen, the grid displays all
User IDs and Profile IDs previously assigned.
The next time the selected user opens the form that has been restricted,
the fields hidden in the Working Profile will not appear.
Note that:
i. Click your Sage 300 version, and then click Change. (Do not
double-click.)
ii. Click Modify, and then use the Select Features screen to select
the programs you want to install and clear the selections for
programs you want to remove.
• Enter activation codes for user LanPaks, and for Report Manager and
Report Viewer for Sage 300 Reporting Intelligence.
Until you enter activation codes, whenever you sign on to your company
database, Sage 300 will display an Unregistered Applications message to
remind you to register the programs.
Once you receive valid serial numbers and activation codes, you enter
them in the License Manager to make the licenses permanent.
You require a Installation does not generate temporary LanPak licenses, however.
LanPak license to
LanPak is Sage 300’s user licensing system. Without a LanPak license, no
use Sage 300
one — including the ADMIN user — can sign on to a company.
Normally, you enter the activation code for your LanPak license as part of
program installation. (When the installation program finishes, it displays
the License Manager, where you enter the activation code for your LanPak
on the Users tab.)
After you change the company name in the License Manager, the
activation code will be marked Unauthorized. The license will
remain valid, but you should apply for another activation code for
the new company name.
The following sections describe LanPak licenses in more detail, and explain
how to create a temporary LanPak license if you did not enter an
activation code for a LanPak when you installed Sage 300.
LanPak Licenses
A LanPak license regulates how many users can work with a particular
version of Sage 300. The number of LanPak licenses you require depends
on the number of workstations on which you install Sage 300 and the
number of users who will access company databases on those
workstations.
Note: One LanPak is required for each user that opens a Sage 300
database from a workstation. A user can open multiple databases
from the same workstation providing they use the same Windows
user profile.
2. Click the Users tab, and then click in the blank space to create a new
line. (If there are existing lines, right-click in the blank space, and
then click Insert.)
a. Click the License Type column, and then select LanPak from the list
that appears.
b. Click the Count column, and then enter the number of users that
require concurrent access to Sage 300.
You can obtain activation codes from the Sage Customer or Partner Portal.
4. Follow the instructions on the My Products tab to display and print the
Details Sheet.
5. On the Details Sheet, click the Products Details tab to view the
customer’s activation codes.
• View license information for your Sage 300 programs, including the
number of users authorized by the LanPak license.
• Enter serial numbers, activation codes, and expiry dates (if applicable)
for the Sage 300 programs and services that your company is using.
• When necessary, change the company name to which your Sage 300
software is registered (for instance, after a merger).
The License Manager form appears during program installation, letting you
enter serial numbers, activation codes, and expiry dates (if applicable) for
any new Sage 300 programs and LanPaks that you are installing.
You can also open the License Manager, later, if you need to add or
change any licensing information. If you don’t enter LanPak information
during installation, for example, the program prompts you to enter it in
the License Manager form.
1. From the Help menu on the Sage 300 desktop, click Licenses.
2. On the Licenses form that appears, click the License Manager button.
If you need to change the company name to which your Sage 300
software is registered, you click the Change button, and then type
the new name in the Company field. When you next open the
License Manager form, the company field will be disabled, unless
you click Change again.
You must enter the Serial Number and the Activation Code, in
order, for each Sage 300 product you want to register:
i. Click in the Serial Number column, and then type your serial
number for the selected product.
ii. Click in the Activation Code column, and then type the
activation code for the product.
iii. For subscription licenses, click in the Expiry Date column, and
then type the expiry date.
You must enter information for each LanPak user in this order:
ii. Click in the Count column, and then enter the number of users
that require concurrent access to Sage 300.
iii. Click in the Serial Number column, and then type your serial
number for the selected product.
iv. Click in the Activation Code column, and then type the
activation code for the product.
Note: You also use this tab to record activation codes for additional
licenses for the Report Manager and the Report Viewer in single-
user increments. (One Report Manager license — for one user — is
free with Sage 300.)
On the Sage 300 desktop, from the Help menu, click Licenses.
Viewing details for • To see information for a single license, select the product on the list,
a single license
and then click the License Info button (or double-click the product
name).
Viewing details for • To see information about users currently signed in to Sage 300,
LanPak and IAP
including third-party products you are using that integrate with Sage
license use
300, click the Current Users button.
Updating product • To see details for all Sage 300 licenses and LanPaks, or to update
or LanPak licenses
licensing information, click the License Manager button.
To open the Current Users screen, click Current Users on the Sage 300
desktop Help menu.
3. Check that you can connect to your data and run installed applications
from the Sage 300 Desktop locally or from the server (depending on
your network configuration).
Use the instructions for your operating system provided in the section,
“Installing Internet Information Services (IIS).”
• Web-Deployment Files.
• If you plan to use .NET Remoting for Web deployment, also select
the option Sage 300 .NET Libraries.
http://www.iis.net/configreference/system.applicationhost/applicati
onpools/applicationpooldefaults
For Windows 7
1. From the Windows Start menu, click Settings > Control Panel > All
Programs And Features.
3. Expand the Internet Information Services folder, and then expand the
Web Management Tools folder.
5. Expand the World Wide Web Services folder, and then the Application
Development Features folder. Select the following options:
a. ASP
b. ASP.NET
1. From the Windows Start menu, click Settings > Control Panel >
Administrative Tools > Server Manager.
2. In the left pane, select Roles, and then in the center panel, click Add
Roles.
3. In the left navigation pane, select Server Roles, and then select the
roles Application Server and Web Server (IIS).
4. In the left navigation pane, select Application Server and then Role
Services, and then select the role service COM+ Network Access.
5. In the left navigation pane, select Web Server (IIS), and then Role
Services. Expand the Web Server folder tree, and then select:
1. From the Windows Start menu, click Programs > Sage 300 > Web
Deployment Manager.
Configuring Web If you are configuring Web Deployment, and Windows’ user access
Deployment for
controls are set at the default level, you may receive a message
systems with user
access controls saying that IIS is not installed, even if it is installed. If this occurs:
d. Click OK.
2. Read the information on the Welcome page, and then click Next.
Choose how the Sage 300 server will communicate with browser
clients.
Or
• Port Range. Specify the range of ports that .NET Remoting can
use to communicate with clients. If you are not the network
administrator, ask your network administrator to confirm whether
the default range is in use. If other applications on the server are
using ports within the default range, specify a different range.
Select the maximum number of Web server objects you require. This
will depend on the number of users who will access the Web Desktop,
and the number of installed applications.
Note:One object is required for each user logged into the Web
Desktop and for each user interface form that the user opens.
On the server, the Sage 300 server components must be installed into
Windows Component Services. The server components generate the
Web pages that users see in their Web Desktop.
Specify the server name and site directory that clients will access to
view the Web Desktop.
a. Type the name of the Virtual directory in which your Sage 300 site
will be stored. This name will form part of the URL that users enter
in their browser’s address bar to access the Web Desktop.
b. Type the server’s name in the Server name field. Web clients use
this name to gain access to services and to download applications
from the Sage 300 server.
4. Read the text on the Summary tab, and then click Next.
5. Read the text on the Done tab, and then click OK to quit the Wizard.
The first time you access a Sage 300 company database from your
browser, you will be prompted to download Web Client Setup files. Click
Sign On to start the download and sign on to your company database.