Producer 9.3 Installation Guide en-US

7/23/2019 Producer 9.3 Installation Guide en-US

http://slidepdf.com/reader/full/producer-93-installation-guide-en-us 1/37

Installation Guide

Workforce Performance Builder

Document Version: 1.0 – 2014-10-15

CUSTOMER

SAP Workforce Performance Builder 9.3

Producer



2

Customer

© 2014 SAP AG. All rights reserved.


Typographic Conventions

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, table names, and key concepts of a programming language when theyare surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,

names of variables and parameters, source text, and names of installation, upgrade and

database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they

appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters

with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .




Table of Contents

Customer

© 2014 SAP AG. All rights reserved. 3

Table of Contents

1 Introduction .................................................................................................................................................... 5

1.1 About this document ................................................................ ............................................................... ......... 5

1.1.1 Purpose ......................................................................................... .................................................... 5

1.1.2 Constraints.................................................................................... .................................................... 5

1.1.3 List of Documents ................................................................ ............................................................ . 5

1.2 General Information........................................................ ............................................................. ..................... 6

1.2.1 Identification ........................................ ............................................................. ................................ 6

1.2.2 System requirements ..... ............................................................ ...................................................... 8

1.2.3

Upgrades ......................................................... ............................................................. ..................... 9 1.2.4 Technical Support ................................................................ ............................................................ . 9

1.3 New Features ......................................................... ............................................................ ............................. 10

1.4 Before you start .............................................................. ............................................................. ................... 10

1.4.1 SAP Notes for the installation ....................................................... .................................................. 10

2 Preparation.....................................................................................................................................................11

3 Installation .................................................................................................................................................... 12

3.1 Files .............................................................. ............................................................. ...................................... 12

3.2 Filetypes ................................................................ ............................................................. ............................. 12

3.3 Shortcuts ............................................................... ............................................................ ............................. 13

3.4

Pre-parameterization of the installer ........................................................... .................................................. 13

3.4.1 Use .................................................................................................................................................. 13

3.4.2 Prerequisites ............................................................... ............................................................. ....... 13

3.4.3 Procedure................................................................................................ ........................................ 13

3.5 Prerequisites.................................................................................................................................................. 20

3.6 Procedure ...................................................................................................................................................... 20

3.6.1 Installing the Producer ......................................................... .......................................................... 20

3.6.2 Notes on updating the Producer............................................................... ..................................... 20

3.6.3 Creating a Workarea ............................................................ ........................................................... 21

3.6.4 Integrating resources............................................................................................................ .......... 22

3.6.5 Migrating a Workarea................................................................................................. ..................... 22

3.6.6

Settings for recording and playback....................................................... ........................................ 31

4 Post-Installation .......................................................................................................................................... 32

4.1 Database ................................................................................................................. ........................................ 32

4.2 Files .............................................................. ............................................................. ...................................... 32

4.3 Registry ....................................................................................................... .................................................... 32

5 Additional Information ............................................................................................................................... 34

5.1 Settings for Recording and Playback ................................................ .............................................................34

5.2 Uninstalling Producer .......................................... ............................................................. ..............................34

5.3 Working with the Producer under Citrix ................................................................................................ .........34

5.3.1 Installation on the Citrix terminal server .................................... .................................................... 35

5.3.2

Seamless Load-Balancing Citrix ................................................... .................................................. 35



4

Customer



Table of Contents

5.3.3 Setting up an author environment................................................................................................ .. 36




Introduction

Customer


1 Introduction

This installation guide will provide you administrative support in using the SAP Workforce Performance Builder

Producer as well as the applications required for creating and playing learning content. Various prerequisites need

to be complied with when installing the Producer and when recording and playing lessons and specific settings

applied.

Once the installation has been completed and the appropriate settings applied, work can begin immediately on

producing learning content in the Producer.

Should you require help with the installation or the applicable settings, please contact SAP support, which is

available to assist you with any questions. You will find the necessary information and contact data in the

"Technical support" section of this manual.

1.1 About this document

1.1.1 Purpose

This document is intend to guide you through all installation and configuration processes which are necessary to

successfully run your component of the SAP Workforce Performance Builder for first time.

1.1.2 Constraints

This document is not intended to give you information about user processes or configuration methods within the

installed Producer.

Go the chapter List of Documents to find more related documentation.

1.1.3 List of Documents

The following table lists all documents mentioned in this Guide:

Title Where to find

Installation Guide Producer http://help.sap.com/Download/wpb/93/Producer_9

.3_Installation_Guide_en-US.pdf

Manual Producer http://help.sap.com/Download/wpb/93/Producer_9

.3_Manual_en-US.pdf

http://help.sap.com/Download/wpb/93/Producer_9.3_Installation_Guide_en-US.pdf



http://help.sap.com/Download/wpb/93/Producer_9.3_Manual_en-US.pdf









6

Customer



Introduction

Title Where to find

Security Guide Producer http://service.sap.com/~sapidb/011000358700000

254902014E/sec_wpb_producer_93_en.pdf

Installation Guide Instant Producer http://help.sap.com/Download/wpb/93/Instant_Pro

ducer_9.3_Installation_Guide_en-US.pdf

Manual Instant Producer http://help.sap.com/Download/wpb/93/Instant_Pro

ducer_9.3_Manual_en-US.pdf

Installation Guide Manager http://service.sap.com/~sapidb/011000358700000

254902014E/inst_wpb_manager_93_en.pdf

Operations Guide Manager http://service.sap.com/~sapidb/011000358700000

254902014E/op_wpb_manager_93_en.pdf

Manual Manager http://help.sap.com/Download/wpb/93/Manager_9.3_Manual_en-US.pdf

Security Guide Manager http://service.sap.com/~sapidb/011000358700000

254902014E/sec_wpb_manager_93_en.pdf

Installation Guide Navigator http://help.sap.com/Download/wpb/93/Navigator_

9.3_Installation_Guide_en-US.pdf

System Requirements http://help.sap.com/Download/wpb/93/SAP_Workf

orce_Performance_Builder_9.3_SystemRequirements

_en-US.pdf

1.2 General Information

1.2.1 Identification

Property Value

Software Name SAP Workforce Performance Builder

Software Version 9.3

Component Name Producer

Component Version 9.3.2.288

Software Language

<LCID decimal: Identifier>

1. 1033: English

2. 1031: German

3. 1034: Spanish

4. 1036: French

5. 1037: Hebrew

http://service.sap.com/~sapidb/011000358700000254902014E/sec_wpb_producer_93_en.pdf



http://help.sap.com/Download/wpb/93/Instant_Producer_9.3_Installation_Guide_en-US.pdf



http://help.sap.com/Download/wpb/93/Instant_Producer_9.3_Manual_en-US.pdf



http://service.sap.com/~sapidb/011000358700000254902014E/inst_wpb_manager_93_en.pdf



http://service.sap.com/~sapidb/011000358700000254902014E/op_wpb_manager_93_en.pdf



http://help.sap.com/Download/wpb/93/Manager_9.3_Manual_en-US.pdf



http://service.sap.com/~sapidb/011000358700000254902014E/sec_wpb_manager_93_en.pdf



http://help.sap.com/Download/wpb/93/Navigator_9.3_Installation_Guide_en-US.pdf



http://help.sap.com/Download/wpb/93/SAP_Workforce_Performance_Builder_9.3_SystemRequirements_en-US.pdf


























Introduction

Customer


Property Value

6. 1043: Dutch

7.

1046: Portuguese (Brazil)8. 1041: Japanese

9. 1042: Korean

10. 1049: Russian

11. 2052: Chinese (Simplified)

12. 1028: Chinese (Traditional)

13. 1029: Czech

14. 1030: Danish

15. 1035: Finnish

16. 1038: Hungarian

17. 1040: Italian

18. 1045: Polish

19. 1054: Thai

20. 1055: Turkish

21. 1057: Indonesian

22. 1066: Vietnamese

23. 1081: Hindi

24. 1086: Malay

25. 1026: Arabic (Saudi Arabia)

26.

2052: Serbian

Software Manufacturer SAP

Installer Size (MB) ~ 42 MB

Operating System Microsoft Windows Vista

Microsoft Windows 7

Microsoft Windows 8 (without tile mode)

Included in

software packages

SAP Workforce Performance Builder Enterprise

Edition

SAP Workforce Performance Builder Producer

Description The Producer provides the authoring environment

which enables content developers to create, edit,

localize, update and deploy high quality simulations,

documentation, soft skill trainings, and navigations for

their end users.



8

Customer



Introduction

1.2.2 System requirements

Type Specifications

Operating system 32 & 64 bit version of

Windows Vista

Windows 7

Windows 8 (without tile mode)

Processor Pentium IV, at least 1 GHz

Memory A minimum of 1 GB

Hard drive 200 MB of free space

Browser Internet Explorer 7.0 – 11.0

Soundcard Any soundcard

For production of audio lessons and book pages

Microphone Any microphone

For recording of audio

Scenario Requirement

SAP Business Suite SAP GUI Scripting activated

(serversided and role-specific)

Java Applications Java Access Bridge installed

Windows Vista Windows Automation API

Documentation Generation MS Office (Word and PowerPoint) 2003 - 2013

PDF Generation MS Office 2007 and Plug-In Microsoft Save as PDF

MS Office 2010 / MS Office 2013

Aris Import Symbio 4.2

(license required)

ViFlow ViFlow 5.0

HPQC HPQC 11




Introduction

Customer


1.2.3 Upgrades

Does the package upgrade existing package(s):

Package Version Upgrade actions

SAP Workforce Performance Builder 9.3 Resource structure (workarea)

Read according chapter Migration of a Workarea.

1.2.4 Technical Support

Please use the SAP Incident Wizard on the SAP Service Marketplace to submit your incidents on the following

components:

KM-WPB // Workforce Performance Builder

KM-WPB-PRO // Workforce Performance Builder – Producer

KM-WPB-IPR // Workforce Performance Builder – Instant Producer

KM-WPB-MGR // Workforce Performance Builder - Manager

KM-WPB-NAV // Workforce Performance Builder - Navigator

KM-WPB-CXH // Workforce Performance Builder - Context Sensitive Help

KM-WPB-APR // Workforce Performance Builder - Application Profiles

KM-WPB-SMI // Workforce Performance Builder - Solution Manager Integration

If you are not familiar with the SAP Service Marketplace, read the following information:

To access the SAP Support Portal you need an S-user ID and password. You can request access data from

your SAP Super Administrator or register online on the SAP Service Marketplace page under

‘Registration‘.

With this user, you have read-access to all the contents of the SAP Support Portal, you can use the SAP

Community Network and SAP Help Portal, and you can also book courses under SAP Education.

If you want to work with the support applications (Incident Wizard, license key request, system data

maintenance, manage remote connections, software download and so on), you need the corresponding

authorizations, which your SAP Super Administrator can give you.

You can find information for new users and about support applications on the Support Portal Homepage

under ‘Learn More‘. There you can also register for a personal overview demonstration of the SAP Support

Portal.

In case of problems with SAP Service Marketplace contact you local Customer Interaction Center.

An online webform is available on http://support.sap.com/contactus. This webform should be used for allwritten communication with your local customer interaction center. More Details about Incident

Processing, Support Addresses and Hotline Numbers can be found here:

http://service.sap.com/sap/support/notes/560499

Are you interested in a tour through the SAP Support Portal? Register for an online demo.

Note

The Producer diagnosis function can also be used to check the technical data of the installation on your

computer (version, operating system, browser, etc.). Open Producer and select Diagnosis… over the Help

menu. The Producer transmits the required information automatically and lists this in a corresponding

dialog box. This information can also be saved as a text file and sent as an E-mail attachment to the SAP

support staff.

http://support.sap.com/contactus





http://ctx.cfg_show%28%27https//service.sap.com/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=501100035870000019462&_HIER_KEY=601100035870000239025&_HIER_KEY=701100035871000579073&_SCENARIO=01100035870000000202&#HOME








10

Customer



Introduction

1.3 New Features

Please read the What's New document according to your version to find out newly implemented functions as wellas enhanced features in your component of the SAP Workforce Performance Builder.

The What's New documents are to be find in the SAP Service Marketplace.

1.4 Before you start

1.4.1 SAP Notes for the installation

You must read the following SAP Notes before you start the installation. These SAP Notes contain the most

recent information on the installation, as well as corrections to the installation documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find in the SAP Service

Marketplace at the Internet address:

http://service.sap.com/notes.

Use the following component identifiers to filter SAP Notes Search by filter Application Area:

KM-WPB // Workforce Performance Builder

KM-WPB-PRO // Workforce Performance Builder – Producer

KM-WPB-IPR // Workforce Performance Builder – Instant Producer

KM-WPB-MGR // Workforce Performance Builder - Manager

KM-WPB-NAV // Workforce Performance Builder - Navigator

KM-WPB-SMI // WPB Interface to Solution Manager

http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000747725&_SCENARIO=01100035870000000202



http://service.sap.com/notes







Preparation

Customer


2 Preparation

Recommendation

Check the chapter Additional information to avoid installation conflicts which might come up in a special

scenario.



12

Customer



Installation

3 Installation

3.1 Files

Location Path

Default application location %ProgramFiles%\SAP Workforce Performance

Builder\Producer 9.3

Default workarea location %USERPROFILE%\Producer Workareas

3.2 Filetypes

The installation and the use of the Producer results in registration/existence of new file formats.

File suffix Symbol Identification

*.dkp Archive to exchange contents and

resources between:

Producer Instant Producer

Instant Recorder

*.exe Self-starting deployment output

containing contents and resources

needed for playback.

*.slc Deployment output for SAP

Learning Center containing

contents and resources needed for

playback.

*.deploy Deployment control file containing

list of assets to be used for

deployment.

*.meta Control file for communication with

Central Workarea/Manager

containing information about

object state and ownership of write

token.




Installation

Customer


3.3 Shortcuts

Application Shortcut

Producer

3.4 Pre-parameterization of the installer

3.4.1 Use

Pre-parameterization of the Installer file will enable you to roll-out Producer in one or more central remote

installation scenarios whereas you can predefine or restrict Producers behavior on workarea creation as well as

on resource handling. Furthermore you can provide connection data to an already existing instance of the SAP

Workforce Performance Builder Manager without the need to send it separately.

3.4.2

Prerequisites

To pre-parameterize the installation process of the Producer you will need the following prerequisites:

1. Producer installation file, e.g. SAP-Workforce-Performance-Builder-Producer-<version>-<init. language>.msi.

2. Windows command line. Open the Run dialog (Windows key + R), type in CMD and press Enter.

3. In some cases a Text editor application like the Windows build-in "Notepad".

3.4.3 Procedure

The following cases show up scenarios to pre -parameterize the installation process of the Producer. You may

combine given commands but note that some combinations will have side effects.

To combine commands just add commands divided with a space character like in following syntax example.

Syntax

msiexec /i <path of msi file> INITWA=... ADDITIONAL_INITWA=...



14

Customer



Installation

Recommendation

Using a path which contains spaces you will have to declare the path in command line by enclosing it with

quotation marks ("...").

Side effects of parameter combinations

1. Combination of wa_path_fixed with default_wa_path and/or initial_create_wa

1. wa_path_fixed will be taken, other parameters will be ignored

2. Combination of default_wa_path and initial_create_wa

1. initial_create_wa will be taken

2. if initial_create_wa is not accessible, default_wa_path will be taken

3.4.3.1 Set default suggested workarea path

Target

Individualize workarea path suggested to the user on first run of Producer.

Use

Provide a suggestion to save the workarea at another path than default, e.g. to enable users to save their contents

at a special storage indexed for backup policies. Users still are able to specify an individual path to store the

workarea.

Procedure

1. Open command line.

2. Type in the following command. Replace the msiexec /i Using a path which contains spaces you will have to

declare the path in command line by enclosing it with quotation marks ("..."). INITWA=...

ADDITIONAL_INITWA=... with your individual values.

Syntax

msiexec /i <path of msi file> DEFAULT_WA_PATH=<default path>

3. Finish installation

Result

On first run the Producer opens the select/create workarea dialog suggesting the individualized path by default.

Registry

Registry node Registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Nod

e\SAP WPB\Producer93

DefaultWAPath




Installation

Customer


3.4.3.2 Set default workarea path without possibility to change

TargetSpecify workarea path to be initially created and deny the individual creation of workarea at another path.

Use

Force users to use a specific storage path only and disallow the creation of other workareas not fulfilling the

storage criteria. This might be useful in case of using Citrix environments with auto rollback function or for testing

purpose.

Procedure


2. Type in the following command. Replace the msiexec /i <path of msi file> DEFAULT_WA_PATH=<default

path> with your individual values.

Syntax

msiexec /i <path of msi file> WA_PATH_FIXED=<fixed WA>


Result

On first run the Producer doesn't show the select/create workarea dialog but automatically creates the workarea

at the given path. The menu item to change/create workarea will be disabled.

Registry




WAPathFixed

3.4.3.3 Create initial workarea automatically

Target

Create initial workarea directly at specified path without displaying the select/create workarea dialog.

Use

Auto create a workarea at a special system path without needing the user to know where to store.

Procedure


2. Type in the following command. Replace the <placeholders> with your individual values.



16

Customer



Installation

Syntax

msiexec /i <path of msi file> INITIAL_CREATE_WA=<INITCREATEWA>

3.

Finish installation

Result

No select/create workarea dialog will be shown on first run of the Producer but the initial workarea will be created

automatically within the path specified.

Registry




InitialCreateWA

3.4.3.4 Individualize resource source location

Target

Individualize the path the Producer takes its resources from on initial workarea creation or edit configuration.

Use

Provide a set of initial resources independently from changes to initial resources which might come up with

Producer updates. This will enable you to manage and roll-out initial resources globally.

Procedure

1. Go to the installation directory of an already existing Producer installation (Default: C:\Program Files

(x86)\SAP Workforce Performance Builder\Producer92).

2. Copy the content of the INITWA folder (..\initwa).

3. Create individual folder, e.g. "myinitwa", and paste the files from INITWA folder.



Syntax

msiexec /i <path of msi file> INITWA=<INITWA>


Result

On workarea creation or edit configuration the Producer will import its resources from individualized INITWA

folder.




Installation

Customer


Registry




InitialWA

3.4.3.5 Specify additional resource source location

Target

Add an additional source path the Producer takes its resources from on initial workarea creation or edit

configuration.

Use

Provide a set of custom resources to be included or restored on workarea creation or configuration.

Procedure

1. Create individual folder and insert different resources as in INITWA folder.


3. Type in the following command. Replace the msiexec /i <path of msi file> INITWA=<INITWA> with your

individual values.

Syntax

msiexec /i <path of msi file> ADDITIONAL_INITWA=<ADDTIONALINITWA>


Result

On workarea creation or edit configuration the Producer will import its resources from individualized additional

INITWA folder as well.

Registry




AdditionalInitWA



18

Customer



Installation

3.4.3.6 Specify path for automatical resource updates

TargetSpecify resource path to automatically update resources if more recent versions are available.

Use

Force the user to use a custom set of resources and its most recent versions at any time.

Procedure

1. Create individual folder and insert more recent resources as in Producers INITWA folder.

2. Open a text editor and create file update.xml like the following. Add one <Resource> line for each resource to

be taken.

Syntax

<?xml version="1.0" encoding="utf-8"?>

<root>

<Application name="producer">

<AppVersion Minimum="9.2" Maximum="999" IncludeMinimum="true"

IncludeMaximum="true"/>

<Resource mandatory="true" method="auto" title="my

settings">C:\autoupdateWPB\mysettings.dkp</Resource>

</Application>

</root>

3. Save the xml file to the folder to be used as source for auto update.



Syntax

msiexec /i <path of msi file> AUTOUPDATE_PATH=<AUTOUPDATEFOLDER>


Result

The Producer will import the resources from individual specified folder on Producer startup, on workarea creation

or when update-time-interval is expired. The updates path is shown within the P roducer settings.

Note

o If AUTOUPDATE_PATH is enabled, manual changes to according parameters in settings dialog are

disallowed.

o Resources imported by auto update function cannot be deleted manually.

o If a resource specified in the xml file is not available within specified folder the Producer will display an

error message on startup.




Installation

Customer


Registry




AutoUpdatePath

3.4.3.7 Predefine Manager connection

Target

Provide values for a connection to the Manager to prefill connection dialog.

Use

Enable users to easily connect with an existing Manager instance.

Procedure

1. Download connection file from Manager (click on Connect Instant Producer).



Syntax

msiexec /i <path of msi file> MANAGER_CONNECTION=<path to connection file>


Result

On opening “Connect with Manager...” dialog the dialog fields are filled out with the connection values from the

connection file. The user just has to enter password.

On startup of Producer it will be checked if an URL mismatch between user/administrator setting exists and, if so,

a message box will prompt for confirmation to keep user settings or re-apply administrative settings.

Recommendation

You may want to provide connection path only without individual username. In this case open the

connection file with a text editor and empty or anonymize (e.g. "<enter your username here>") the

parameter Authentication user.

In this case no message will appear to user, since the URL settings check will fail in any case.

Registry




ManagerConnection



20

Customer



Installation

3.5 Prerequisites

You will need the ability to run the installer with administrator permissions for the PC on which the Producer is tobe installed.

Note

To install on a Citrix terminal server please refer to the chapter on working under Citrix.

3.6 Procedure

3.6.1 Installing the Producer

To install Producer, perform the following steps:

1. Start the installation program by double-clicking on the installation file program icon.

2. The installation program will guide you through all the steps for installing the Producer. Now follow the

instructions in the displayed dialog.

1. A welcome dialog with the Producer version will be displayed. Click on the Next button.

2. Select the installation folder. This will be proposed to you by the Producer in C:/Program Files/SAP

Workforce Performance Builder.

The Browse... button allows you to change the installation location. A dialog will open allowing you toselect a different folder.

3. Initiate the installation process by clicking on the Install button. The installation will now be executed.

3. Once the Producer has been installed, you can close the installation program by clicking on the Finish button.

If the launch Producer setting is activated, the Producer will be opened when the dialog is closed.

In general use, you can launch the Producer by double-clicking on the Producer icon on the desktop or via the

start menu, from Programs -> SAP Workforce Performance Builder.

3.6.2 Notes on updating the Producer

In case you update an already existing installation of the Producer note the following information.

3.6.2.1 Update Producer using a service release version (SP)

If you want to update an already existing Producer installation to a newer service release (SP) without a change of

the major version the installation program will recognize the existing installation and automatically overwrite

existing program components within the installation process.

Opening an already existing workarea as created with formerly installed version the migration assistant will




Installation

Customer


appear, offering you to update your workarea resources to most recent resource version. Proceed as described in

chapter Migrating a workarea.

3.6.2.2 Update Producer to next major version

If you want to install a new major version (e.g Producer 9.2) note that any already installed previous major version

(e.g. Producer 9.1) won't be uninstalled automatically. Both versions can be installed side by side in your system.

This enables you to work on different workareas having different version requirements.

However, consider to use only one Producer version on each workarea you have. Don't open workareas which

have been created or migrated by your most recent Producer version with any older Producer version or vice

versa when the workarea has to stay editable for other authors using the same older Producer version.

In case the older Producer version is not required anymore you have to uninstall it manually. Read chapter

Uninstalling Producer in Additional information on how to do so. Consider to select the correct Producer version inthe application list since at least two entries will be available.

3.6.2.3 Update Producer using a custom program path

In case you installed your previous Producer version to a custom path like D:\programs\wpb and you want to

install your new major Producer version by using the same custom path you should uninstall the previous

Producer version before to avoid unnecessary entries in your systems program list. After uninstallation of the

previous version you may use your custom installation path again.

3.6.3 Creating a Workarea

If you would like to create a new Workarea, then select the Select Workarea... function in the Workarea menu.

1. A Workarea selection dialog is opened after startup, offering a preset path for filing the folder.

This path is under:

%USERPROFILE%/Producer Workareas/ Workarea

Changing the name

If you would like to change the name of the Workarea, you can do so using the path data in the Target

directory. Replace the prescribed name with the new name.

Changing the base directory

1. To set a different directory as the base directory, click on the Select button.

2. Designate the folder in the directory structure in which the Workarea is to be set up and click on Create

new folder. Give this a name of your choosing.

3. Then click on OK to confirm the dialog. The path for the Workarea folder is now displayed in the dialog.

2. You will see the standard installation resources displayed in the window under the Target directory. You can

use this selection to define the resources to be used.

3. Click on Create to set up the Workarea. The required files are now copied into the target directory.



22

Customer



Installation

Once all the files have been copied into the corresponding working directory, you can confirm the conclusion of

the creation process by clicking on OK. The resources and Content group are now created within the tree

structure.

Note

The standard installation resources are set up when a Workarea is created. You can then insert individual

resources, such as customized styles or application profiles, in your Workarea via Import Archive…

3.6.4 Integrating resources

Individual Workarea resources can be integrated in the Producer. For example, these can be:

Individual application profiles Customized styles (library, trainer, bubble type etc.)

Customized document templates

Text files for the project languages

Importing resources

The resources are imported as archive files in DKP format ( *.dkp).

1. To do so, navigate in the Project Explorer to Import archive... in the Workarea -> Management menu.

2. Select the archive file you want. You may select one or a number of files.

3. A dialog will then open at the same time as you are shown the contents of the archive file. Now select whether

to import the entire archive or only part of it. Confirm your selection by clicking on OK.

Your resources will now be imported into, and be available in, the Workarea.

A number of resources need to be activated for use as the default. Select the appropriate resource in the

Producer's resource tree and click on Set as default in the object editor.

You will find additional information about the resources in the Producer's F1 Help.

Managing Resources in the Central Workarea

In order to make certain resources available to all of a Central Workarea's users, save these resources from your

Producer into the Central Workarea.

To do so, select the resource and click on Store on the server.. in the Central Workarea menu.

An author can store this resource in his local Workarea using the Fetch objects... function in the Central Workarea function.

3.6.5 Migrating a Workarea

Migrating a workarea allows you to update the workarea resources to a newer Producer version. The migration is

necessary, as a newer version of the Producer includes changes in the resources and the resource structure.

During the migration the resources will be changed to the new requirements and your own resources will be

converted. The migration does not change the content of the workarea.

The migration of a workarea has to be done for:




Installation

Customer


a new release (Major Release)

a service pack

The migration of a workarea depends on your SAP Workforce Performance Builder Edition and includes the

following steps:

Desktop Edition - local workareas

1. Backup of the workarea

2. Preparation of the migration

3. Installation of the new Producer version

4. Migration of the workarea

Enterprise Edition - central and local workareas

1. Backup of the database and corresponding files

2. Backup of the local workareas

3.

Preparation of the migration

4. Checkout of write permissions for the resources by the master author

5. Installation of the new Producer version

6. Upgrade to the new Manager version

7. Creation of a new Manager password (only Migration from 9.1)

8. Migration of the central workarea by the master author

9. Migration of the local workareas by the standard authors

Note

The migration is only possible for workareas from the Producer version 9.1. Older workareas have to be

updated at first in a Producer 9.1 and afterwards to be migrated into the current Producer version.

Note

After the migration it is not possible to use the workarea in an older Producer version.

Migration of user-defined resources

A workarea can include user-defined resources for the creation of individual learning content. Typical user-defined

resources are bubble styles, settings or templates.

During the migration, user-defined modifications and settings will be kept and converted into the new resource

structure. The adaptations won’t be deleted.

In a workarea with an up-to-date resource structure imported resources have to be migrated individually.For further information on changes in the resources, refer to the chapter 'Differences in Resource Structure'.

Migration of an Instant Producer workarea

The workarea migration of an Instant Producer 9.2 for the Enterprise Edition is executed automatically after the

first start of the program.

The workarea migration of an Instant Producer 9.2 for the Desktop Edition can be done after the migration of the

resources in the central workarea (see chapter Central Workarea - Enterprise Edition). The synchronization is

executed automatically after the first start of the program.



24

Customer



Installation

3.6.5.1 Local Workarea - Desktop Edition

The migration of a workarea for the Desktop Edition allows you to update a local workarea of your Producer.

Preparation for the migration

Before migrating a workarea the following preparations and requirements are necessary:

Backup workareas

Before migrating a workarea make an archive, which you can revert to in the event of any problems. This can

be done with the Export Archive... function in the menu Workarea -> Administration.

Update workareas to version 9.1



Take a note of trainer Configurations (only Migration from 9.1)

The settings of the trainer Configuration (old trainer) won't be converted. Before migrating the workarea take

a note of your configurations.

After the migration adapt the Playback Settings with your configurations.

Migration of the workarea

The migration of a workarea can be executed as follows:

1. Install the new Producer version.

2. Open the Producer.

3. Open the workarea by clicking on Workarea -> Select Workarea...

4. A dialog opens automatically. Click on Migrate Workarea.

5.

Afterwards the workarea migration dialog box opens. The dialog box shows the recommended migration

action for each available resource group.

Adapt the resource actions using the dropdown box.

It is recommended that you keep the settings. Adaptations are only necessary in a few situations, if no

changes should be made.

For further information on the settings see the chapter 'Migration Dialog Box'.

6. Click OK to start the migration.

The migration will now be executed.

7. Click OK in the progress dialog, if the migration is completed.

8. With the finishing of the migration a folder with log files opens.

The folder contains archives with the changed and removed resources, as well as log information. The folder

is located in the workarea folder.

9. Click Restart in the dialog box. Restarting the Producer is necessary so that the new resources and

configurations can take effect.

Note

Do not import the outdated resources of the log folder into your workarea again.




Installation

Customer


3.6.5.2 Central Workarea - Enterprise Edition

When updating the workarea in an authoring environment with a central workarea and a number of localworkareas, it is necessary that the master author performs the update in one local workarea and afterwards

deploys it to the other local workareas. This achieves a consistent use of the needed resources.

Preparation for the migration

Before migrating a central workarea the following preparations and requirements are necessary:

Caution

Make sure, that the preparations and requirements are fulfilled before you perform the migration. This is

necessary to avoid errors during the migration process as well as in the migrated workarea.

Note

Consider the SAP Note 1863148 about the clean up of deleted files in a database.

Backup central and local workareas

Before migrating a workarea make an archive, which you can revert to in the event of any problems. This

should be done for the central workarea on the Manager as well as for the local workareas of the authors.

Update workareas to version 9.1



The migration of a central workarea is only possible from the Manager version 9.2 or higher. Consider the

following:

o Upgrade Manager

Upgrade your Manager 9.1 to the version 9.2 or 9.x. The Manager can handle the new resources and

resource structure.

o Create new passwords

With the Manager 9.2 the password encryption is optimized and old passwords are expired.

Create a new password for your login in Manager. This is necessary for all master and standard authors.

The creation of a new password is only necessary for non LDAP-based users.

Further information about the upgrade of a Manager is available in the Operations Guide.

Save write permissions centrally

Save all write permissions of the resources to the server. The write permissions are necessary for the masterauthor to migrate the resources. This can be done by selecting a resource and clicking Finish editing.

Take a note of trainer Configurations (only Migration from 9.1)

The settings of the trainer Configuration (old trainer) won't be converted. Before migrating the workarea take

a note of your configurations.

After the migration adapt the Playback Settings with your configurations.

Migration steps for the master author

The migration can be executed by the master author as follows:

Steps in old Producer and Manager version

1. Open the workarea in the old Producer version.



26

Customer



Installation


If the authentication dialog appears, insert your user data with the new password.

3. Start editing resources to get all write permissions. Select the Resources tree and click on Central Workarea -

> Start editing all objects...

4. Close the Producer.

5. Click Shut down in the opened dialog. Do not return the write permissions.

6. In Manager delete all resources from the trash do avoid the restore of the objects.

Steps in new Producer and Manager version

1. Upgrade the Manger to the new version.




5.

The authentication dialog appears. Insert your user data with the new password.

Note

Log on with the user data as used for the checkout of the write permissions to avoid permission errors.

Through the switch of the Producer versions the authentication dialog may appear twice. Insert your user

data again.

6. A dialog opens automatically. Click on Migrate Workarea.

7. Afterwards the workarea migration dialog box opens. The dialog box shows the recommended migration

action for each available resource group.

Adapt the resource actions using the dropdown box.

It is recommended that you keep the settings. Adaptations are only necessary in a few situations, if no

changes should be made.

For further information on the settings see the chapter 'Migration Dialog Box'.

8. Click OK to start the migration.

The migration will now be executed. During the migration the write permissions of the resources to be deleted

are removed automatically.

9. Click OK in the progress dialog, if the migration is completed.

10. The synchronization of all resources with the central workarea is started automatically.

Click OK in the progress dialog, if the synchronization is completed.11. Click Restart in the opened dialog that the changes can take effect.

Recommendation

The migrated resources have the synchronization status Edit and own. If you want to finish the editing

change the status to Edit and share.

Note

Do not restore outdated resources from the trash of the central workarea in your local workarea.




Installation

Customer


Migration steps for the standard author

After the migration of the central workarea by the master author the standard author can migrate the local

workarea as follows:




4. The authentication dialog appears. Insert your user data with the new password.

5. After the workarea opens, the synchronization of the resources with the central workarea starts

automatically.

If the authors use an Instant Producer the synchronization of the workarea is executed automatically after the

start of the program.

3.6.5.3 Migration Dialog Box

The migration dialog box opens automatically, if the workarea contains outdated resources. The dialog box

contains different setting areas for structuring the resource groups. Each resource group has an individual

migration action.

Migration setting areas

The migration dialog box contains the following setting areas: Documentation Settings and Style:

Contains the setting and style resources, that are relevant for generating documentation.

Authoring and Playback Settings:

Contains the setting resources, that are relevant for the creation and playback of content.

Deprecated Resources:

Contains outdated resources, which have to be removed. The resources will be replaced by new resource

types.

Required Resources:

Contains resources, which have to be installed. The resources are necessary for content creation and

playback.

Recommended Resources:

Contains resources, which can be installed optionally.

Incompatible Old Resources:

Contains outdated resources, which have to be replaced with a newer resource type.

Compatible Old Resources:

Contains resources of the same type, which have to be updated.

User Resources:

Contains resources, which have to be updated.

Customized User Resources:

Contains adapted resources, which have to be updated.

The areas that are shown depend on the available resources.



28

Customer



Installation

Migration actions

The following migration actions can be executed for a resource:

Convert:

Updates the files and structures of an available resource.

Install:

Integrates a new resource into the resource structure.

Can be used instead of converting a resource. Does not save the available settings.

Remove:

Deletes an outdated resource from the structure.

Overwrite:

Updates the files of an available resource.

Skip:

Keeps the current resource status.

When selecting a resource, you will see the version and included sub-resources in the help box at the bottom of

the dialog box.

3.6.5.4 Migration of Imported Resources (Conversion)

Beside the migration of a complete workarea single outdated resources can be migrated after the import into an

up-to-date workarea. This can be done for own styles or to use own settings of an older version. The resources will

be inserted as additional resources in the structure and marked with converted. In the workarea available

resources won't be overwritten.

Migration of resources

For the migration of imported resources, proceed as follows:

1. Open the Producer with an up-to-date workarea.

2. If you use a central workarea, start the editing of the resource group to get the write permission.

3. Import the resource archive by using the menu entry Workarea -> Administration -> Import Archive...

4. In the opened dialog select the archive and click Open.

5. In the import dialog select the resource and click Ok.

6. After the import of the resource the migration dialog opens automatically.

Click Ok to start the migration.The migration will now be executed.

7. With the finishing of the migration a folder with log files opens.

The resources are stored in the resource structure and marked as converted.

8. If you use a central workarea, save the resources to the server.

Handling of migrated resources

The screenshot shows an example for converted resources after the import of a Standard resource. The settings

and documentation templates are created in the resource structure of a current version. The resources marked

with converted and number 2 (or higher) for the second object of a resource type.




Installation

Customer


The converted resources are additional resources and can be used as standard resources or can be deleted, if not

required. In this case, the settings can be activated in the Configurations resource and the Documentation Style in

the Documentation Settings.

Note, that it is not possible to change the name of the resources. Import only needed resources to keep a clearly

structure.

3.6.5.5 Differences in Resource Structure

The resource structure of the SAP Workforce Performance Builder 9.2 - 9.x release is different to the structure in

release 9.1. This means that a migration is necessary to guarantee error-free creation and playback of content.

For the standard resources the differences are as follows:

9.1 Resources 9.2 - 9.x Resources Recommended Migration

Adaptable Resources Convert and Install

Authoring Settings Convert

Playback Settings Convert

Navigation Authoring Settings Convert

Navigation Playback Settings Install

Text Style Install

Navigation Style Install



30

Customer



Installation

9.1 Resources 9.2 - 9.x Resources Recommended Migration

Desktop Assistant Style Install

trainer Standard Style

(includes book Style, library Style,

Mouse Pointer, trainer Panel,

Popup Style, Quiz Style, Task

Window Style)

Install

trainer Mobile Style Install

Documentation Style

(includes Documentation

Templates)

Convert

Book Styles Book Styles Overwrite

Bubbles Types Bubbles Types Overwrite

Documentation Settings Convert

Glossaries Playback Dictionaries Overwrite

Help Help Overwrite

library Styles Remove

Macrosets Macrosets Overwrite

Mouse Pointers Remove

trainer Panels Remove

Popup Styles Remove

Quiz Styles Remove

Application Profiles Application Profiles Overwrite

Content Glossaries Recording Dictionaries Overwrite

Scripts Scripts Overwrite

Configurations / Styles Configurations Remove old resource

Install new resource

Task Window Styles Remove

trainer trainer Remove old trainer

Install new trainer




Installation

Customer


3.6.6 Settings for recording and playback

Depending on your scenario the setup of some settings may be required for recording and rerecordingapplications as well as for the playback of recorded contents. Read the chapter "Settings" in the application help

of the Producer for detailed instructions.

Consider to check the application manual on SAP Help Portal for most recent instructions.

http://help.sap.com/wpb






32

Customer



Post-Installation

4 Post-Installation

4.1 Database

The package does not connect to a database.

4.2 Files

The package needs to add/replace/remove files:

Filename/Directory Action

Application installation folder

(Default: %PROGRAMFILES(X86)%\SAP Workforce

Performance Builder\Producer<version>

Create folder and add anxillary structure

Replace anxillary files (on update)

Remove folder (on uninstallation)

Workarea directory

(Default: %USERPROFILE%\Producer

Workareas\<name of workarea>)

Create folder

Create anxillary folders and files

Replace anxillary folders and files

Remove anxillary folders and files

Desktop Shortcut Create shortcut

Remove shortcut (on uninstallation)

4.3 Registry

The package needs to add/update/remove registry keys|values:

Registry Key Action

HKEY_CURRENT_USER\Software\SAP Workforce

Performance Builder\Producer<version*>\install

add entries (on installation)

remove entries (on uninstallation)

HKEY_CURRENT_USER\Software\SAP WPB\Expert add entries

change entries

remove entries

HKEY_CURRENT_USER\Software\SAP

WPB\FileControl

add entries

change entries

remove entries




Post-Installation

Customer


Registry Key Action


WPB\FileSelector

add entries

change entries

remove entries


WPB\Producer<version*>

add entries

change entries

remove entries

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\datan

go.License




go.Package




go.Project




go.ProjectPackage



HKEY_CLASSES_ROOT\sap.slc add entries (on installation)


HKEY_LOCAL_MACHINE\SOFTWARE\\Microsoft\Wi

ndows\CurrentVersion\Installer\Folders



HKEY_LOCAL_MACHINE\SOFTWARE\\Microsoft\Wi

ndows\CurrentVersion\Installer\UserData\<id>\Co

mponents




e\SAP WPB



*In Windows Registry version numbers are written without periods.



34

Customer



Additional Information

5 Additional Information

5.1 Settings for Recording and Playback

For recording and editing contents within the Producer as well as for playing back contents using the trainer,

library and book reader functionalities several settings are required. Further information are available in the

"Settings" chapter of the Producer manual.

5.2

Uninstalling Producer

If you would like to uninstall the Producer, this is done from the Settings -> System control -> Software menu:

1. A dialog will open listing all the programs on your PC. Select the Producer.

2. Click on the Remove button.

3. A dialog will open. Initiate the uninstallation process by clicking on the Yes button.

4. The Producer will be deleted from your PC. When uninstallation is complete you can close the Software

dialog.

Note

When uninstalling the Producer only the program is deleted. The workareas that were created are

retained for further use.

Alternatively you can also perform the uninstallation using the Producer.msi installation file from the

corresponding version of your Producer:

To do so, launch the installation program by double clicking on the installation file. Then click on Next. Select the

option Remove and confirm your selection by clicking on the Remove button. The Producer will now be

uninstalled.

5.3 Working with the Producer under Citrix

Certain requirements and settings are necessary in order to be able to use the Producer in a Citrix environment to

ensure that projects are successfully recorded.

Note

The Producer should preferably be installed on the terminal server as, with local installation, recording

using the Citrix client is only possible with graphical object recognition.





Customer


The Citrix clients

So-called clients are required to access the Producer and the applications on the terminal server.lease note:

Use a version 11.0 Citrix client or later. With older versions, there can be no guarantee that working with the

Producer will be trouble-free.

5.3.1 Installation on the Citrix terminal server

You can install the Producer directly on a terminal server, thereby making it available to the authors.

This is the recommended installation as it allows the Producer to access the various object recognition interfaces

instead of being blocked by the Citrix client when installed locally.

Internet Explorer, for postprocessing of the projects, as well as Microsoft Office for generating documentation are

also to be installed on the same server and started in the same session.The authors should also possess user rights for the Producer BHO, required for postprocessing.

Note

When working with Producer, ensure that you always implement each application you are using on the

same server and start it in the same session. This is necessary for trouble-free recording, postprocessing

and publication of the projects.

Customizing display characteristics

The following system settings are also to be applied:

Set a color depth of 24 bits for the terminal server, workstation and Citrix client. Ensure that you apply

matching settings for the systems.

Deactivate Screen font anti-aliasing on the terminal server and author workstation.

5.3.2 Seamless Load-Balancing Citrix

With a seamless transmission and for load-balancing, take care to ensure that the Producer and the application to

be recorded are launched in one session from the same server.

Special attributes when using load-balancing:

The Producer has to be installed on each server in the cluster. Do not install the Producer on the virtual

server, which is there to balance the load between the servers.

Special attributes when using seamless:

Set the same parameters (resolution, color depth, encryption) when publishing the Producer via Citrix and for

the target application.



36

Customer




5.3.2.1 Functional test for seamless transmission

Once the Producer has been provided via seamless transmission, a test should be run to establish whetherInternet Explorer can be launched from within the Producer.

If the Producer cannot be launched, seamless transmission must be converted to desktop for each author on a

one-time basis. The Producer is then launched using desktop transmission and Internet Explorer is started.

If launch is possible, the transmission can be switched back to seamless.

5.3.3 Setting up an author environment

When creating projects, it is recommended that an author environment be set up for the authors on a separate

server on which the authors are given access to all the necessary applications, settings and rights. This ensures

that the Producer will operate smoothly and free from errors.

Also pay attention here to the section: Installation on the Citrix terminal server.

The author workstations can be regular workstations or else be set up as thin PCs. Thin PCs are workstations on

which only one operating system is installed and which draw their data and applications from a server.

The following overview summarizes the necessary requirements to be borne in mind for an author environment:

Author workstations & Terminal server Author environment

Producer installation

Installation of applications to be recorded

Internet Explorer with corresponding accessrights

Microsoft Office for creating documentation

Matching settings for color depth and resolution

Deactivation of screen font anti-aliasing.

For the recording: Launching of the Producer and

target application in the same session



www.sap.com/contactsap

Material Number


No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software

vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System ads, System i5, System

p, System p5, System x, System z, System z10, System z9, z10, z9,

iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS,

S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise

Server, PowerVM, Power Architecture, POWER6+, POWER6,

POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2

Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,

Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are

trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and

other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems

Incorporated in the United States and/or other countries.

Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod,

iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are

trademarks or registered trademarks of Apple Inc.

Oracle and Java are registered trademarks of Oracle and its

affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks

of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP Business ByDesign, and other SAP products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. All other product and

service names mentioned are the trademarks of their respective

companies. Data contained in this document serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice. These

materials are provided by SAP AG and its affiliated companies ("SAP

Group") for informational purposes only, without representation or

Producer 9.3 Installation Guide en-US

Documents

Transcript of Producer 9.3 Installation Guide en-US