Академический Документы
Профессиональный Документы
Культура Документы
Administrator's Guide
Worktop 2.5 for Infor ERP
LN 6.1
Copyright © 2007 Infor Global Technology Solutions GmbH and/or its affiliates and subsidiaries
All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor
Global Solutions Technology GmbH and/or its affiliates and subsidiaries. All rights reserved. All other trademarks
listed herein are the property of their respective owners.
Important Notices
The material contained in this publication (including any supplementary information) constitutes and contains
confidential and proprietary information of Infor Global Solutions.
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 Infor Global Solutions 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 Infor Global Solutions 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 Infor Global Solutions has taken due care to ensure that the material included in this publication is accurate
and complete, Infor Global Solutions 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, Infor Global Solutions
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
Infor, Infor Global Technologies are trademarks or registered trademarks of Infor Global Technologies, Inc. in the
United States and/or other countries.
Baan is a registered trademark of Infor Global Technologies, 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.
Publication Information
In your e-mail, refer to the document code and title. More specific information
will enable us to process feedback efficiently.
iv | Table of Contents
Chapter 1
Introduction 1
Worktop is the user interface for the various Infor ERP products, such as
Infor Enterprise Resource Planning and Sales Force Automation (Infor CRM).
Worktop provides an easy-to-use and intuitive view on the Infor-integrated
products that hides the complexity of the software used.
References
Document Abbreviation
Infor ERP Baan 5.0c central deployment for DEM and [CD_DEM_BW]
Baan Windows
Infor Baan ERP Windows Client Installation Guide [WCIG]
Worktop 2.5 Administration Guide [WT_ADM]
Worktop 2.5 Configuration Guide [WT_CFG]
Chapter 2
Central deployment 2
Introduction
There are different ways to setup centrally deployed access to the backend
system:
Webtop
The preferred solution for central deployment and remote access is
Webtop. Webtop is the User Interface going forward, and offers the
smallest network load.
Worktop centrally deployed
Since Webtop does not support all application sessions (on older Baan
versions), Worktop centrally deployed can be an alternative for Webtop.
How to setup Worktop central deployment is described in this chapter.
Note: Be aware that Worktop causes a higher network load than Webtop.
For best results, read these two sections carefully to work with central
deployment in Worktop.
The menu options that are available for a user in Worktop depend on
whether the Worktop server or the Worktop client runs. The Worktop server
has additional, so-called administrative options.
However, these options only apply to administrators who are also owners of
the Worktop document. Therefore, in Worktop, the following two types of
authorization are actually available:
Administrator:
A user has Worktop installed locally. Note that all users logged in onto a
machine with Worktop installed are, therefore, administrators.
Owners:
Owners of a Worktop document are administrators logged in to the
machine where the Worktop document was created originally. Therefore,
if an administrator runs Worktop and subsequently opens a Worktop
document created on a different Worktop server, this administrator is not
an owner of the document.
Initially, your Worktop document will not have the central deployment option
enabled. In this case, the Send Shortcut(s) menu option is unavailable,
because this option is only applicable in a central deployment environment.
To enable central deployment for this document, and note that you must
repeat this procedure for any document you want to enable, select the
Enable or Disable Central Deployment option.
To enable central deployment for this document, simply click Enable. After
several seconds, Worktop finishes. Worktop shares your Worktop and BW
directory, prepares your BW environment, and prepares your Worktop
document for Central Deployment. During this process, error messages can
appear. In this case, Worktop notifies you that the enabling failed and refers
to the log file. The log file is called wtError.log and is located in the \log
subdirectory of the Worktop directory.
In addition, some warning messages can appear. The following two issues
can cause these types of warnings:
notifies you about this fact if you enable a Worktop document using an
Infor ERP Baan IV environment. To use central deployment on
Infor ERP Baan IV, you must install the BW client on all clients. The
version of this BW client must be of the exact same version used by the
Worktop server. Note that Worktop only provides a warning, and
continues with the enabling. As long as the BW client of the same version
is installed on the clients, central deployment will function fully.
Worktop document not yet saved:
To enable Central Deployment, the document must be saved first. If the
document was not saved previously, Worktop warns you that you must
first save the document and automatically open the Save As dialog box. If
the document was saved previously, Worktop automatically saves the
document before you enable the document.
After you enable central deployment for this document, you might want to
change policies with respect to password saving and configuring BWC files.
Information on how to change these policies is discussed in more detail in the
Infor ERP Baan 5.0c Central Deployment for DEM and Baan Windows and
Infor ERP Baan Windows Client Installation Guide.
If you click Create Shortcut, a save dialog box appears and you can save
the shortcut to a desired location. The shortcut that will be created contains a
shortcut to the Worktop client executable on the Worktop server and opens
the Worktop document automatically when you activate the shortcut.
simultaneously that are opened in the same Worktop instance. Only one
instance of Worktop can run at a time.
To send shortcuts
In most cases, this will not be an issue because any user can modify the user
interface of Worktop in the way they choose. However, the administrator
might have new important information to share among the users. To share
this information, the administrator can send a selection of the shortcuts
present in the shortcut bar to the users.
The users receive a message that informs them that “New shortcuts have
been made available by your administrator.” The user can choose to ignore
this message, or import these shortcuts into the current document.
To send messages
You can send messages to all users currently using your Worktop server.
These users are those who are currently running the Worktop client
executable on your Worktop server. To send a message, on the Worktop
server, on the Administrator menu, click Send Message. The Send
Message dialog box appears, as shown in the following figure:
Central deployment | 2-7
Type the message you want to send into the text field and click Send to send
the message to all users. The message appears on all users’ desktops with a
maximum delay of 10 seconds. To view additional help, click the question
mark icon in the lower-left corner of the dialog box.
Configurations
Specially designed for Central Deployment, you can select or clear the
following options in the Worktop.ini file, which is located in the root directory
of the Worktop directory on the Worktop server:
In this case, you can use this option to automatically remove these
shortcuts. By default, this option is selected and, as a result, all
inaccessible shortcuts are filtered out for the user automatically.
The default values for these options are contained in the Worktop.ini file:
AutoShortcut=0
AutoMessage=1
AutoRemoveShortcuts=1
PasswordStorage=1
System requirements
Technical details
Error logging
Worktop places any error or warning messages in a file called wtError.log.
This file is located in the Application Data\Baan\Worktop\log directory of the
users profile for users and in the \log subdirectory on the Worktop server for
administrators. The log file often contains useful information to determine the
cause of the problem. Each log contains the date and time on which the error
was generated and a description of the problem. Optionally, arguments are
added that provide more-detailed information. The error codes in front of
each error are useful for support, because these error codes provide
information about where these errors were generated in the source code.
Worktop documents
Worktop 2.5 documents are separated into the following three parts:
Now, if a user opens a Worktop document for the very first time, the
corresponding .gct file is copied from the server into the users profile in the
\Application Data\Baan\Worktop\documents directory.
The next time the user opens the Worktop document, Worktop finds this .gct
file in the user’s profile and uses that file instead of the file located on the
server. The user has write access to the local .gct file, but not to the .gct and
.sct files on the server. The .sct file is not copied to the client, but is always
read from the server.
Note: Because the .gct and .sct file separate GUI settings and server
settings, you can reuse these files. For example, if you created a document
and want to create a second document using the same GUI settings, but
different server settings, you can either modify the reference in the Worktop
document to the other .gct file, or overwrite the .gct file.
2-10 | Central deployment
Transparency of documents
You can copy and open Worktop documents anywhere, although not the
templates, because Worktop contains pointers to the UNC name of the
corresponding templates. Therefore, you can, for example, create a Worktop
document on the Worktop server with the name test.wtd and copy this
document to your local machine and open the document from that location.
From the Test.wtd file that Worktop points to, Worktop reads the templates
on the Worktop server and loads these templates. You can load Central
Deployment-enabled Worktop documents from within any Worktop: either a
Worktop client or Worktop server.
To minimize the amount of data transferred over long distances, you can
install extra Worktop servers or mirrors.
Users can use this local Worktop server to launch Worktop, either
Worktop.exe or Worktop_client.exe, while still using the Worktop documents
located on the central Worktop server. For more information, refer to
“Transparency of documents.”
In this case, only the Worktop document is sent over the long distance, which
is only a small amount of kilobytes. As few as 50 KB would already be a large
document.
Global access
Worktop 2.5 supports global access; however, this only applies when
roaming Profiles are used, which is supported on Windows XP. Because
Central deployment | 2-11
Worktop writes the personalized documents into the user’s profile, global
access is supported when Worktop is roaming.
To run a Worktop client, browse to the \bin subdirectory of the Worktop share
on the client machine. For example, if a Worktop server called cnl05259 has
shared the Worktop directory with the name Worktop, open Explorer on the
client machine and browse to \\cnl05259\Worktop\bin.
Run Worktop.exe:
In this case, no Worktop-related files will be stored on the local machine,
but these files will be loaded into memory. After you close Worktop, the
memory is released. The advantage of this method is that no Worktop
files, except for the personal documents, are stored on the client. The
disadvantage of this method is that each time you start Worktop, you must
transfer the Worktop-related files from the Worktop server into the client’s
memory, which causes significant network load.
Run Worktop_client.exe.
If a user runs Worktop_client.exe, initially only a very small executable is
transferred from the Worktop server to the client. The first time this
executable runs, this file will copy the Worktop-related files into the
%USERPROFILE%\Local Settings\Temp\ Application Data\Baan\Worktop
directory. Subsequently, Worktop_client.exe runs Worktop.exe from that
directory.
Any other time, this file checks whether files are missing and whether the
Worktop server contains a version of Worktop that differs from the client’s
version. In both cases, the client will be updated.
To enable terminal server users to use the Worktop, the administrator must
configure the Worktop in the Terminal Services configuration to start up with
the argument /ts.
3-2 | To use worktop in a terminal server environment
Several methods are available to deploy the Worktop on terminal server. The
most typical approach is to enable users to connect to terminal server with
their system account. Subsequently, a user can open a Worktop document
that is created by an administrator and connect to the Baan backend with
their personal Baan account. Specific changes made to the document, such
as GUI modifications, are stored in the terminal server user profile.
A second approach is for all users to connect to terminal server with their
system account and connect to the Baan backend with a common account.
This can be useful if all users rely on one specific DEM business process.
To use worktop in a terminal server environment | 3-3
Note that some restrictive issues, such as the following, apply to the use of
terminal server:
http://<workflow-server>:<port>/wfupdate/DownloadJarServlet?method=getjar
A file save dialog will appear so you can provide a location to save the workflow
integration component.
Note: The user needs to restart Worktop to free the java virtual machine and
to load a new classpath with another version of the workflow integration
component.
5-2 | Worktop runtime files and folders
Chapter 5
Worktop runtime files and folders 5
The worktop uses a number of files and folders in which runtime data is
saved during Worktop execution, such as the following:
This difference implies that when different Windows users use the same
system, on Windows XP these users can share each others Worktop
documents. However, on Windows Vista the Worktop documents cannot be
shared by different Windows users.
Appendix A
Administration FAQ A
Q: Can I use the same .bwc file from multiple Worktop documents
simultaneously by using several Baan logins?
A.: No. If you use the same BWC file from two Worktop documents and you
open both documents, no login or password is requested when you open the
second document. Worktop assumes that you want to use the same Baan
login as for the first document. No workaround is currently available to
address this known issue. This problem is a Baan Automation, or, more
precisely, a COM restriction.
A: The wfupdate web application comes with the Infor Workflow extension.
The wfupdate application can be deployed along side the Workflow server.
The wfupdate web application provides download access to the correct
Workflow integration component. With Worktop two versions of the Workflow
integration component are shipped. However when these are not correct
Worktop will automatically try to download the correct version from the
wfupdate web application
Appendix B
To create application shortcuts B
In this case, you will encounter two problems. The first problem is that the
executable that you created the shortcut to is probably not shared, nor do
you want to share this executable. You do not want to share any application
to which you created a shortcut. The second problem is that, even if you did
share an executable, most applications do not support central deployment,
therefore, the application will not run that way anyway. For example, if you
create a shortcut to the Microsoft Word application, word.exe, you must share
the directory where the word.exe file is located, but the share still will not
work because Microsoft Word does not support central deployment.
1 In the Run Application field, type the name of the application you want to
start and precede it with a “#”. Don not specify a path. To create a shortcut to
notepad, type “#notepad”.
2 Press Create Shortcut behind the field to create a shortcut.
3 Now the shortcuts can be distributed with the “Send Shortcut(s)…” menu
option.
B-2 | To create application shortcuts
In the following picture the Run Application field and the Create Shortcut
button are highlighted.
To create application shortcuts | B-3