Ntinstall 84 0212

MK
For Windows 2000 and


Windows NT
Installation and Upgrade Guide

Version8.40212
Copyright © 2003 by SSA Global Technologies, Inc.
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
way or by any means, including, without limitation, photocopying or recording, without the prior written consent of
SSA Global Technologies, Inc.
Important Notices
The material contained in this publication (including any supplementary information) constitutes and contains
confidential and proprietary information of SSA Global Technologies, Inc.
By gaining access to the attached, you acknowledge and agree that the material (including any modification,
translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein,
are the sole property of SSA Global Technologies, Inc. and that you shall not gain right, title or interest in the material
(including any modification, translation or adaptation of the material) by virtue of your review thereof other than the
non-exclusive right to use the material solely in connection with and the furtherance of your license and use of
software made available to your company from SSA Global Technologies, Inc. pursuant to a separate agreement
(“Purpose”).
In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such
material in strict confidence and that your use of such material is limited to the Purpose described above.
Although SSA Global Technologies, Inc. has taken due care to ensure that the material included in this publication is
accurate and complete, SSA Global Technologies, Inc. cannot warrant that the information contained in this
publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As
such, SSA Global Technologies, Inc. does not assume and hereby disclaims all liability, consequential or otherwise,
for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication
(including any supplementary information), whether such errors or omissions result from negligence, accident or any
other cause.
Trademark Acknowledgements
Masterpiece/Net is a registered trademark and MK Logistics, MK Manufacturing, SSA GT and SSA Global
Technologies are trademarks of SSA Global Technologies, Inc. in the United States and/or other countries.
Microsoft, MS-DOS, Windows, Windows NT and the Windows logo are registered trademarks of Microsoft
Corporation in the United States and/or other countries.
Oracle is a registered trademark of the Oracle Corporation in the United States and/or other countries.
Novell and NetWare are registered trademarks of Novell, Inc. in the United States and/or other countries.
Symbol is a registered trademark of Symbol Technologies, Inc. in the United States and/or other countries.
Vertex is a registered trademark of Vertex, Inc. in the United States and/or other countries.
All other company, product, trade or service names referenced may be registered trademarks or trademarks of their
respective owners.
Contents
Chapter 1: Before You Begin

In This Guide................................................................................. 1–1
Installation Configurations .................................................................... 1–2
System Requirements ......................................................................... 1–4
Supported Databases .......................................................................... 1–7
Services ...................................................................................... 1–8
Chapter 2: Before Installing MK

Overview .................................................................................... 2–1
Pre-Installation Checklist ...................................................................... 2–2
Adding User mkadmin to the Domain .......................................................... 2–2
Installing the Relational Databases Supported by MK ............................................ 2–3
Chapter 3: Installing MK on a Single Server

Overview .................................................................................... 3–1
Single Server Installation Checklists ............................................................ 3–2
Performing a Single-Server Installation ......................................................... 3–4
Installing the interBiz Desktop ................................................................ 3–16
Chapter 4: Installing MK in a Dual-Server Environment

Overview .................................................................................... 4–1
Dual Server Installation Checklist .............................................................. 4–2
Setting Up the Database Server................................................................. 4–3
Setting Up the Application Server ............................................................. 4–13
Setting Up a Secondary Application Server ..................................................... 4–24
Contents iii
Chapter 5: Upgrading MK
Overview .....................................................................................5–1
Performing a Single-Server Upgrade ............................................................5–2
Performing a Dual-Server Upgrade ........................................................... 5–13
After Upgrading ............................................................................ 5–34
Chapter 6: After Installing MK

Overview .....................................................................................6–1
Adding Users .................................................................................6–2
Adding a Printer ..............................................................................6–7
Licensing the Software .........................................................................6–9
Adding Additional Package Combinations .................................................... 6–20
Installing Demo Companies .................................................................. 6–22
Creating Help ............................................................................... 6–25
Changing the Date Format ................................................................... 6–26
Creating a New Database .................................................................... 6–26
Appendix A: Setting Up the Radio Frequency Devices

Supported By MK
Overview .................................................................................... A–1
Configuring the Symbol RF Device............................................................. A–2
Configuration Telnet ......................................................................... A–7
Appendix B: Troubleshooting
Detecting and Correcting Problems ............................................................ B–1
Understanding the Install and Upgrade Processes ............................................... B–2
Uninstalling MK ............................................................................. B–4
Appendix C: Setting Tax Provider Parameters

Setting Tax Provider Parameters ............................................................... C–2
Required Fields .............................................................................. C–3
Tax Conversion for 8.0 US ..................................................................... C–3
iv MK Installation and Upgrade Guide for Windows 2000 and Windows NT

Appendix D: Compatibility of MK 8.4 (0212) and Windows
2000 with Active Directory
Active Directory and MK FAQs ............................................................... D–2
Active Directory FAQs ....................................................................... D–3
Appendix E: Installing the MK Source Code

Installing the Source Code ..................................................................... E–2
Contents v
Chapter
Before You Begin

1
In This Guide
This guide contains installation requirements and step-by-step instructions for
installing MK Manufacturing and MK Logistics for Windows 2000 and
Windows NT. It covers the installation process for both single-server and dual-
server configurations. It also tells you how to upgrade your current version of
MK Manufacturing or MK Logistics and how to install the Radio Frequency (RF)
devices supported by MK.
This chapter contains the following information:

■ Installation configurations
■ System requirements
■ Databases supported
■ System services
Before You Begin 1–1

Installation Configurations
You can install MK for Windows 2000/NT using one of the following
installation configurations:
■ Single-server configuration
■ Dual-server configuration
What you choose depends on your site’s requirements.
Single-Server Configuration
In a single-server configuration, the MK application server and database driver

are installed on a single machine. interBiz Desktop is installed on every
Windows workstation from which you want to run and access MK.
MK Internet Client interBiz Desktop interBiz Desktop
TCP/IP Connection TCP/IP Connection
MK Application Server
Database Driver
Relational Database
Note: All machines must have a TCP/IP connection to run and access MK.
1–2 MK Installation and Upgrade Guide for Windows 2000 and Windows NT
Dual-Server Configuration
The MK dual-server configuration uses two server machines: the application

server and the database server. The application server is the machine where the
MK application server product is installed. The database server is the machine
where the relational database and the appropriate MK database driver are
installed. In a dual-server configuration, the MK application and database
server software are installed on separate NT server machines.
Important! You must install the MK database driver on the database server machine
before installing the MK application server on the application server machine.
Install the interBiz Desktop client on every Windows workstation for each user.
Installation Sequence
The following is the sequence of installation in a dual-server environment:

1. Install the database
2. Install the MK database driver
3. Install the MK application server
4. Install the interBiz Desktop client
Note: All machines must have a TCP/IP connection if you want to run and
access MK.
TCP/IP TCP/IP
Connection Connection
interBiz Desktop MK Internet Client
MK Application Server
TCP/IP
Connection
TCP/IP TCP/IP
Connection Connection
MK Database Server

System Requirements
System Requirements
The following table lists minimum hardware requirements for the MK
components. The hardware requirements vary depending on whether you are
installing all functions on a single-server or across multiple servers. Keep in
mind that although we are providing hardware recommendations in this table,
we recommend that you always purchase hardware with the fastest CPU speed
available at the time of purchase. In addition, be aware that adding more CPUs
than the number recommended always results in improved performance.
Installation
Component Description of Component Minimum System Requirements
Database Server In a dual-server configuration, the 32 GB disk space
machine where the relational Less than 40 users: 1 GB RAM, 450
database and the MK database MHz Dual Pentium III processor or
driver are installed. higher
40 users or more: 2 GB RAM, 450 MHz
Quad Pentium III processor or higher
Windows NT 4.0 with Service Pack 5 or
Windows 2000 Server with Service Pack
1
Application Server In a dual-server configuration, the 12 GB disk space
machine where the MK application Less than 40 users: 1 GB RAM, 450
server is installed. MHz Dual Pentium III processor or
higher
40 users or more: 1.5 GB RAM, 450 MHz
Dual Pentium III processor or higher
1
Database Server and In a single-server configuration, the 32 GB disk space
Application Server machine where the relational Less than 40 users: 1.5 GB RAM, 450
database, MK database server, and MHz Quad Pentium III processor
MK application server are installed. 40 users or more: 2 GB RAM, 450 MHz
Quad Pentium III processor
1
System Requirements
Installation
Component Description of Component Minimum System Requirements
interBiz Desktop interBiz Desktop is the Microsoft Windows NT 4.0 with Service Pack 5 or
Windows user interface client. above or Windows 2000 Server with
Service Pack 1; Internet Explorer 5.0 or
above
Or
Windows 95, Windows 95 OSR2,
Windows 95OSR25 or above
Windows 95 Service Pack 1 (applicable
only to Windows 95, not the OSR
releases)
Microsoft DCOM 95
Microsoft Winsock 2.0
Internet Explorer 5.0 or above
Or
Windows 98
Windows 98 SE
Windows ME
Windows XP
Additional Requirements
The following must be running on each machine on which MK is installed:

■ 32 bit TCP/IP Network Protocol
■ All server machines must belong to a common Windows NT domain
The following are additional requirements when installing MK:

■ Do not use the MK application or database server as the primary or backup
domain controller.
■ Do not install any other software on the MK application or database server
except for what is required to run MK.
■ Make sure that name resolution for the MK application and database servers
is done through a DNS or WINS server. Refer to the Microsoft Windows NT
Server Guide for more details on name resolution.

System Requirements
interBiz Desktop Requirements
You can install the interBiz Desktop client on Windows 2000, Windows NT
Workstation and Server 4.0 and above, Windows XP, Windows ME, Windows 98
SE, Windows 98, or Windows 95.
Windows 2000
Microsoft Windows 2000 Service Pack 1 must be installed.
Windows NT 4.0 Server and Workstation

1. Microsoft Windows NT 4.0 Service Pack 5 or above must be installed.
2. Microsoft Internet Explorer 5.0 or above must be installed.
Windows XP, Windows ME, Windows 98 SE, or Windows 98
Currently there are no prerequisites for installation on Windows 98, Windows 98

SE, Windows ME, or Windows XP.
Windows 95
Before installing interBiz Desktop on Windows 95 you must install the following
Microsoft products, product updates, or service packs in the order indicated:
1. Install either Windows 95, Windows 95 OSR2, or Windows 95 OSR25.
2. If you have installed the Windows 95 retail release, you must install
Windows 95 service pack 1 or above. The install for service pack 1 is in the
file win95sp1.exe.
3. You must install the OLE service pack update. The install for this update is
in the file oleupd.exe.
4. You must install DCOM for Windows 95 (or later). The install for DCOM 95
is in file Dcom95.exe.
5. You must install Winsock 2.0 for Windows 95. The install for Winsock 2.0 is
in file ws2setup.exe.
6. You must install either Microsoft Internet Explorer 4.01 or the Microsoft
Common Control 4.0 update if you don't wish to install Internet Explorer
4.01. We highly recommend that you Install Internet Explorer 4.01 since not
all MK Desktop functionality will be available otherwise. The install for the
common control update is in file 40Comupd.exe.
7. Microsoft HTML Help engine must be installed. This is installed
automatically by the MK Desktop install and normally will not require
manual installation. The install for the HTML help engine is in file
hhupd.exe.
Supported Databases
Supported Databases
The following databases are supported by MK:
■ Ingres II 2.6/0207 (Ingres II 2.6/0201 + Ingres II 2.6 Service Pack 1)
■ Ingres II 2.5
■ Ingres II 2.0/0001
■ Microsoft SQL Server 2000 (must be run on Microsoft Windows 2000)
■ Microsoft SQL Server 7.0
■ Oracle 9i
■ Oracle 8i
■ Oracle 8.0.5.0.0
Upgrading From You must upgrade to Ingres II before upgrading MK. Refer to the Ingres II
OpenIngres 1.2 or documentation for details on the database upgrade.
OpenIngres 2.0
Upgrading From SQL If you are running MK with SQL Server 6.5, you must upgrade to SQL Server
Server 6.5 7.0 or SQL Server 2000 before upgrading to MK 8.4.

Services
Services
The MK installation program installs three system services. Each of these
services performs a specific system function. The services are described in the
following table. Note that the database install creates its own environment
variables and services.
Service Description of the Service

MK Print Server This service manages the printer queue for printers
defined in MK.
It is installed on the application server.
CAMK License Service This service provides license administration to all of
the MK installations.
It is installed on the application server.
MK Server This server provides remote connections and manages
shared memory resources for the application and
database server.
It is installed on both the application server and the
database server.
Chapter
Before Installing MK
2
Overview .................................................................................... 2–1

Pre-Installation Checklist ...................................................................... 2–2
Adding User mkadmin to the Domain .......................................................... 2–2
Installing the Relational Databases Supported by MK ............................................ 2–3
Configuring Ingres II for MK ............................................................... 2–3
Configuring Microsoft SQL Server 2000 for MK .............................................. 2–6
Configuring SQL Server 2000 for MK .................................................. 2–10
Configuring Microsoft SQL Server 7.0 for MK .............................................. 2–15
Configuring SQL Server 7.0 for MK .................................................... 2–20
Configuring Oracle 9i for MK ............................................................. 2–25
Creating Tablespaces and Rollback Segments ........................................... 2–28
Creating Oracle Users ................................................................ 2–28
Installing MK ........................................................................ 2–28
Configuring Oracle 8i for MK ............................................................. 2–29
When Installing Oracle 8i ............................................................. 2–29
Creating an MK Database ............................................................. 2–30
Installing MK ........................................................................ 2–34
Configuring Oracle 8.0 for MK ............................................................ 2–35
Creating an MK Database ............................................................. 2–35
Installing MK ........................................................................ 2–39
Contents i
Chapter
Before Installing MK
2
Overview
This chapter describes the conditions that must be met before you install MK. It
also tells you how to add user mkadmin to the domain and provides you with the
information you need when installing the relational databases (Ingres II,
Microsoft SQL Server, and Oracle) supported by MK.
Before Installing MK 2–1

Pre-Installation Checklist
Before installing MK, the following conditions must be met:
1. Install Microsoft Windows NT or Windows 2000 Server on server machines
and Microsoft Windows NT Workstation, Windows 2000, Windows XP,
Windows ME, Windows 98, Windows 98 SE, or Windows 95 on client
machines. Install additional support software as specified in the Systems
Requirements section of Chapter 1.
All machines running MK must belong to the same Windows NT domain.
Make sure that a Windows NT domain controller exists before installing MK
software. If it does not exist, you must create one.
2. TCP/IP must be installed on every server and client machine.
3. Install your relational database on the database server.
4. Install MK onto an NTFS formatted drive.
In addition, we recommend that you:

■ Back up your current system
■ Choose the Show All Files and Display Full Paths options in the Windows
NT Explorer View options.
Adding User mkadmin to the Domain

Before installing MK, you must add the user mkadmin as a domain administrator
account for the NT domain in which MK will run. The following procedure
applies to both a single- and dual-server installation.
Note: User mkadmin is case sensitive in MK. Therefore, you should establish
mkadmin as lowercase in Windows NT, in MK, and in your database.
⇒ To add users to the domain:

1. Log on as a user with administrator rights to a machine running the
Windows NT Domain Server that controls your domain.
2. Assign the mkadmin user as a member to the following groups:
■ Domain Admins
■ Domain Users
3. Define the mkadmin user rights as part of the operating system.
Refer to the Microsoft Windows NT documentation for details on adding users
to the domain.
Installing the Relational Databases Supported by MK

You must install your database before installing MK. Refer to the installation
instructions for your database for specific information on how to do this.
This section provides you with additional information you need when
configuring each database (Ingres II, Microsoft SQL Server, and Oracle) to work
with MK.
Configuring Ingres II for MK
This section describes the options you need to select when installing Ingres II in
order to configure it for MK.
Refer to the Ingres II documentation for details on installing an Ingres II

database.
⇒ To configure Ingres II for MK:

1. In the following dialog box:
Select the Ingres/DBMS installation type. You can also select the Ingres
Character Based Tools option.

You must select the Start Ingres Service Automatically at System Startup
option.
Set the Transaction Log File Size to at least 500 MB.
4. When you have finished installing Ingres II, install any applicable patches
and reboot your server.
5. Check Services. Ingres II should be running. Open the Ingres II
Configuration Manager. Select DBMS Server, and set the cursor_limit to 128,
as shown in the following example:
6. Add user mkadmin to the database.

Use Visual DBA to add the user mkadmin to the database.
Check all options under the Users and Default columns.

7. Add user mk to the database.
Use Visual DBA to add the user mk to the database. In the Privileges section,
check the Users and Default boxes for the Create Database option.
8. Create an MK database
Open a command prompt window. Create the MK database using the
following command: createdb –umk mk.

Configuring Microsoft SQL Server 2000 for MK
This section provides you with information you need when installing Microsoft
SQL Server 2000. It also tells you how to configure SQL Server 2000 for MK.
⇒ To install SQL Server 2000:

1. Create a user mkadmin on the MK domain with domain administration
privileges (if one does not already exist).
2. Log on to the MK database server as the domain user mkadmin.
3. Put the SQL Server 2000 CD-ROM into the CD-ROM drive.
4. Choose Install SQL Server 2000 Prerequisites to make sure that all
prerequisites have been installed. When you are finished, click Back to
return to the startup screen.
5. Choose Install SQL Server 2000 Components.
6. Choose Install Database Server.
7. Click Next on the Welcome screen.
8. The Computer Name dialog box opens:
Choose Local Computer and click Next.
9. The Installation Selection dialog box opens:
Choose Create a new Instance of SQL Server and click Next.

10. Enter information in the User Information dialog box. Click Next.
11. The Installation Definition dialog box opens:
Choose Server and Client Tools. Click Next.

12. In the Instance Name dialog box, enter a name of your choice or choose
Default.
13. Click Next to open the Setup Type dialog box:
Choose Typical. Change the location of the Program Files and Data Files if
necessary.
14. Click Next to open the Services Accounts dialog box:
Select an account for the Service Settings. If you choose a domain user, make
sure you use a domain administrator account.
15. Click Next to open the Authentication Mode dialog box:
Choose Windows Authentication Mode.

16. Click Next to display the Setup is ready to copy files dialog box.
17. Click Next to start the installation. The SQL Server files are copied and the
services are set up.
18. When this process is complete, the Setup Complete dialog box opens. Click
Finish to complete the setup process.

Configuring SQL Server 2000 for MK
After you install SQL Server 2000, you need to configure it for MK. The
remainder of this section describes what you need to do, including:
■ Creating an mk database
■ Adding an ODBC server DSN
⇒ To create an MK database:
1. From the Start menu, select the SQL Server Manager:
Right-click on Databases and select New Database.

2. The Database Properties dialog box opens:
Set the database name to mk. In the Collation Name field, choose
Latin1_General_BIN.
3. Click the Data Files tab:
Set the initial database size to 1000 mb. Accept the default choices for the
remaining options in this dialog box.
4. Click the Transaction Log tab:
Set the initial size of the transaction log to 500 Mb.

5. Click OK to create the database.
⇒ To add an ODBC server DSN:

1. From the Control Panel, double-click the ODBC Data Sources icon. Click the
System DSN tab.
2. Click Add to add a new server DSN. The Create New Data Source dialog box
opens:
Choose SQL Server. Click Finish.
3. The Create a New Data Source to SQL Server dialog box opens:
Enter MKServer in the Name field and choose local in the Server list box.
4. Click Next.
Accept the default choices.

5. Click Next:
Check the Change the default database to option and select mk from the
drop-down list box.

6. Click Next:
Accept the default choices and click Finish.

7. The ODBC Microsoft SQL Server Setup dialog box opens:
Click Test Data Source to make sure that the connection is functional. Click
OK.
The system is now ready for installing MK.
Configuring Microsoft SQL Server 7.0 for MK
This section provides you with information you need when installing SQL Server
7.0 . It also tells you how to configure SQL Server 7.0 for MK.
⇒ To install SQL Server 7.0:

2. Log on to the MK database server as the domain user mkadmin.
3. Put the SQL Server 7.0 CD-ROM into the CD-ROM drive.
4. Choose Install SQL Server 7.0 Prerequisites to make sure that all
prerequisites have been installed.
The prerequisites for this release of MK are shown above. Click Back to
return to the startup screen.

5. Choose Install SQL Server 7.0 Components. The following window opens:
6. Choose Database Server – Standard Edition. (Note: If you have the

Enterprise Edition of SQL Server, choose Database Server – Enterprise
Edition). The Select Install Method dialog box opens:
Choose Local Install.

7. A Welcome screen opens. Click Next.
8. Enter information in the User Information dialog box and click Next.
9. The Setup Type dialog box opens:
Choose Custom as the setup option. Change the Program Files and Data
Files destination folders if necessary or accept the defaults.
10. Click Next to display the Select Components dialog box:
Accept the default values by clicking Next.

11. The Character Set/Sort Order/Unicode Collation dialog box opens:
In the Sort Order option, choose Binary Order.

12. Click Next to display the Network Libraries dialog box:
Accept the default selections by clicking Next. (Note that MK does not use
these options.)
13. The Service Accounts dialog box opens:
Choose the “Use the same account for each service. Auto start SQL Server
service” option Use the mkadmin user for these services. Enter the password
and domain name as set up on your system.
14. Click Next to display the Setup is ready to copy files dialog box.
15. Click Next to start the installation. The SQL Server files are copied and the
services are set up.
16. When this process is complete, the Setup Complete dialog box opens. Click
Finish to complete the setup process.

Configuring SQL Server 7.0 for MK
After you install SQL Server 7.0, you need to configure it for MK. The remainder
of this section describes what you need to do, including:
■ Adding an ODBC server DSN
1. From the Start menu, select the SQL Server Manager:
Right-click on Databases and select New Database.

2. The Database Properties dialog box opens:
Set the database name to mk and the initial database size to 1000 mb. Accept
the default choices for the remaining options in this dialog box.
3. Click the Transaction Log tab:
Set the initial size of the transaction log to 500 Mb.

4. Click OK to create the database.
Double-click the mk database to set the Log Option for the Database.

5. Click the Options tab:
Check the Truncate Log on Checkpoint option. Click OK.
⇒ To add an ODBC server DSN:

1. From the Control Panel, double-click the ODBC Data Sources icon. Click the
System DSN tab.
2. Click Add to add a new server DSN. The Create New Data Source dialog box
opens:
Choose SQL Server. Click Finish.
3. The Create a New Data Source to SQL Server dialog box opens:
Enter MKServer in the Name field and choose local in the Server list box.
4. Click Next.
Accept the default choices.

5. Click Next:
Check the Change the default database to option and select mk from the
drop-down list box.

6. Click Next:
Accept the default choices and click Finish.

7. The ODBC Microsoft SQL Server Setup dialog box opens:
Click Test Data Source to make sure that the connection is functional. Click
OK.
The system is now ready for installing MK.
Configuring Oracle 9i for MK
This section provides you with information you need when installing Oracle 9i.
It also tells you how to configure Oracle 9i for MK, including:
■ Creating tablespaces and rollback segments
■ Creating Oracle users mk, mkadmin
■ Installing MK
⇒ To configure Oracle 9i for MK:

2. Log on to the MK database server as the domain user mkadmin. From the
Oracle CD Browser screen, choose Install/Deinstall products.

3. From the Available Products dialog box, select the Oracle 9i Database option.
4. From the Database Configuration dialog box, choose Customized.
5. Once the software is installed, use the Database Configuration Assistant to

configure a database template for the MK database. The following
parameter must be set in the template to the values shown below:
open_cursors = 500
6. From the Character Sets Tab, choose WE8ISO8859P1 and select UTF8 for the
National Character set.
Use the Database Configuration Assistant to create an mk database. When

prompted for database identification, enter
mk.yourcompanyname.
The SID must be mk.
At this point, you must create tablespaces and set up users for mk.

Creating Tablespaces and Rollback Segments
Following instructions in the Oracle RDBMS Installation Guide, use the Oracle
command create tablespace to create the following tablespaces:
mkxtables with at least 800 MB MK data tables

mkindexes with at least 800 MB MK indexes
mktmp with at least 25 MB Temporary tables
mkrbs with at least 100 MB Rollback segments
Refer to Chapter 2, “Configuring Oracle for MK” in MK in the Oracle Environment

for more information on creating tablespaces and rollback segments.
Creating Oracle Users
You need to set up the following Oracle users: mk, mk_g, mkadmin. After you
create the users, you need to grant permissions for the users. Refer to Chapter 2,
“Configuring Oracle for MK” in MK in the Oracle Environment for more
information on creating Oracle users.
Installing MK
After installing the Oracle 9i database, you can install MK. During this
installation, select the Oracle 9i database.
Configuring Oracle 8i for MK
This section provides you with information you need when installing Oracle 8i.
It also tells you how to configure Oracle 8i for MK, including:
■ Creating Oracle users mk, mk_g, mkadmin
■ Installing MK
When Installing Oracle 8i
When installing Oracle 8i, make sure to perform the following:

2. Log on to the MK database server as the domain user mkadmin and run
setup.exe from the Oracle CD-ROM.
3. When prompted for product selection, choose Oracle 8i 8.1.5.0.0.
4. When prompted for Installation Type, choose Custom. This lets you define
the database parameters for the database mk that you will create.
5. When prompted for database identification, enter mk.yourcompanyname.
The SID must be mk.
6. After the software is installed, the Oracle Database Configuration Assistant
starts, to step you through the process of creating the mk database.

Creating an MK Database
This section tells you how to create a new database using the Oracle Database
Assistance utility.
Keep In Mind When you create the MK database, write down the ORACLE_HOME and
ORACLE_SID parameters, as you will be prompted for this information when
you install MK.
1. Start the Oracle Database Assistant.
Choose the option to create a database.

2. Click Next.
Choose Typical.
3. Click Next.
Choose the option to Create new database files.

4. Click Next.
Choose the Hybrid option to specify that both Online Transaction Processing
and Decision Support System applications run with the database.

5. Click Next.
Specify the number of users that can use MK at the same time.
6. Click Next.
Accept the default configuration options.

7. Click Next.
Verify that the SID is set to mk.
8. Click Next.
Choose the option to create the database and click Finish.
After Installing the After the database is created, you need to add the following line to the end of
Database the init.ora file:
open_cursors = 500
This file is located in the %ORACLE_HOME%\DATABASE directory.
In order for this parameter to take effect, you must stop and restart the Oracle
service. From the Control Panel, choose Services, and select Stop the
OracleServiceMK. Next, start the OraceStartMK, which in turn starts
OracleServiceMK.
Warning! If you do not make this modification, the install will fail with an error
indicating that there are not enough cursors.


mkrbs with at least 100 MB Rollback segments

Installing MK
After installing the Oracle 8i database, you can install MK. During this
installation, select the Oracle 8i database.
Configuring Oracle 8.0 for MK
After you install the Oracle 8.0 database, you need to configure it for MK. This
section tells you what you need to do, including:
■ Creating Oracle users mk, mk_g, mkadmin
■ Installing MK
Creating an MK Database
This section tells you how to create a new database using the Oracle Database
Assistance utility.
Keep In Mind When you create the MK database, write down the ORACLE_HOME and
ORACLE_SID parameters, as you will be prompted for this information when
you install MK.
1. Start the Oracle Database Assistant.
Choose the option to create a database.

2. Click Next.
Choose Custom to create a user-defined database. Click Next.

3. Leave the Advanced Replication Support option unchecked. Click Next.
4. Accept the default database size (Medium) or select Large and click Next.
Enter mk for the Database Name and SID fields as shown and set the
internal password. Click Next.
5. Accept the default control file parameter information. Click Next.
6. Accept the default information and click Next.
Select log file sizes of 1024 and click Next.

7. Accept the default logging parameter information. Click Next.
8. Accept the default SGA parameter information. Click Next.
Accept the default trace file configuration information.

9. Click Next.
Select the first option to create the database immediately and click Finish.
10. Answer Yes to the prompt to create the database now.
Click OK.
11. Answer Yes to add the SID name to your listener.ora file.
After Installing the After the database is created, you need to modify the initmk.ora file, which is
Database located in the %ORACLE_HOME%\DATABASE directory. Add the following
line to the end of the file:
open_cursors = 500
In order for this parameter to take effect, you must stop and restart the Oracle
service. From the Control Panel, choose Services, and select Stop the
OracleServiceMK. Next, start the OraceStartMK, which in turn starts
OracleServiceMK.
Warning! If you do not make this modification, the install will fail with an error
indicating that there are not enough cursors.

mkrbs with at lest 50 MB Rollback segments

Installing MK
After installing the Oracle database, you can install MK. During this installation,
select the Oracle 8.0. database.

Chapter
Installing MK on a Single Server

3
Overview .................................................................................... 3–1

Single Server Installation Checklists ............................................................ 3–2
Pre-Installation Checklist .................................................................. 3–2
Installation Checklist ...................................................................... 3–3
Post-Installation Checklist ................................................................. 3–3
Performing a Single-Server Installation ......................................................... 3–4
Contents i
Chapter
Installing MK on a Single Server

3
Overview
This chapter describes how to install MK on a single-server. A single-server
configuration installs the MK application server and database driver on a single
machine.
Installing MK on a Single Server 3–1

Single Server Installation Checklists

This section provides you with checklists for things you need to do before,
during, and after the installation of MK.
The following is provided for quick reference. Each task is described in greater
detail in Chapter 2, “Before Installing MK.”
; Task
Make sure that you meet all system requirements
Create the domain user mkadmin
Install the relational database
Apply database patches or service packs, as described in the System
Requirements section of Chapter 2 of this guide
Configure database parameters for the mk database, as described in the
appropriate database section of Chapter 2 of this guide
Add the users mk and mkadmin to the database, as described in the
Create the mk database
If you are installing MK with Microsoft SQL Server, make sure to create
the ODBC DSN
If you are installing MK with Oracle, make sure that open_cursors are
added to the initmk.ora file
If you are installing the Advanced Finance Option for MK, make sure
you have the server name and port number for the Masterpiece/Net
server
If you are using Quantum software with MK, make a note of the version
of the Quantum software that is installed
Installation Checklist
detail in this chapter.
; Task
Re-run the MK set up after the system .dll’s are installed and the system
is rebooted
Make sure to reboot after setup is completed
Post-Installation Checklist
detail in Chapter 6, “After Installing MK.”
; Task
Install a demo company for currency setup

Add users to the database, the database driver, and mk as needed
Set up your printers
License the software
Add additional package combinations as needed

Performing a Single-Server Installation

⇒ To complete a single-server installation:
1. Log onto the Windows NT Server machine as user mkadmin in the Windows
NT domain.
2. Put the MK for Windows NT CD-ROM in the CD-ROM drive.
If autoplay is turned off on your computer, the MK browser dialog will not
open automatically. To access it, on the Start menu, click Run and enter
x:\autorun.exe. Substitute X with your CD-ROM drive. Click Install MK 8.4
(0212) Server.
3. The install checks to see if your system has the required system files for this
release of MK. If it does not, the following Information dialog box opens:
Click OK to continue with the upgrade of system files. (If you do not see this
dialog box, go to step 8.)
4. The MK System Files Setup Welcome dialog box opens:
Click Next to continue.

5. An Information dialog box opens:

6. The system files are copied to your computer. When finished, the following
dialog box opens:
Select the option to restart your computer now. Click Finish.

7. When the system reboots, make sure the MK for Windows NT CD-ROM is in
the CD-ROM drive. Start the MK setup by clicking Run on the Start menu
and typing x:\autorun.exe, where X is your CD-ROM drive. Click Install
MK 8.4 (0212) Server.
8. The MK Server Setup Welcome dialog box opens:
Click Next.
9. An MK product selection dialog box opens:
Select the MK product you are installing. Click Next.

10. The MK Install Notes display:
Review the install notes.

11. Click Next.
Make sure the MK Application Server and MK Database Server components

are selected. You can change the default destination folder by clicking
Browse. Click Next.
12. The System Information dialog box opens:
Identify the installation in the MK System Name field. You use this name to
log into MK. Use the other fields to describe the server and the MK system.
13. Click Next.
Select the version of MK you want to install on your system.

14. Click Next.
If you are using Symbol devices, choose Yes.

15. Click Next.
If you are using the Advanced Finance Option, choose Yes.

16. Click Next. If you enabled the Advanced Finance Option, the following
dialog box opens (otherwise, go on to the next step):
Enter the server name and port number for the Masterpiece/Net server.
17. Click Next.
Select the version of the Quantum software that is installed on your system
or choose None.
18. Click Next.
Select the database you are using with MK.

19. Click Next. The install searches for the database; it displays informational
messages if it doesn’t find it. You can choose to continue with the
installation if these messages display. When this process is complete, one of
the following dialog boxes opens (depending on the database you are using):
Ingres II
Oracle
8.0
Oracle 8i
and
Oracle 9i
Microsoft SQL
Server 2000 and
SQL Server 7.0
Enter the name of the database. This is usually the default name mk.
20. Click Next. Accept the default program folder or select one from the list of
available folders.

21. Click Next.
Review your installation selections. If you need to change any settings, click
Back; otherwise, click Next to begin the installation.
The installation process copies files to the MK directories, installs new MK
services, and runs the Import Data Dictionary (ttiex1287m000) session to
import the copied components. This process can take several hours,
depending on your system. The MK Console Log dialog box opens during
the Import Data Dictionary Process:
You can ignore these messages.
The installation process can detect and correct any situation that prevents the
install from completing. If this happens, the install process prompts you to
determine whether you want to restart the process; choose Yes to continue.
If a failure occurs again, report the problem to Technical Support for further
analysis.
When the install successfully completes, the Setup Complete dialog box
opens. Choose Yes to restart your computer and click Finish.
After you complete the installation, you need to perform post-installation tasks.
See Chapter 6, “After Installing MK,” for information on what to do.

Installing the interBiz Desktop

After you install the MK application server and database driver, you need to
install the interBiz Desktop client. The interBiz Desktop is the Microsoft
Windows user interface client.
⇒ To install the interBiz Desktop client:

1. Put the MK Client CD in the CD-ROM drive.
2. Click interBiz Client.

3. Follow the instructions that appear to install the interBiz Desktop client.
When the Select Components dialog box opens, check the options to install
the interBiz Desktop and the MK Internet Client.
The MK Internet client contains the ActiveX controls needed to access MK
through Microsoft Internet Explorer.
Installing MK in a Dual-Server
Chapter
4 Environment
Overview .................................................................................... 4–1

Dual Server Installation Checklist .............................................................. 4–2
Setting Up the Database Server................................................................. 4–3
Pre-Installation Checklist .................................................................. 4–3
Installation Checklist ...................................................................... 4–3
Post-Installation Checklist ................................................................. 4–4
Installing the MK Database Server .......................................................... 4–4
Setting Up the Application Server ............................................................. 4–13
Pre-Installation Checklist ................................................................. 4–13
Installation Checklist ..................................................................... 4–13
Post-Installation Checklist ................................................................ 4–14
Installing the MK Application Server ...................................................... 4–14
Setting Up a Secondary Application Server ..................................................... 4–24
Installing the interBiz Desktop Client ...................................................... 4–26
Contents i
Installing MK in a Dual-Server
Chapter
4 Environment
Overview
This chapter describes how to install MK in a dual-server environment.
A dual-server configuration uses two server machines: the application server

and the database server. The application server is the machine where the MK
application server is installed. The database server is the machine where a
relational database (Ingres, Microsoft SQL Server, Oracle) and the appropriate
MK database driver are installed. In a dual-server configuration, the MK
application server and database driver are each installed on a separate machine.
You must install the MK database driver on the database server machine before
installing the MK application server on the application server machine.
Perform the following steps to complete a dual-server installation:

■ Set up the database server
■ Set up the application server
■ Install the interBiz Desktop client
These steps are described in this chapter. It also tells you how to set up a
secondary application server, which you can use to take some of the load off the
primary or first application server.
Installing MK in a Dual-Server Environment 4–1

Dual Server Installation Checklist
Dual Server Installation Checklist

The following is provided for quick reference before you install MK in a dual
server environment.
; Task
Make sure that all system requirements are met

Make sure that the application and database servers belong to the same
Windows NT domain
Verify the application and database server name resolution; refer to your
Microsoft Windows NT documentation for details
Create the mkadmin domain user
Setting Up the Database Server

This section tells you how to set up the database server, which is the machine on
which you installed the relational database. Installation checklists are provided
for quick reference for things you need to do before installing MK, during
installation, and after installing MK.
; Task
Install the relational database

Apply database patches or service packs, as described in the System
Requirements section of Chapter 2 of this guide
Configure database parameters for the mk database, as described in the
Add the users mk and mkadmin to the database, as described in the
Create the mk database
If you are installing MK with Microsoft SQL Server, make sure to create
the ODBC DSN
If you are installing MK with Oracle, make sure that open_cursors are
added to the initmk.ora file
; Task
is rebooted

; Task
Add additional users to the database and the database driver as needed
Installing the MK Database Server
⇒ To install the MK database server:

1. Log onto the Windows NT database server machine as user mkadmin in the
Windows NT domain.
2. Put the MK for Windows NT CD-ROM in your CD-ROM drive.
appear automatically. To access it, on the Start menu, click Run and enter
(0212) Server.
The install checks to see if your system has the required system files for this


dialog box opens:

MK 8.4 (0212) Server.
Click Next.
Select the MK product you are installing.

10. Click Next. The MK Install Notes display:

11. Click Next.
Make sure that only the MK Database Server component is selected. You
can change the default destination folder by clicking Browse. Click Next.
Identify the MK installation in the MK System Name field. You use this
name to log into MK. Use the remaining fields to describe the server and the
MK system.
13. Click Next.

Ingres II

Oracle 8.0
Oracle 8i
and
Oracle 9i
Microsoft SQL
Server 2000 and
SQL Server 7 0
15. Click Next.
Enter the name of the MK application server. Note that the server name is
case sensitive in MK. You must enter it exactly as it was named on your
Windows NT domain. Check your Network Neighborhood Properties for
verification.
available folders.
17. Click Next.

The installation process copies files to the MK directories and installs new
MK services.
The installation process can detect and correct certain situations that prevent
the install from completing. If this happens, the install process prompts you
to determine whether you want to restart the process; choose Yes to
continue. If a failure occurs again, report the problem to Technical Support
for further analysis.
opens. Select the option to restart your computer and click Finish.
You are now ready to install the MK application on the application server.
Setting Up the Application Server

This section tells you how to set up the application server, which is the machine
on which you installed the MK application. Installation checklists are provided
for quick reference for things you need to do before installing MK, during
installation, and after installing MK.
; Task
If you are installing the Advanced Finance Option for MK, make sure
you have the server name and port number for the Masterpiece/Net
server
If you are using Quantum software with MK, make a note of the version
of the Quantum software that is installed
Make sure that the database software is running on the database server
; Task
is rebooted

; Task
Install a demo company for currency setup

Add users to mk as needed
Set up your printers
License the software
Add additional package combinations as needed
Installing the MK Application Server
⇒ To install the MK application server:

1. Log onto Windows NT database server machine as user mkadmin in the
Windows NT domain.
(0212) Server.
4. The MK System Files Setup Welcome dialog box opens. Click Next to
continue.
5. An Information dialog box opens. Click Next to continue.
6. The system files are copied to your computer. When finished, a dialog box
opens informing you that setup has finished copying files to your computer.
MK 8.4 (0212) Server.
Click Next.

Select the MK product you are installing. Click Next.

10. The MK Install Notes display:
11. Click Next.
Make sure that only the MK Application Server component is selected. You

13. Click Next.
Select the version of MK you want to install on your system.

14. Click Next.
15. Click Next.


17. Click Next.
or choose None.
18. Click Next.
19. Click Next.
Enter the name of the MK database server. Note that the database server
name is case sensitive in MK. You must enter it exactly as it was named in
the Windows NT domain. Check your Network Neighborhood Properties
for verification.
20. Click Next.
Enter the password information.

available folders.

22. Click Next.
The installation process copies files to the MK directories, installs new MK
services, and runs the Import Data Dictionary session to import the MK
component. This process can take several hours, depending on the speed
and memory of your system. The MK Console Log dialog box opens during
the Import Data Dictionary Process:
You can ignore these messages.
The installation process can detect and correct any situation that prevents the
install from completing. If this happens, the install process prompts you to
determine whether you want to restart the process; choose Yes to continue.
If a failure occurs again, report the problem to Technical Support for further
analysis.
opens. Select the option to restart your computer and click Finish.

Setting Up a Secondary Application Server

You can set up a secondary application server to take some of the load off the
primary or first application server.
⇒ To set up a secondary application server:

1. Log onto Windows NT database server machine as user mkadmin in the
Windows NT domain.
2. Put the MK for Windows NT CD-ROM in your CD-ROM drive.
3. Click Install MK 8.4 (0212) Server. Setup may need to install system files
required for this release of MK; if this happens, you will need to reboot your
machine after the files are installed to continue with the installation.
4. Click Next to start the setup program.
5. Select the MK product you are installing and click Next.
6. Review the install notes. Click Next.
7. Select only the MK Secondary Application Server component. You can
change the default destination folder by clicking Browse. Click Next to
continue.
8. In the System Information dialog box, identify the installation in the MK
System Name field. You use this name to log into MK. Use the other fields
to describe the server and the MK system.
9. In the Primary Application Server dialog box, enter the name of the primary
application server and the drive letter to use for network connections to the
primary application server. Click Next.
10. Accept the default program folder or select one from the list of available
folders. Click Next.
11. Review the selections you have made. To change any of your selections,
click Back until you reach the necessary screen. If your selections are correct,
click Next.
The installation process copies the MK files and installs the MK secondary
application server. When finished, you are prompted to reboot the system.


After you install the server, you need to install the interBiz Desktop client on
each Microsoft Windows workstation.
Installing the interBiz Desktop Client

Click interBiz Client.

When the Select Components dialog box opens, check the options to install
the interBiz Desktop and the MK Internet Client.
The MK Internet client contains the ActiveX controls needed to access MK
through Microsoft Internet Explorer.
Chapter
Upgrading MK
5
Overview .................................................................................... 5–1

Performing a Single-Server Upgrade............................................................ 5–2
Performing a Dual-Server Upgrade ............................................................ 5–13
Upgrading the Database Server ........................................................... 5–13
Upgrading the Application Server ......................................................... 5–23
Upgrading the interBiz Desktop ........................................................... 5–33
Installing the interBiz Desktop Client .................................................. 5–33
Installing the MK Client Classic........................................................ 5–34
After Upgrading ............................................................................. 5–34
Contents i
Chapter
Upgrading MK
5
Overview
This chapter gives detailed instructions for both a single- and a dual-server
upgrade of MK.
Upgrading MK 5–1
Performing a Single-Server Upgrade

⇒ To upgrade an existing version of MK on a single server:
1. Log onto the Windows NT server machine as user bsp or mkadmin
(whichever user is predefined in your system) in the Windows NT domain.
2. Stop all MK services. Leave your database services running.
x:\autorun.exe. Substitute X with your CD-ROM drive.
Click Install MK 8.4 (0212) Server.
4. The install checks to see if your system has the required system files. If it
does not, the following Information dialog box opens:

Upgrading MK 5–3
dialog box opens:

8. When the system reboots, make sure the MK for Windows NT CD-ROM is
in the CD-ROM drive. Start the MK setup by clicking Run on the Start menu
MK 8.4 (0011) Server.
9. The Welcome dialog box opens:
Click Next to continue with the upgrade.

10. The dialog box that opens depends on whether you are upgrading from a
prior release of MK 8.4 or from an MK 8.1 non-technology release or a
release earlier than MK 8.1.
■ If you are upgrading from a prior release of MK 8.4, the following dialog
box opens:
Indicate whether you want to select an MK system to upgrade or install

MK as a separate system on the server. If you select the first option, a
dialog box opens for you to select the system to upgrade. Go to Step 11
to continue the upgrade. If you select the second option, the screens that
display are those that appear for a fresh install of MK.
■ If you are upgrading from an MK 8.1 non-technology release or an MK
release earlier than 8.1, select the components that you want to install
(MK Application Server, MK Database Server, and so forth). Then the
following dialog box opens:
You need to provide this information as it is not available in non-

technology release systems and is needed by MK 8.4.
Upgrading MK 5–5
11. The following dialog box opens:

12. The MK Upgrade Notes display:
Read the upgrade information.
13. Click Next.
Make sure the MK Application Server and MK Database Server components

are selected. You can accept the default destination folder or change it by
clicking Browse.
14. Click Next.
Select the version of MK you want to install on your system. Choose the
version that matches what is currently installed for your system.
Upgrading MK 5–7
15. Click Next.

17. Click Next.
or choose None.
18. Click Next.

Upgrading MK 5–9
Ingres II
Oracle 8.0
Oracle 8i
and
Oracle 9i
Microsoft SQL
Server 2000 and
SQL Server 7.0
Enter the name of the database. This is usually the default name mk. Click
Next.
Review your selections. If you need to change any settings, click Back;
otherwise, click Next to begin the upgrade.
The upgrade process copies files to the MK directories, installs new MK
services, and runs the Import Data Dictionary (ttiex1287m000) session to
import the copied components. This process can take several hours,
depending on your system.
Upgrading MK 5–11
Performing a Dual-Server Upgrade
The upgrade process can detect and correct any situation that prevents the
upgrade from completing. If this happens, the upgrade process prompts
you to determine whether you want to restart the process; choose Yes to
When the upgrade successfully completes, the Setup Complete dialog box
opens. Select the option to restart the computer to complete the upgrade.
Next perform the post-upgrade tasks, described in the After Upgrading
section later in this chapter.

To upgrade an existing version of MK in a dual-server environment, you need
to:
■ Upgrade the database server
■ Upgrade the application server
■ Upgrade the Windows NT and Windows Client workstations
Upgrading the Database Server
The database server is the machine on which you installed the relational
database and the MK database driver.
⇒ To upgrade the database server:

1. Log onto Windows NT database server machine as user bsp or mkadmin
2. Stop all MK services on the database server. Leave your database services
running.
(0212) Server.
4. The install checks to see if your system has the system files required for this
release of MK. If it does not, the following information dialog box opens:
Upgrading MK 5–13

dialog box opens:

MK 8.4 (0011) Server.
9. The Welcome dialog box opens:
Click Next.
box opens:

Upgrading MK 5–15


Select the system you want to upgrade and click Next.
Read the upgrade notes.

13. Click Next.
Make sure that only the MK Database Server component is selected. You
can change the default destination folder by clicking Browse.
Upgrading MK 5–17
14. Click Next.

15. Click Next. The upgrade searches for the database; it displays informational
messages if it doesn’t find it. You can choose to continue with the upgrade if
these messages display. When this process is complete, one of the following
dialog boxes opens (depending on the database you are using):
Ingres II
Oracle 8.0
Oracle 8i
and
Oracle 9i
Microsoft SQL
Server 2000 and
SQL Server 7 0
Upgrading MK 5–19
16. Click Next.
Enter the name of the MK application server. Note that the server name is
case sensitive in MK. You must enter it exactly as it was named on your
Windows NT domain. Check your Network Neighborhood Properties for
verification. Click Next.
The upgrade process copies files to the MK directories and installs new MK
services. The upgrade process can detect and correct certain situations that
prevent the install from completing. If this happens, the upgrade process
prompts you to determine whether you want to restart the process; choose
Yes to continue. If a failure occurs again, report the problem to Technical
Support for further analysis.
When this process is complete, the Setup Complete dialog box opens. Select
the option to restart your computer and click Finish. After the system
reboots, you can install the application server on another machine.
Upgrading the Application Server
The application server is the machine on which you installed the MK application.
⇒ To upgrade an existing version of MK for Windows NT on the application

server:
1. Log onto the Windows NT server machine as user bsp or mkadmin
2. Stop all MK services on the application server.
appear automatically. To access it, on the Start menu, click Run and enter
(0212) Server.
Upgrading MK 5–21
5. The MK System Files Setup Welcome dialog box opens. Click Next to
continue.
6. An Information dialog box opens. Click Next to continue.
7. The system files are copied to your computer. When finished, a dialog box
opens informing you that setup has finished copying files to your computer.
MK 8.4 (0011) Server.
9. A Welcome dialog box opens:
box opens:


Upgrading MK 5–23
Select the system you want to upgrade and click Next.

Review the upgrade notes.
13. Click Next.
Make sure that only the MK Application Server component is selected. You
Upgrading MK 5–25
15. Click Next.
Select the version of MK you want to install on your system. Choose the
customization that matches what is currently installed for your system.
16. Click Next.
18. Click Next.
Upgrading MK 5–27
19. Click Next.
or choose None.
20. Click Next.
21. Click Next.
Enter the name of the MK database server.

22. Click Next.
Enter the password information. Click Next.

Upgrading MK 5–29
The upgrade process copies files to the MK directories, installs new MK
services, and runs the Import Data Dictionary session to import the MK
component. This process can take several hours, depending on the speed
and memory of your system.
The upgrade process can detect and correct certain situations that prevent
the upgrade from completing. If this happens, the upgrade process prompts
Upgrading the interBiz Desktop
The final step you need to take is to install the interBiz Desktop client on a
Microsoft Windows workstation.


Installing the MK Client Classic
⇒ To install the MK Windows CW client:

2. Click MK Client Classic.
3. Follow the instructions that appear to install the MK Windows CW client.
Upgrading MK 5–31
After Upgrading
After Upgrading
Before You Begin If you are using a European release of MK, refer to the Migration Guide before
performing any of these tasks.
Perform the following tasks after upgrading MK:
■ Re-license all software components by running the Configure Application
(ttiex3225m000) session. Refer to the section Enabling the Software in
Chapter 6, “After Installing MK,” for more information on running this
session.
■ Add a package combination for the MK8.4 VRCs.
■ Define production and development VRCs that are derived from the MK 8.4
VRCs and create the new package combinations.
■ Merge any customizations into the new package combinations.
■ Convert all companies to the new package combination using the Change
Package Combination by Company (ttaad1101m000) session. Refer to the
MK Migration Guide for a complete list of steps to perform to complete the
migration of a company.
■ Convert all users to the new package combination by running the Change
Package Combination for Users (ttaad2200m000) session. Convert to
runtime for all users.
Refer to the MK Migration Guide for more information on performing these tasks.
The upgrade process can detect and correct certain situations that prevent
the upgrade from completing. If this happens, the upgrade process prompts
Upgrading the interBiz Desktop
The final step you need to take is to install the interBiz Desktop client on a
Microsoft Windows workstation.


Upgrading MK 5–33
After Upgrading
Installing the MK Client Classic
⇒ To install the MK Windows CW client:

2. Click MK Client Classic.
3. Follow the instructions that appear to install the MK Windows CW client.
After Upgrading
Before You Begin If you are using a European release of MK, refer to the Migration Guide before
performing any of these tasks.
Perform the following tasks after upgrading MK:
■ Re-license all software components by running the Configure Application
(ttiex3225m000) session. Refer to the section Enabling the Software in
Chapter 6, “After Installing MK,” for more information on running this
session.
■ Add a package combination for the MK8.4 VRCs.
■ Define production and development VRCs that are derived from the MK 8.4
VRCs and create the new package combinations.
■ Merge any customizations into the new package combinations.
■ Convert all companies to the new package combination using the Change
Package Combination by Company (ttaad1101m000) session. Refer to the
MK Migration Guide for a complete list of steps to perform to complete the
migration of a company.
■ Convert all users to the new package combination by running the Change
Package Combination for Users (ttaad2200m000) session. Convert to
runtime for all users.
Refer to the MK Migration Guide for more information on performing these tasks.
Chapter
After Installing MK
6
Overview .................................................................................... 6–1

Adding Users ................................................................................ 6–2
Adding Users to the Ingres II Database ...................................................... 6–3
Adding a User to the Ingres Database Group in MK .......................................... 6–4
Adding Users to the SQL Server Database and Database Group ............................... 6–5
Adding Users to the Oracle Database ....................................................... 6–5
About Passwords ..................................................................... 6–6
Adding a Remote User File ................................................................ 6–6
Adding a Printer .............................................................................. 6–7
Licensing the Software ........................................................................ 6–9
Licensing Checklist........................................................................ 6–9
License Manager Overview ............................................................... 6–10
Maintaining the Commercial Function ..................................................... 6–11
Configuring the Tools Functions........................................................... 6–12
Generating the Security Code ............................................................. 6–13
Printing and Faxing a System Configuration Report ......................................... 6–14
Enabling the Software .................................................................... 6–15
Entering the Validation Keys .......................................................... 6–15
Confirming the Configuration Has Not Changed ........................................ 6–15
Validating the Tools .................................................................. 6–15
Verifying the Shared Memory and License Services...................................... 6–16
Configuring the Application .......................................................... 6–17
About Patching Objects ................................................................... 6–18
Adding Additional Package Combinations ..................................................... 6–20
Adding a Package Combination ........................................................... 6–20
Defining Package Combinations ........................................................... 6–21
Installing Demo Companies .................................................................. 6–22
Accessing Demo Companies .............................................................. 6–24
Creating Help ............................................................................... 6–25
Contents iii
Changing the Date Format ................................................................... 6–26
Creating a New Database .................................................................... 6–26
iv MK Installation and Upgrade Guide for Windows 2000 and Windows NT

Chapter
After Installing MK
6
Overview
This chapter describes the tasks you need to perform after installing MK. These
tasks include:
■ Adding users
■ Adding a printer
■ Licensing the software
■ Adding additional package combinations
■ Installing demo companies
■ Creating help
■ Changing the date format
■ Creating a new database
In addition, this chapter tells you what you need to do if you are using the
Advanced Finance Option for MK.
After Installing MK 6–1

Adding Users
Adding Users
This section gives you general instructions for adding each MK user. It then tells
you how to add a user to the Ingres, Microsoft SQL Server, and Oracle database
and database groups. Finally, it tells you how to create a remote user file for
user mkadmin; this is necessary if you are using a dual-server configuration.
⇒ To add each MK user:

1. Define the user in Windows NT. Add the user to the domain used for MK.
2. If you are using Ingres II, use the Accessdb utility to add MK users to the
Ingres database; see Adding Users to the Ingres II Database section for
instructions. Use the oping_maint utility to add MK users to the Ingres
database drivers user list; see Adding a User to the Ingres Database Group
for instructions.
If you are using SQL Server, use the mssql_maint utility to add MK users to
the SQL Server database and to the database group.
If you are using Oracle, use the SQL*Plus utility to add MK users to the
Oracle database. See Adding Users to the Oracle Database later in this
section for instructions.
3. Define the user in MK. See the System Administrator’s Guide for instructions
on how to define a user in MK.
Adding Users
Adding Users to the Ingres II Database
To add an MK user to the Ingres II database you must log onto the database
server machine as the Ingres administrator. The database server is the machine
on which the Ingres II database is installed.
Before You Begin You must be logged on as ingres user in order to perform these tasks.
⇒ To add a user to the Ingres database:

1. From the desktop on the database server, double-click the Accessdb icon:
2. Press Shift+F3 to display the Users Catalog, which lists all users currently
defined in the Ingres database.
3. Press Shift+F1 (Create) to display the User Information dialog box:
4. Enter the user name and Y in any permissions you want to assign. Press F3
(Save) to save the user information. Answer Y to the prompt, and press
Enter to save your changes. Press F10 to exit.
Note: For more information about the Accessdb utility, see the Ingres Database
Administrator’s Guide.

Adding Users
Adding a User to the Ingres Database Group in MK
Use the oping_maint database administration utility to add MK users to the

Ingres database group in MK.
⇒ To add a user to the database group:

1. Log onto the database server.
2. From the Start menu, select Run, and enter the following command:
oping_maint -a<MK user> -G<group> [-B<%BSE% path>] –y<MK system name>
where the MK user is the name of the user you are adding, and the group is
the name of the database. You can also use the following command:
oping_maint -a<MK user> -G<group> –y<MK system name>
For example:
oping_maint -a johndoe -G mk –y MKMANUFACTURING
Note: The user names and switches (-a, -G, and so forth) used above are case
sensitive.
Adding Users
Adding Users to the SQL Server Database and Database Group
Before You Begin You must install MK before adding any users and groups. This is because the
MK installation program automatically adds the mk group and mkadmin user.
Use the mssql_maint database administration utility to add your MK users to the
SQL Server database and to the database group.
⇒ To add an MK user to the SQL Server database and the database group:
1. Log onto the database server.
2. From the Start menu, select Run and enter the following command:
mssql_maint -a<MK user> -M<system user> [-P<system user password>] –G<group> -
P<group password> -y<MK system name>
where the MK user is the name of the user you are adding, and the group is
the name of the database.
Adding Users to the Oracle Database
Add the following users to the Oracle database:

■ mk as dba
■ mkadmin with connect and resource privileges
■ mk_g with dba
⇒ To create users:
1. Connect to the Oracle server as dba. Start the SQL*Plus utility and log on as:
■ User name: internal
■ Password: <internal password>
■ Host string: <database alias>
2. Create mk and mk_g as database administrator (dba) by entering:
create user mk identified by <password>;
grant dba to mk;
create user mk_g identified by <password>;
grant dba to mk;
3. Create mkadmin with resource privileges by entering:

create user mkadmin identified by <password>;
grant connect, resource to mkadmin;

Adding Users
About Passwords
To facilitate the installation, you can temporarily use the same name for the user
name and password as is shown in the example below:
User Name Password

mk mk
root root
mkadmin mkadmin
mk_g mk
After the installation is completed and you want to change the passwords, make
sure you change the Oracle database passwords before you change the Oracle
driver passwords.
Adding a Remote User File
If you are using a dual server configuration, you must create a remote user file
for the user mkadmin. This file is used by the Print Server service and other MK
utilities when connecting to the database server.
⇒ To create a remote user file for user mkadmin:

On the application server, run the utility camk3rem.exe from the mk\bse6.0\bin
directory:
Adding a Printer
Adding a Printer
Before you begin, you must set up a local or remote printer in Windows NT.
When adding a printer, you first need to install the printer on the Windows NT
server; then you set up the printer in MK.
⇒ To install the printer on the Windows NT server:

1. From the Start menu, select Settings, and then Printers. Double-click the
Add Printer icon.
2. Select My Computer. You need to select this even if the printer is not
installed physically on the Windows NT server. Next you will get a list of
available ports.
3. Perform one of the following procedures, depending on whether the printer
is installed on the server or is new:
■ If the printer is currently installed (or has been installed previously):
− Locate the port with the network address of the printer to which you
want MK to print. Place a check mark in the box next to it and click
Next.
− Select the manufacturer and model of your printer and click Next.
− Indicate whether to keep or replace the existing driver and click
Next.
− Provide a name for your printer. This name must be eight characters
or less; it can include underscores. Click Next.
− The printer does not need to be shared in order for MK users to
access it through MK. Indicate this and click Next. Print a test page
and click Finish.
■ If the printer has not been installed on this server before:
− Click Add Port. Select Local Port and click New Port. Enter the port
name; this is the Windows network address of the printer you are
installing. Click Close and then click Next.
− Select the manufacturer and model of your printer and click Next.
− If prompted, indicate whether to keep or replace the existing driver
and click Next.
− Provide a name for your printer. This name must be eight characters
or less; it can include underscores. Click Next.
− The printer does not need to be shared in order for MK users to
access it through MK. Indicate this and click Next. Print a test page
and click Finish.

Adding a Printer
⇒ To set up the printer in MK:

1. Start MK. Access the Maintain Device Data (ttaad3100m000) session:
2. Enter values in the following fields:

■ Device Type —printer.
■ Driver—portrait or landscape.
■ Device Queue—printer name in the NT Printers folder.
■ Paper Type—select your paper type.
Save this information.
3. Exit MK.
4. From the Start menu, select Settings, and then Control Panel. Double-click
the Services icon. Choose the MK Print Server service. Click Stop if it has
already started running.
5. Click Startup. In the Startup Type box, select Automatic. In the Log On As
box, select This Account and enter mkadmin. Enter the correct password for
user. Click OK.
You only need to perform this step once. If you are adding additional
printers just stop the MK Print Server service and then restart it after waiting
a minute for the new printer to become active.
6. In the Services window, click Start.
If you are installing a printer attached to a Novell Netware printer, add user
mkadmin to the Novell user list. The Novell user mkadmin must have the same
password as the Windows NT user.
If you are installing a printer on a client workstation, make sure that the printer
is shared on that workstation and that the workstation is turned on when the
printer needs to be available.
Licensing the Software

This section describes the function of the license manager and tells you how to
license your software. You should perform the tasks in this section as soon as
possible after installing the software.
You must license the software on the application server.
Licensing the software consists of:

■ Maintaining the commercial function
■ Configuring the Tools functions
■ Generating the security code
■ Printing and faxing a system configuration report
■ Enabling the software
■ Patching program objects
Each of these tasks is described in greater detail in this section. Note that some
of these tasks are performed from within MK using System Management
sessions and others from Windows NT using the Control Panel.
Licensing Checklist
Session/Task Description
ttiex3102m000 Maintain Security Code Validation Keys
ttiex3100m000 Maintain Requested System Configuration
ttiex3101m000 Maintain Requested System Configuration (Tools)
ttiex3400m000 Print Requested System Configuration
Fax security code to SSA Fax the report output to SSA Global Technologies
Global Technologies
Receive validation codes SSA Global Technologies will fax back a form
from SSA Global similar to the Security Code form with the
Technologies validation codes to authorize the software
ttiex3220m000 Tool Set Validation (enables the binaries)
Verify the license service Verify the License Service and Memory Service
ttiex3225m000 Configure Application (patch the program objects
that you are authorized to run; this is the only task
that needs to be completed after an update

License Manager Overview
All available software and tools are shipped on the distribution media that
comes with MK. To control use of the software, a license manager is used.
Once installed, you run a series of sessions to select the products you have
purchased and to generate a license request form. You fax this form to SSA
Global Technologies, who will fax back a validation key upon approving the
request. You enter the validation key to enable the software.
The license manager controls the following components:

■ Application functions (Purchasing, Sales, and so forth)
■ Tools (Foundation, Customizer, and Developer)
■ User interfaces and their associated number of users (ASCII, graphical)
■ Database interfaces (Ingres II, Microsoft SQL Server, Oracle)
■ Network connectivity
After the initial installation, the software is temporarily activated for a period of
14 days, after which the software is deactivated. It is therefore very important
that you generate the security code as soon as possible and fax it to SSA Global
Technologies to avoid having your software expire.
Maintaining the Commercial Function
⇒ To maintain the commercial function you have purchased:

1. Access the Maintain Requested System Configuration (ttiex3100m000)
session:
2. Click Modify Record to access the Runable field for the Foundation
commercial function.
3. Select Yes or No based upon the contents of the license key notification form,
then press Tab. The cursor moves to the From Date field.
4. Enter the date from which the license is valid. Press Tab to move the cursor
to the End Date Column.
5. Enter the date through which the license is valid. Press Tab. The cursor
returns to the Runable column for the next line.
− For products that you have not purchased, enter No in the Runable field
rather than leaving the entry blank. If you enter No in this field, you are
not prompted for Start or End dates.
− If you have previously entered a date to the From or End Date field,
pressing Tab automatically enters your previous value.
6. Continue performing this task until all the commercial functions are filled in.
For certain modules (td and ti, for example) not all the commercial functions
can be displayed on one screen. To get the next screen of information, click
Next.
7. Once all the commercial functions have been entered for the package, select
the View Change View Field menu command. Tab to the Package field and
zoom to select the next package.

8. Continue performing this until all packages have been filled (qa, tc, td, tf, ti,
ts, and tt).
At the end of this process, you should have entered a value to all the
commercial functions and your data should reflect the commercial functions
on your form.
9. Click Close to save your data and leave the session.
Configuring the Tools Functions
⇒ To specify the Tools configuration:

1. Access the Maintain Requested System Configuration (Tools)
(ttiex3101m000) session.
For this session, a single start and end date is specified and is used for each
of the options on the screen.
2. From the View menu, select Change View Field.
3. Enter tt in the Package field.
4. Enter the start and end date.
5. Specify the number of users for each user interface. The Runable flag is
automatically set to Yes if the value is greater than zero. If you enter 0, the
flag is set to No.
For Ingres Server Ingres and the network manager, enter Yes.
Note: Check file licence6.0 in %BSE%\lib to ensure that the file contains the
application server name.
Generating the Security Code
Before you begin, you should have MK installed and ready to run. In addition,
the details of the configuration you have purchased should either be included
with the distribution media or arrive separately in the license key document.
This document contains essential details required for licensing the software.
⇒ To generate the security code and validation keys:

1. Access the Maintain Security Code/Validation (ttiex3102m000) session:
2. Enter the customer code, license code (a number greater than 100), a
sequence number of 1, and organization name.
3. Leave the security code and validation keys blank. These codes will be
populated later.
4. Click Close to save your data and exit the session.

Printing and Faxing a System Configuration Report
Once you have completed the preceding sessions, print a System Configuration
report and fax the results to SSA Global Technologies.
⇒ To produce a System Configuration report:

1. Access the Print Requested System Configuration (ttiex3400m000) session:
2. The customer code and license code display. Click Execute to start the print
process.
The output of the report contains a summary of the components requested
plus a security code consisting of a series of digits.
Note: Every time this print session is run, a different security code is
generated even if the components have not been altered between printing.
Do not run the session between generating the output and validating the
software since validation of the software can be done only on the last
security code generated.
3. Fax the output of this session to SSA Global Technologies Total License Care.
If you are unable to print the report, ensure that the data entered into MK
exactly reflects the details on the license key document before copying down
the security code onto the original form and faxing this back to SSA Global
Technologies. If you are unable to print the report, you can print to device
ASCIF and view and print the file with Wordpad.
4. After approval you will receive a validation code from SSA Global
Technologies and can then enable the software.
Enabling the Software
After you receive the validation code, you perform the following tasks to enable
the software:
■ Enter the validation keys
■ Confirm configuration has not changed
■ Validate the tools
■ Verify the license service is running
■ Configure the application
Entering the Validation Keys
⇒ To enter the validation keys:

1. Access the Maintain Security Code/Validation Key (ttiex3102m000) session.
2. Enter the validation codes exactly as it appears on the fax.
3. Click Close to save the changes and exit the session.
Confirming the Configuration Has Not Changed
Confirm the configuration has not changed from the fax sent to SSA Global
Technologies Total License Care. If it has, you need to rerun the Maintain
Requested System Configuration (ttiex3100m000) and Maintain Requested
System Configuration (Tools) (ttiex3101m000) sessions.
Validating the Tools
After you have entered the validation codes, you need to validate the tools. Use
the Validate Tool Set session to create a brand file called /.brand/brand6.0 in the
root file system. This file contains information about the user interfaces,
commercial functions with effective date windows, databases, the number of
users licensed as well as specific hardware information concerning the machine
MK is running on.
⇒ To validate the tools:

1. Access the Validate Tool Set (ttiex3220m000) session.
2. Click Execute.
3. Click Close to exit the session.
If there are errors during this stage, check that you have the same exact
configuration as specified in the validation form.
Warning! This file should not be moved, renamed, or tampered with in any way.

Verifying the Shared Memory and License Services
After validating the tools you, log off MK to license your software. To do this,
you need to perform the following sequence of steps:
1. Stop the MK Server service
2. Start the CAMK License service
3. Restart the MK Server service
⇒ To stop the MK Server service:

1. From the Control Panel, double-click the Services icon.
2. Select MK Server.
3. Click Stop and then click Close to exit.
⇒ To start the CAMK License service:

2. Select CAMK License Service.
3. Change the Startup mode to Automatic.
4. Click Start and then click Close to exit.
⇒ To restart the MK Server service:

2. Select MK Server.
3. Click Start and then click Close to exit.
Configuring the Application
After the License server starts, log back onto MK to complete licensing the
software. The final step in enabling the software is to run the Configure
Application session.
⇒ To configure the application:

Access the Configure Application (ttiex3225m000) session.
The relationship between the commercial functions purchased and the objects is
held in the %$BSE%\sec\standard.secu file. All objects belonging to commercial
functions not authorized to be used are disabled. You receive an error message
if one of these sessions is invoked. When using this session:
■ All users must be off the system before running this session.
■ The license service must be running in order to access this session.
■ Always choose to patch Standard and Remaining Objects.
■ In addition to running this session during the initial installation process, you
must run this session every time you apply an update.

About Patching Objects
This section describes how objects are patched when they are installed:
■ The start and end dates when the object can run. In this particular case, the
start date is the date of installation and the end date is 14 days from the date
of installation.
■ A temporary flag which allows the objects to run without the license service
running.
Temporary vs. If the license service is not active, MK assumes that the software is temporarily
Permanent Objects licensed and, therefore, looks for a temporarily patched object.
In the licensing process, the Configure Application session patches the objects
with the start and end date specified in the Maintain Requested System
Configuration session. The objects are also flagged as permanent. Once specified
as permanent, the object can be run only if the service is running. Along with the
permanent flag, the cursor and license codes are also added to the object.
Patching Objects The Patch Object after System Crash (ttiex3228m000) session patches all the
after System Crash objects with a temporary flag and sets the end date to be seven days after
execution. Since the objects are flagged as temporary, the license service can
not be running.
Note: Only permanently patched objects can be patched with this session.
Running this session twice in succession without permanently patching the
objects again will not work.
Patching Objects If objects are moved from another system such as a priority patch from SSA
after Error Solving Global Technologies, they will not run if the customer and license codes are
different than those held in the brand file.
Run the session Patch Objects after Error Solving to patch the new objects with
the correct customer code, license code and start and end dates.
⇒ To access the Patch Objects after Error Solving session:

1. Access the Patch Objects after Error Solving (ttiex3226m000) session:
2. Select Patch Objects (Standard) and Patch Objects (Remaining) and then
select the object(s) to be patched.

Adding Additional Package Combinations

One package combination is added during installation. If you require other
package combinations, add them at this time.
All installations should have the BASE Package Combination. If you did not
choose the 842BASE package combination when executing the installation script,
you should add it now.
Adding a Package Combination
⇒ To add a new package combination:

1. Log on as user mkadmin.
2. Access the Maintain Package Combinations (ttaad1120m000) session:
Enter the necessary information. Change the table definition path to

${BSE}/dict6.0 for each package combination.
Defining Package Combinations
If you add a new package combination, you need to indicate the package VRCs
that make up the package combination.
⇒ To define the package VRCs for a package combination:

1. Access the Maintain Packages by Package Combinations (ttaad1121m000)
session:
2. Add the package VRCs to the new package combination. Click Execute.
3. Run the Maintain Package VRCs (ttadv1111m000) session:
Make sure that each package VRC is integrated with its respective package
combination. For each package VRC the Integration with Package VRCs in
Pack Combination field should display the associated package combination.
Note: When maintaining package VRCs, be sure that the VRC points to the
correct parent package combination.

Installing Demo Companies

MK comes with demonstration databases distributed as flat ASCII files. This
section describes how to install these tables.
If You are Using Ingres If you are using Ingres, you need to perform the following procedure before
installing demo companies:
1. Run CBF.
2. Configure the DBMS server.
3. Edit the default_page_size to equal 4096 and press Enter.
4. Arrow down to max_tuple_length and edit to equal 4096. Press Enter.
5. Enter the DBMS Caches.
6. Arrow down to DMF Cache 4k and change the Status value to On.
7. Exit the DBMS Server, choosing Yes to save changes.
8. Exit the CBF.
9. Restart Ingres.
⇒ To install the demo companies:

1. Log on as mkadmin or as a user who points to the new package combination.
For example, if logged on as mkadmin, point mkadmin to US package
combination before installing demo tables for US companies. Point
mkadmin to base package combination before installing demo tables for base
companies. (If necessary, create a new user to point to the new package
combination.)
2. Run the Install Demo Tables (ttiex1290m000) session to install all of the
demo tables that reside in the directories under tables6.0 corresponding to
the package VRC associated with the user.
3. For BASE Package VRC, enter the following in the fields:

■ Company From: 912
■ Company To: 913
■ Remove Dumps after Installation: No (do not check box)
■ Overwrite Existing Tables: No (do not check box)
For US Package VRC, enter the following in the fields:
■ Company From: 914
■ Company To: 915
■ Remove Dumps after Installation: No (do not check box)
■ Overwrite Existing Tables: No (do not check box); enter Yes if tables
were installed earlier

Accessing Demo Companies
Before accessing the demo companies, you need to assign the currency code for
each of the companies installed.
⇒ To access demo companies:

1. Access the Maintain Companies (ttaad1100m000) session:
2. To convert to runtime, click Zoom.
Creating Help
Creating Help
After you have created a developer-level user and set up basic text parameters
such as default text groups and text windows, you should activate the online
help system. You do this by running the Create Runtime Help (ttadv5230m000)
session. This session loads the help texts associated with the components and
languages you specify into the runtime data dictionary.
⇒ To activate online Help:

1. Log on as a developer-level user.
2. Access the Create Runtime Help (ttadv5230m000) session.
3. Specify the range of package VRCs, languages, and components for which
help should be created.
4. Click Execute to process.
This session may take some time to complete its processing, especially when
creating help for the Tools (tt) package. However, you must run this session to
make online help available to users.

Changing the Date Format
Changing the Date Format

The date format is set with the language.
⇒ To modify the date format for your language:

1. Access the Maintain Languages (ttaad1110m000) session:
2. Click Zoom to go to the Convert to Runtime Data Dictionary menu, then

click Execute to process. You need to exit and re-enter MK to see the effect of
this change.
Creating a New Database

⇒ To create a new database:
1. Add a company with the Maintain Companies (ttaad1100m000) session.
2. Run the Convert to Runtime Data Dictionary (ttaad4200m000) session.
3. Exit and re-enter MK.
4. Run the Create Tables (ttaad4230m000) session for each company.
5. Add static data.
Setting Up the Radio Frequency
Appendix
A Devices Supported by MK
Overview ................................................................................................................................................................ A–1

Configuring the Symbol RF Device .................................................................................................................... A–2
Configuring the Hardware ........................................................................................................................... A–2
Configuring the Spectrum 24 Access Point ......................................................................................... A–3
Configuring the Symbol Hand-Held Device....................................................................................... A–4
Configuring the Software.............................................................................................................................. A–5
Symbol Enabler and Symbol STEP Software ...................................................................................... A–5
MK Spawn Service.................................................................................................................................. A–5
User Attributes ........................................................................................................................................ A–6
Registry Entries ....................................................................................................................................... A–6
RF Device Troubleshooting .......................................................................................................................... A–6
Configuration Telnet............................................................................................................................................. A–7
Installing Microsoft Telnetd ......................................................................................................................... A–7
Installing and Configuring Pragma Telnetd .............................................................................................. A–8
Configuring the MK Environment .............................................................................................................. A–9
MKAS Environment Variables.............................................................................................................. A–9
VT Terminal Emulator Environment Variables.................................................................................. A–9
New Technology Environment Variables ......................................................................................... A–10
VT Terminal Emulator Shell Commands .......................................................................................... A–10
Configuring a Remote Database ................................................................................................................ A–10
Manually Executing VTController ............................................................................................................ A–11
Contents i
Setting Up the Radio Frequency
Appendix
A Devices Supported By MK
Overview
MK supports the following Radio Frequency (RF) devices:
■ Symbol
■ Telnet
This appendix describes how to install and configure the hardware and software
on these RF devices.
All devices require the following:

■ Downloading emulation software to a hand-held device
■ Configuring an access point
■ Configuring a hand-held device
■ Configuring a radio frequency driver on the MK server
Setting Up the Radio Frequency Devices Supported By MK A–1

Configuring the Symbol RF Device

This section tells you how to configure the Symbol hardware and software. It
also provides solutions to possible problems that may occur.
⇒ To set up the Symbol RF device:

1. Install the Symbol Enabler software on a Windows NT system.
2. Configure the Symbol Enabler Access point device.
3. Install the Symbol Enabler software on the PDT 3140 hand-held device.
4. Modify the MK Spawn Server to start the Symbol Enabler software, if you
have not selected this option during the initial installation of MK.
Each of these tasks is described in more detail in this section.
Configuring the Hardware
You must configure two hardware devices from Symbol:

■ The Spectrum 24 Access Point, or gateway
■ The Symbol hand-held terminal
For additional information, refer to the Symbol Installation Guide.
A–2 MK Installation and Upgrade Guide for Windows 2000 and Windows NT
Configuring the Spectrum 24 Access Point
Before You Begin You need a special null-modem serial cable. Connect one end of the cable to
COM2 on the server and connect the other end to the serial port on the Access
Point.
⇒ To configure the Access Point

1. Use HyperTerminal to dial into the Access Point. Your HyperTerminal port
setting should be:
19200, 8, NONE, 1, NONE, ANSI
2. When connected to the Access Point, choose the Enter Admin Mode option.
The password is Symbol
3. Select AP installation.
4. Configure the IP address, the default gateway, and so forth. You will need
the IP address for the AccessPoint and the IP address of the NT server.
5. Accept the defaults. Save your changes and exit.
6. Ping the IP address from an MS-DOS prompt to verify the configuration.
7. After you have downloaded the software, you must connect the Access Point
to the network.

Configuring the Symbol Hand-Held Device
To configure the Symbol hand-held terminal, you perform the following tasks:
1. Download the software from the server
2. Run a menu-driven program to configure IP addresses and masks into the
flash on the terminal
⇒ To download the software:

Note: This procedure is described in detail in the Symbol Installation Guide.
1. Connect a network cable from the server to the hand-held terminal.
2. Enter the terminal command mode. To do this, turn off the terminal. Then,
while pressing and holding F and I, press and release the Power key, and
then release F and I.
3. Configure the port setting on the Symbol Terminal. (Refer to the Symbol
documentation for the exact configuration.)
4. Configure a COM port setting on a PC using HyperTerminal.
5. Use the serial cable provided by Symbol to connect the COM port to the
terminal.
6. Start SendHex program to load the disk image onto the terminal. (Refer to
the Symbol documentation for details.)
⇒ To update the flash:

1. From the main menu of the terminal, select Terminal Configuration. Enter
the following required information (move between fields using the arrow
keys and Enter):
■ Net ID - any unique number
■ Subnet Mask
■ Default Router
■ Terminal IP Address
Press Enter to save and exit the configuration.
2. Select the Host Configuration option. Enter the Primary Server IP address
under Host 1. If you have more than one server, enter it’s IP address under
Host 2, or Host 3. Select CLR to exit and save the configuration.
Configuring the Software
The software needed to run the Symbol RF device must be installed on the MK
server and on the RF hand-held device. You need the following software to run
the RF device:
■ A Symbol service that runs on your NT Server – one of the Symbol Enabler
components
■ A Symbol Terminal Enabler Program (STEP) – one of the Symbol Enabler
components
■ A spawn service that runs on your NT Server – one of the MK system
components
■ An RF client executable that interfaces between your hand-held terminal and
the MK spawn service.
■ A stand-alone program that configures the services on your NT server.
Symbol Enabler and Symbol STEP Software
To install the software supplied by Symbol Technologies, you first install the
Enabler software and configure it to run with MK. Then you install and
configure the Symbol STEP software on the handheld scanner. If you are using
more than one handheld scanner, you must do the STEP installation for each
device.
The Enabler software, or Symbol Service, comes on a diskette from Symbol. You
install it using a setup program on the diskette, which you can access from the
Windows NT desktop.
You must install the Symbol STEP software on a Windows 95 machine.
All the information needed to install the software is in the Symbol Installation
Guide.
MK Spawn Service
The MK spawn service and associated libraries are installed with MK. Since
there is a dependency between the spawn service and the Symbol service, you
must perform the following steps to ensure that the dependency is enabled:
1. From the DOS command prompt, enter the following command to change to
the etc subdirectory for MK:
cd {BSE}\etc
2. Execute the following command:

instsrv “MK Server” “Symbol Enabler” add_dependency

User Attributes
After you create the RF user accounts for MK, you must verify that the accounts
start with the RF main start menu. In the Main Start Menu in Create User
account field, change the value to
tdawm60000001
Registry Entries
By default, the RF listening device on the MK spawn service is always enabled.

You can disable it manually by making an entry in the Windows NT registry.
All the service registry entries are in the registry HKEY_LOCAL_MACHINE.
Add a REG_DWORD value of RFEnable under the key:

SYSTEM/CurrentControlSet/Services/MK Server
1 – Enables the RF Device
0 – Disables the RF Device
RF Device Troubleshooting
Problem You logged onto MK and didn’t have your start menu set to:
tdawm60000000
and you see garbage on your Symbol Terminal screen.
Solution Abort out of the Symbol Terminal menu. Start MK and fix the start menu for
that account. Then reboot the Symbol Terminal. (This is because the terminal is
put into All Capital mode. The only way to clear this is to reboot the device.)
Problem You get a “RECV TIMEOUT 60h” on your Symbol Terminal Screen.
Solution The timeout occurred because the MK Server you wanted to access was too busy
to acknowledge your terminal input. You can:
■ Press R to retry. If you are not successful after two or three attempts, try the
next solution.
■ Press CTL to abort the session, then try to log in later.
Configuration Telnet
You can use the information provided in this section to configure any hand-held
device that can emulate a VT100 terminal. This requires a telnetd service
running on the MK server.
This section tells you how to:

■ Install both the Microsoft telnetd and the Pragma telnetd; Pragma telnetd is
the recommended telnetd for the MK server.
■ Configure the MK environment
■ Configure a remote database
■ Execute VTController manually
Installing Microsoft Telnetd
⇒ To install Microsoft telnetd:

1. Put the Windows NT Services for UNIX disk in the CD-ROM drive.
2. Click Next on the Setup Wizard screen.
3. On the License dialog box, click I agree to accept the licensing terms and
then click Next.
4. Click the Custom Setup option.
5. Install all listed components.
6. Accept the default path and then click Next.
7. Click Finish to copy the files.
When the installation successfully completes, a message informs you that the
registry has been updated and a program group has been added to the Start
menu. Click OK.
You must reboot your machine for the installation to take effect.

Installing and Configuring Pragma Telnetd
To install the Pragma telnetd, follow the instructions provided by Pragma.
After installing the software, perform the steps in this section to configure the
daemon for the MK server by running the InterAccess Manager program. This is
installed under Programs/InterAccess TelnetD Server.
TelnetD – prompts:
1. Remove the Domain Message
2. Remove Ask For Terminal Type
3. Remove Show Copyright Information
4. Remove Ask user for Console Mode
5. Remove Ask User for Color Mode
TelnetD – Screen Settings

1. Set Default Rows and Default Columns to match those available by your
hand held device.
2. Remove Pass Control-C to Application
TelnetD – General Settings

■ For MK 8.1 server releases, set the Console Shell Setup Program to:
${BSE}\bin\vt81.cmd
■ For MK 8.1 Technology server release, set the Console Shell Setup Program
to: ${BSE}\bin\vt81nt.cmd
InetD – Configuration
Nothing needs to be done in this section.
Configuring the MK Environment
The MKAs environment variables set the display screen to 8 rows and 20
columns so that the menus fit on the hand-held device screen. Since MKAs.exe
is executed by telnetd, and not the MK server, you need to manually set the
environment variables through a .cmd file.
If you are using MK 8.1 Technology or later, you can configure the vt81nt.cmd
file for use in your MK system. If you are using MK 8.1, you can configure
vt81.cmd.
MKAS Environment Variables
MKAS uses environment variables to limit the size of the display. These are
further explained in the MK style guide. These entries are set in the appropriate
.cmd file in ${BSE}\bin.
The valid entries for design are:

set BA_ROW_DESIGN=4
set BA_COL_DESIGN-40
or:
set BA_ROW_DESIGN=8
set BA_COL_DESIGN-20
The only valid entry for display is:

set BA_ROW_DISPLAY=4
set BA_COL_DISPLAY=40
VT Terminal Emulator Environment Variables
The VT Terminal Emulator needs to know which version of MKAS is running on

the system. This is for backwards compatibility issues.
For MK 8.1, enter:

set MK_VERSION=8.1
For MK 8.1 Technology, enter:

set MK_VERSION=8.1_NewTechnology
Since the VT Terminal Emulator is interpreting the VT100 data stream you need
to set a terminal environment variable
set TERM=vt100

New Technology Environment Variables
If you are using MK 8.1 Technology or later, you need to enter a system name. If
this environment variable is not set, the user will be prompted to enter a system.
Enter the following:

set USERSYSTEM=<desired system>
VT Terminal Emulator Shell Commands
The last three commands in your <MK version>.cmd file must be

cls
VTController.exe
exit
These commands clear the screen, execute the VT emulator, then exit from the
telnetd.
Configuring a Remote Database
Access to a remote database requires an r<use> file.
⇒ To create this file:

1. You must be in the ${BSE}\lib\user directory. Execute:
${BSE}\bin\encrypt > r<user name>
2. Enter your password.

3. Edit the r<user> file. The required fields are:
■ Server name: Set this field to the server name.
■ BSE path: Set this field to the BSE on the server.
■ Domain\user name: Set this field to your domain and user name.
■ The encrypted password created by running the encrypt program. This
is created when you execute encrypt.
■ SUID: Set this field to No.
■ Inherit Logon_name: Set this field to No.
■ System Type: Set this field to WINNT.
Manually Executing VTController
If you have properly configured the Pragma Telnetd, the VTController software
executes immediately after logon. However, there may be times when you need
to run VTController manually.
In order to run the VTController manually, you must copy the vt81(nt).cmd file
to vt.bat. Then you must go into the general configuration menu of the pragma
telnetd and blank out the console shell setup program. (Otherwise, every time
you telnetd in you will automatically run the vt81(nt).cmd program).
⇒ To manually execute VTController:

1. Telnet to the MK server.
2. Log on to the server. The name you use will be used to log onto MK.
3. Set the telnet session to full console support.
4. Set the terminal type to VT100.
5. Change to your ${BSE}\bin directory.
6. Runt he batch file VT.bat. This file sets the environment configuration and
then executes the VTController program. You will be asked what MK
system to log on to.

Appendix
Troubleshooting
B
Detecting and Correcting Problems ............................................................. B–1

Understanding the Install and Upgrade Processes ............................................... B–2
Copying Files to the MK Server(s) .......................................................... B–2
Installing MK Services ..................................................................... B–2
Adding the User and the Group ............................................................ B–3
Starting MK to Import the Data Dictionaries ................................................. B–3
Creating the Package Combinations and Generating the Runtime Help ........................ B–3
Uninstalling MK .............................................................................. B–4
Uninstalling an MK Upgrade ........................................................... B–4
Contents i
Appendix
Troubleshooting
B
You can effectively troubleshoot the MK setup process if you understand the
install/upgrade process and know how to detect and correct any errors that
might occur.
Detecting and Correcting Problems

The MK setup program is able to detect and correct common problems that
might occur during the setup process. If it finds any such errors, the setup
program will ask for confirmation to continue with the setup. Select Yes to that
prompt. The setup program will complete the remaining steps. If the failure
occurs again, you must examine the MKInstall.log file that is in the
\mk\bse6.0\log directory on the drive where MK is installed. This file records
all actions taken during the setup process and indicates completion or failure of
each step. Additional log files that you can examine are described later in this
appendix.
Troubleshooting B–1
Understanding the Install and Upgrade Processes

This section briefly describes the major steps executed by the install or upgrade
process and discusses approaches to troubleshooting problems.
An install executes five major steps:

1. Copies files to the selected drive and directory on the MK server(s).
2. Installs MK services.
3. Adds the user and the group to the MK database.
4. Starts MK to import the data dictionaries.
5. Creates the package combinations and generates the runtime help.
An upgrade executes four major steps:

1. Copies files to the selected drive and directory on the MK server(s).
2. Installs new MK services, if applicable.
3. Starts MK to import data dictionaries.
4. Removes unused MK services.
Copying Files to the MK Server(s)
If files are in use during the copying process, a 623 error may occur. Ensure that
all users have logged out of the system. Reboot the server(s). In some cases you
will see error 132 — if this occurs, abort the install, reboot the server, and start
the install again
Installing MK Services
If the Service Registry is in use during the MK services install process, an error
may occur. If an error occurs, the Control Panel Services applet may be open.
Close the Control Panel and re-install the MK program.
B–2 MK Installation and Upgrade Guide for Windows 2000 and Windows NT
Adding the User and the Group
In order for MK to connect to the database, MK creates configuration files under

the mk\bse6.0\lib directory.
■ For Ingres II, the files are in the mk\bse6.0\lib\openingres directory.
■ For Microsoft SQL Server, the files are in the mk\bse6.0\lib\mssql directory.
During a new install, the database driver utilities are used to add a group mk
and a user mkadmin to the database.
■ For Oracle, the files are in the mk\bse6.0\lib\ora directory.
Error 514 If the pre-installation steps to create the user mkadmin, the user mk, and the
database mk are not properly executed, a 514 error may occur during the Import
Data Dictionary process. Remove the MK installation, re-do the pre-installation
steps and run the install again.
Error 505 If the database is not running or the MK connectivity files are not configured
properly, a 505 error may occur. A 505 error during the import process indicates
that the system could not connect to the database. Start the database if it is not
running. If the database is running, contact Technical Support for further
diagnosis.
Starting MK to Import the Data Dictionaries
The Import Data Dictionary session is used to import the applications and tools
components of the MK product. This process is disk and database intensive.
The process writes two log files in the %BSE%\log directory of the application
server. These files are log.oiex1287 and log.oiex1288. The first part of the
process imports the tools components and creates the run-time data dictionary
for tools. The file log.oiex1287 records the progress for this session. The next
part of the import process brings in the application components and records
progress in the log.oiex1288 file. The application and tools components are
packaged in directories that are named line.####, where # represents a digit. As
each of these line directories is processed, an entry is made in log.oiex1288. If the
session aborts prior to processing all the line.#### directories, the setup
program will take corrective action to rectify a failure and then prompt for
confirmation to complete the import. Select Yes to the prompt. You can also
restart the session by executing the file %BSE%\bin\restart.cmd.
Creating the Package Combinations and Generating the Runtime Help
The last step of the import process creates the selected package combination and
generates runtime help for the various components of the MK system. If the
session aborts prior to completion, you may restart it by running the restart.cmd
file, which is located in the %BSE%\bin directory.
Troubleshooting B–3
Uninstalling MK
Uninstalling MK
⇒ To uninstall a new MK installation from your system:
1. Remove the MK program files, MK services and MK settings from the
Windows NT environment. See below for more information.
2. Remove the MK group from the relational database.
3. Remove all MK users from the relational database.
4. Delete the database "mk."
5. Reboot the system.
For steps 2 through 4, refer to the appropriate relational database guides and the
MK database driver guides for information.
⇒ To remove MK program files, MK services, and MK settings:

From the Control Panel, double-click the Add/Remove Programs icon. Select
the product you want to uninstall (MKMANUFACTURING or MKLOGISTICS).
A dialog box similar to the following opens:
Answer Yes to the prompt. Once this process is finished, use the Windows
Explorer to delete the MK directory, including subdirectories, from the NT file
system.
If the Add/Remove step fails, you must stop and remove the MK services (MK
Print Server, CAMK License Server, and MK Server) from the Windows NT
registry under HKEY_LOCAL_MACHINE\CurrentControlSet\Services. Then
remove the BSE and BSE_TMP environment variables from the Windows NT
system environment; and finally, remove the MK directory including its sub-
directories from the NT file system.
Uninstalling an MK Upgrade
Choosing the Add/Remove Programs function always results in the removal of

the complete MK installation, regardless of whether it is a new install or an
upgrade. The MK software does not allow the removal of an upgrade from an
existing MK system. For this reason, it is strongly recommended that you back
up the entire system including the Windows NT registry, the data in the
database and the MK directories before applying the upgrade.
B–4 MK Installation and Upgrade Guide for Windows 2000 and Windows NT
Appendix
Setting Tax Provider Parameters

C
Setting Tax Provider Parameters ............................................................... C–2

Required Fields ............................................................................... C–3
Tax Conversion for 8.0 US ..................................................................... C–3
Contents i
Appendix

C
The MK Tax Provider allows you to link the MK application to the Quantum
Sales and Use Tax System in the United States VRC. This interface is transparent
to the end user. However, your MK installation has specific tax provider system
administration and application requirements. This appendix explains the
following tasks:
Setting MK Tax Provider parameters
Using MK fields to activate Quantum Sales and Use Tax
The MK Tax Provider is automatically installed during the MK installation

procedure. To install MK, follow the installation instructions in this manual.
During the installation process, the tax provider object for interfacing MK with
the Vertex Quantum product is installed in the following directory:
%BSE%\bin\quantum_api.exe
To ensure the Quantum object is properly defined, edit your

%BSE%\lib\ipc_info file. Search the line for Quantum, and ensure that the path
for Quantum object is %BSE%\bin\quantum_api.exe.
For the MK 8.4 release, these drivers are placed in separate folders under
%BSE%\bin\drivers with directories for:
■ Quantum13 for version 1.3xx
■ Quantum 20 for version 2.0
■ Quantum21 for version 2.1
When you install MK, you will be prompted to choose the version of the
Quantum software installed on your server. The correct executable is then copied
to the %BSE%\bin directory from the %BSE%\bin\drivers directory.
Every release of Quantum must have a different quantum_api6.0 binary. They

are not interchangeable.
Setting Tax Provider Parameters C–1

To link the Tax Provider with the Quantum Sales and Use Tax System, you must
also install Quantum Kits, Data File, GeoCoder File and Tax Decision Maker.
Follow the installation instructions in the Quantum for Sales and Use Tax Installer’s
Guide to install the Quantum Sales and Use Tax System. If you have any other
questions about the Quantum product, please call Vertex technical support.

To establish the link between Tax Provider and the Quantum and Use Sales Tax
System, you must set the MK Tax Provider parameters. Use Maintain Tax
Provider Parameters (tccom9100m000) to set the following parameters:
■ Interface with Tax Provider - Set the Interface with Tax Provider parameters
to Quantum.
■ Path Name Data Files - Set the Path Name Data Files parameter to the
directory path for the Quantum installation. You must define the following
databases in this directory, with exactly these directory/folder names:
− GeoCoder
− Rate
− Register
− TDM
− utils
In the Maintain Tax Provider Parameters session, you must specify a location in
the Path Name field for the Quantum folder.
Quantum has a utilities folder for which you must show the utility path as part
of the specification of the environmental variable, Path, on the application server.
Once you have set these parameters and installed the Quantum Sales and Use
Tax System, the interface between MK and the Quantum Sales and Use Tax
System is established.
C–2 MK Installation and Upgrade Guide for Windows 2000 and Windows NT
Required Fields
Required Fields
The Quantum Sales and Use Tax System requires you to use specific MK address
fields. With MK, you can enter address information in either of the following
ways:
Using the free form address format (for example, the Address 1, Address 2,
Address 3 and Address 4 fields)
Using the customized U.S. address format (for example, the Address 1,
Address 2, City, State, Zip Code, County and City Limits fields)
If you leave the City field blank, MK assumes you have selected the free form
address option and will automatically prompt for the Address 3 field. If you
enter a value in the City field, MK assumes that you have selected the
customized U.S. address option and automatically prompts for the State Zip
Code, County and City Limits fields. City, State, Zip Code and County
information are required for Quantum to determine a GeoCode for the location.
Tax Conversion for 8.0 US

If you are using Quantum as Tax provider in MK applications in the “US” VRC
Companies, install the Quantum Sales and Use Tax System to communicate with
MK applications. If you are an existing Vertex user, contact the Vertex Technical
Support department for details to upgrade your existing Vertex data to Quantum
Tax Decision Maker.
The MK Tax Provider is automatically installed during the MK installation

procedure. It resides in the following directory:
%BSE%\bin\quantum_api6.0
To activate the interface between MK and Quantum, perform the following

steps:
1. Edit the %BSE%\lib\info_file. This file defines the location of the Quantum
object. Find the line for Quantum, and make sure the path for the Quantum
object is %BSE%\bin\quantum_api6.0.
2. Create a directory (for example /MKTAX/QUANTUM) and four

subdirectories to hold the following databases: GeoCoder, Register, Rate,
and TDM. You must create directories with upper and lowercase letters as
shown.
3. Restore the Quantum Kits into the /MKTAX/QUANTUM directory.

Consult the installation instructions in the Quantum for Sales and Use Tax
Installer’s Guide for details on creating the four Quantum databases.
Setting Tax Provider Parameters C–3

Tax Conversion for 8.0 US
4. Activate the MK/Quantum interface by setting the field “Interface with Tax
Provider” to “Quantum” in the session Maintain Tax Provider Parameters
(tccom9100m00). Also, set the Path Name Data Files equal to
/MKTAX/QUANTUM/.
5. Run the session tccom9930m00 (Conversion Program for GeoCodes) to

assign Geocodes, based on the city, state, zip code and county of all
addresses-related MK tables.
To access Quantum tax data, you must use the customized U.S. address format.
If you use the free form address format, MK assumes tax rates are not required,
does not access Quantum tax tables and does not make any tax calculations. For
information on the Quantum Sales and Use Tax System, refer to the Quantum
Sales and Use Tax Decision Maker Taxability Guide.
Note: MK does not allow abbreviations or punctuation for city and county
names. For example, “St. Petersburg” must be spelled out as “Saint Petersburg.”
Refer to the Quantum Geocoder Master List Manual for the correct spelling of cities
and counties.
C–4 MK Installation and Upgrade Guide for Windows 2000 and Windows NT
Appendix Compatibility of MK 8.4 (0212) and
Windows 2000 with Active
D Directory
Active Directory and MK FAQs ............................................................... D–2

Active Directory FAQs ....................................................................... D–3
Contents i
Appendix Compatibility of MK 8.4 (0212) and
Windows 2000 with Active
D Directory
This appendix contains information that certifies that MK 8.4 (0212) Server
supports Active Directory with Windows 2000. All available MK Clients (MK
Desktop, MK Client Classic, Internet Client) are compatible for both releases.
The recommended upgrade procedure for existing MK 8.1 installations running

on Windows NT is to first upgrade MK to the new version, then upgrade NT to
Windows 2000 with Active Directory.
Upgrading a Windows NT domain to a Windows 2000 Domain and upgrading

the MK Server to a Windows 2000 Server does not affect the MK product.
Compatibility of MK 8.4 (0212) and Windows 2000 with Active Directory D–1
Active Directory and MK FAQs
Active Directory and MK FAQs

Q. Is there a change in procedures for setting up MK with Windows 2000 and active
directory?
A. No. You still need to create a Domain User called MKAdmin in the Domain
where MK is installed. Using the Active Directory Users and Computers
utility will now create the user.
Q. Doesn’t MK require that a Primary Domain Controller (PDC) be present?

A. No. The requirement is that the server that MK is installed on is part of a
Windows NT domain. In the case of Windows 2000, it will be part of the
Windows 2000 Domain.
Q. Is it OK to upgrade the PDC on the network servicing MK to a Windows 2000

Domain Controller?
A. Ys. This should have no affect on MK.
Q. Is it OK to upgrade the DNS server to the Windows 2000 Domain?

A. Yes. This should be done when the PDC is being upgraded.
Q. Is it OK to upgrade the MK Server from NT 4.0 to Windows 2000?

A. Yes. MK supports both Native and Mixed mode configurations of Windows
2000.
Q. What security protocol does MK support?

A. MK currently supports NTLM. Support for the Kerberos protocol will be
available in the near future.
Q. Does MK function if the Windows 2000 network security is set to Kerberos?

A. Yes. The system always negotiates the highest level of security that is
supported by the application. The sequences of protocols that are tried are
Kerberos, NTLM and MK Standard signon – in that order.
Q. Does MK support Single signon?

A. Single signon allows an application to use the security context of the logged
on user. This precludes the users from signing on to each application that is
started by those users. The single signon feature of Windows 2000 will be
available in MK in the near future.
D–2 MK Installation and Upgrade Guide for Windows 2000 and Windows NT
Active Directory FAQs

Q. What is Active Directory?
A. Active Directory is an essential and inseparable part of the Windows 2000
network architecture that improves on the domain architecture of the
Windows NT 4.0 operating system to provide a directory service designed
for distributed networking environments. Active Directory lets organizations
efficiently share and manage information about network resources and
users. In addition, Active Directory acts as the central authority for network
security, letting the operating system readily verify a user's identity and
control his or her access to network resources. Equally important, Active
Directory acts as an integration point for bringing systems together and
consolidating management tasks.
Q. Can a Windows 2000 Network exist without Active Directory?

A. No.
Q. Does a Windows 2000 Network Support Primary and Backup Domain Controllers?
A. No. A Windows 2000 Network supports Domain Controllers and Member
Servers. The concept of primary and secondary controllers has been
eliminated. Active Directory allows Windows 2000 domain controllers
function as peers, and clients can make updates to Active Directory on any
Windows 2000 domain controller in the domain. This is a change from the
read-write/read-only roles played by Windows NT Server Primary Domain
Controllers (PDCs) and Backup Domain Controllers (BDCs). The Windows
NT Server domain system supports single-master replication— all changes
must be made on the PDC.
The Windows 2000 operating system supports multimaster replication: all of
a domain’s domain controllers can receive changes made to objects, and can
replicate those changes to all other domain controllers in that domain. A
domain is a directory partition. By default, the first domain controller
created in a forest is a global catalog server, which contains a full replica of
all objects in the directory for its domain and a partial replica of all objects
stored in the directory of every other domain in the forest.
Replicating Active Directory data among domain controllers provides
benefits for information availability, fault tolerance, load balancing, and
performance.
Compatibility of MK 8.4 (0212) and Windows 2000 with Active Directory D–3
Q. What are the two operating modes of Windows 2000 Domains?

A. Windows 2000 domains operate in one of two modes:
■ Mixed Mode. Allows domain controllers running both Windows 2000
and earlier versions of Windows NT Server to co-exist in the domain. In
mixed mode, the domain features from previous versions of Windows
NT Server are still enabled, while some Windows 2000 features are
disabled.
■ Native Mode. Requires all the domain controllers in a domain to run
Windows 2000 Server. In native mode, you can take advantages of new
features such as Universal groups, nested group membership, and inter-
domain user move.
When a domain is first installed, it is in mixed mode. The mode of operation
can be changed from mixed mode to native, but this is not reversible. In
native mode, Windows NT 4.0 Domain Controllers cannot participate in the
domain.
Q. How does one migrate from a Windows NT Windows NT® to the Windows® 2000
Server Active Directory service.
A. The Active Directory Migration Tool (ADMT) provides an easy, secure, and
fast way to migrate from Windows NT to the Windows 2000 Server Active
Directory service. You can also use ADMT to restructure your Windows
2000 Active Directory domains. This tool can help a system administrator
diagnose any possible problems before starting migration operations. The
task-based wizards will then allow you to migrate users, groups, and
computers; set correct file permissions; and migrate Microsoft Exchange
Server mailboxes. The tool's reporting feature allows you to assess the
impact of the migration, both before and after move operations. In many
cases, if there is a problem you can use the rollback feature to automatically
restore previous structures. The tool also provides support for parallel
domains, so you can maintain your existing Microsoft Windows NT 4.0
operating system domains while you deploy the Microsoft Windows 2000
operating system.
Q. Where can I find more information on Active Directory?

A. On the Microsoft Web site.
D–4 MK Installation and Upgrade Guide for Windows 2000 and Windows NT
Appendix
Installing the MK Source Code

E
Installing the Source Code ..................................................................... E–2
Contents i
Appendix
Installing the MK Source Code

E
This appendix describes how to install the MK source code in a Windows NT
environment for base and localized package VRCs. This process does not
overwrite software in customized VRCs.
Before You Begin Make sure that you have not made any source code changes in the VRCs that are
released and supported by SSA Global Technologies; these could be overwritten
by this installation.
Installing the MK Source Code E–1

Installing the Source Code
Installing the Source Code

⇒To install the source code:
1. Log on to the application server as the domain user mkadmin.
2. Insert the MK 8.4.2 source code CD. Run the setup.exe program from the
CD.
3. The MK Source Code Welcome screen opens. Click Next to continue.
4. The MK Source Install Selection dialog box opens.
Choose the MK system and click Next.

5. The Select Components dialog box opens. Select the source code components
you want to install. Click Next to continue.
6. The install copies the files. When all files are copied, the Setup Complete
dialog box opens. Click Finish to exit the install program.
7. Start MK and run the Maintain Directories of Software Components
(ttadv1115m000) session. Add source directories (program scripts and
functions) for each package VRC for which you receive source code.
8. Convert the changes to runtime data dictionary by choosing the Zoom
option from the Maintain Directories of Software Components session. This
updates the runtime data dictionary with the appropriate information.
9. Verify that the source code has been installed by exiting MK and listing the
directory contents.
10. Remove and store the media. The installation of source code is now
complete.
E–2 MK Installation and Upgrade Guide for Windows 2000 and Windows NT

Ntinstall 84 0212

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ntinstall 84 0212

Uploaded by

Copyright:

Available Formats

MK

For Windows 2000 and

Installation and Upgrade Guide

Chapter 1: Before You Begin

Chapter 2: Before Installing MK

Chapter 3: Installing MK on a Single Server

Chapter 4: Installing MK in a Dual-Server Environment

Chapter 6: After Installing MK

Appendix A: Setting Up the Radio Frequency Devices

Appendix C: Setting Tax Provider Parameters

iv MK Installation and Upgrade Guide for Windows 2000 and Windows NT

Appendix E: Installing the MK Source Code

Before You Begin

This chapter contains the following information:

Before You Begin 1–1

What you choose depends on your site’s requirements.

In a single-server configuration, the MK application server and database driver

MK Internet Client interBiz Desktop interBiz Desktop

TCP/IP Connection TCP/IP Connection

The MK dual-server configuration uses two server machines: the application

The following is the sequence of installation in a dual-server environment:

interBiz Desktop MK Internet Client

Before You Begin 1–3

The following must be running on each machine on which MK is installed:

The following are additional requirements when installing MK:

Before You Begin 1–5

interBiz Desktop Requirements

Microsoft Windows 2000 Service Pack 1 must be installed.

Windows NT 4.0 Server and Workstation

Windows XP, Windows ME, Windows 98 SE, or Windows 98

Currently there are no prerequisites for installation on Windows 98, Windows 98

Before You Begin 1–7

Service Description of the Service

Overview .................................................................................... 2–1

Before Installing MK 2–1

In addition, we recommend that you:

Adding User mkadmin to the Domain

⇒ To add users to the domain:

Installing the Relational Databases Supported by MK

Configuring Ingres II for MK

Refer to the Ingres II documentation for details on installing an Ingres II

⇒ To configure Ingres II for MK:

Before Installing MK 2–3

2. In the following dialog box:

Set the Transaction Log File Size to at least 500 MB.

6. Add user mkadmin to the database.

Check all options under the Users and Default columns.

Before Installing MK 2–5

Configuring Microsoft SQL Server 2000 for MK

⇒ To install SQL Server 2000:

Choose Local Computer and click Next.

9. The Installation Selection dialog box opens:

Choose Create a new Instance of SQL Server and click Next.

Choose Server and Client Tools. Click Next.

Before Installing MK 2–7

15. Click Next to open the Authentication Mode dialog box:

Choose Windows Authentication Mode.

Before Installing MK 2–9

Configuring SQL Server 2000 for MK

Right-click on Databases and select New Database.

3. Click the Data Files tab:

Set the initial size of the transaction log to 500 Mb.

Before Installing MK 2–11