Preparing for an SAP SuccessFactors Career Site Builder Implementation

Designing the Career Site

Completing the Initial Setup of the Recruiting System

Building the Career Site

Moving the Career Site to Production

Engaging Potential Candidates

Implementing Source Reporting

Succeeding as a Consultant

Completing the Import of Career Site Settings to Production

Objective

After completing this lesson, you will be able to complete the import of career site settings to production.

Production Environment XML Imports

Import the CSB XMLs into the target (production) instance in the following order:

Site Settings XML (SiteImport).
Career Site Builder Settings XML (SiteBuilderExport).
Category Pages XML (CategoryExport).
Translations XML from Tools→Translations (TranslationOverrideExport).
After selecting the import file, choose Upload Import File.

Security Key for the Production Instance

The leading practice is to generate a unique security key for both stage and production. Remember that the security key must be unique for each CSB instance hosted in a data center.

Insert the new security key in two places in the production environment:
- From CSB select Settings→Site Configuration→Site Integrations: Single Sign-On Security Key.
- From Provisioning select Recruiting Marketing Settings: Security Key.
Run Recruiter Sync. From CSB, select Settings→Site Configuration→Site Integrations→Site Integrations, and then choose Execute Now.

Job Sync in Production

Jobs are not included in imports. After importing XML files into the production environment, you will need to sync the jobs in that instance. From Provisioning, run the scheduled job the Job Type Sync all external job postings, and then do a search in the target career site to ensure that the active jobs appear in the results.

Items Transferred During Export/Import Process

Site settings are transferred to the target instance, including settings that integrate the career site with SAP SuccessFactors Recruiting.

Other considerations include:

All site configurations and database records are updated, including locales and brands.
Settings that configure the look and feel of the career site are transferred.
Career site contents are transferred, including active category pages. New categories are added to the target, and existing category pages with the same name are overwritten.
Candidate Relationship Management functions in Career Site Builder are transferred, including landing pages, data capture forms, and email layouts. Note that all landing pages and data capture forms on the target instance are removed and are replaced by the pages and forms from the source.
Be aware that all images, including archived images, are copied to the target instance.

Items That Do Not Import

Items that do not import include:

Jobs (requisitions) are not transferred to the target instance.
Pages that were saved using Save Draft will not be part of the export.
To maintain site integrity, site integration information is not included in the export, including the security key and API credentials. (See exceptions to this in the section on updating values.)
Candidate Relationship Management functions within the SAP SuccessFactors Recruiting application do not transfer: talent pools and email campaigns.

The following elements do not transfer during the import process. These need to be configured in the target instance:

CSB Role Based Permissions (Users→Roles)
Job Alert Email Template (Layouts→Job Alerts Email Template)
Site Source Editor (Tools→Site Source Editor)
Advanced Analytics (Command Center→Recruiting Advanced Analytics)

Import and Export Career Site Builder Settings XML Files

This video demonstrates how to import and export Career Site Builder settings.

Business Example

This exercise provides steps for two use cases:

MOVE: You are moving the site settings from a source to a target environment.

BACKUP: You are creating a backup of a site's settings that can be reimported to the source environment.

If you have a training environment, you will follow the BACKUP instructions. After exporting, you'll make a change in your career site and reimport, which will reverse the change.

Later, when you are implementing CSB, after your customer approves the site in the stage environment, you will follow the MOVE instructions.

Task 1: Export from the Source Environment

Note

For both MOVE and BACKUP use cases.

Steps

Navigate to CSB→Tools→Import & Export.
Click the Export tab.
Select Site Settings and then select Export and save the export file to your drive.
Select Career Site Builder Settings and the following option beneath it: Site Settings, As currently configured, Core CSB Settings, Fonts and Images, Email Layouts.
Choose Export and save the export file to your drive.
Select Category Pages, then select Export, and save the file.
Navigate to CSB→Tools→Translation.
Select Export and save the file.

Task 2: Replace Fields in the Site Settings XML Export File

Note

Use for MOVE case only. (BACKUP use case: Simply search for the fields but make no replacement.)

Steps

In the target instance of CSB, navigate to Settings→Site Configuration→Site Information and note the Site Name,Company Name,Site URL (also called the Portal URL), and Job Alert Email Address.
Search through the Site Export XML file for the following tags, and replace them with target values, taking care to not change the case (upper or lowercase). Replace the values with the following values:
- ＜name＞
- ＜portalurl＞
- ＜agentemailaddress＞
- ＜companyname＞
- ＜sitefolder＞
- ＜phrasefilterback＞

Task 3: Update Non-Relative Links in the Career Site Builder Settings XML File, if Necessary

Note

Use for MOVE case only.

Steps

Navigate to Pages→Content→English→Company.
Choose the gear icon and select Delete Page.
View a preview of your career site.
From the Best Run home page, under the Why Work Here dropdown in the header, select Company. Because the page is missing, this is a broken link (as expected).

Task 4: Make a Change in Your Training Instance to Test Using Import/Export for Backups

Note

Use BACKUP use case only. For this task, delete the Company page for the Best Run brand.

Steps

Navigate to Pages→Content→English→Default Brand→Company.
Select the gear icon and choose Delete Page.
View a preview of your career site.
From the Best Run home page, under the Why Work Here dropdown in the header, select Company. Because the page is missing, this is a broken link (as expected).

Task 5: Import to the Target Environment

Note

Use for both MOVE and BACKUP use cases.

Steps

In the target instance, navigate to CSB→Tools→Import & Export. (For BACKUP, you will reimport to the source instance.)
Choose the Import tab.
Select Site Settings and select Import.
Navigate to find the SiteExport.xml file and choose Upload Import File.
Select Career Site Builder Settings and then select Import.
Navigate to find the SiteBuilderExport file and select Upload Import File.
Select Category Pages and select Import.
Navigate to find the CategoryExport file and choose Upload Import File.
Navigate to CSB→Tools→Translation.
Select Import.
Navigate to find the TranslationOverrideExport file and choose Upload Import File.
BACKUP: To check that the import was successful, confirm that the Best Run Company content page was restored.

Task 6: Sync Jobs in Production

Note

Use for MOVE case only.

Steps

From Provisioning in the production environment, select Manage Scheduled Jobs and run the job with the Job Type Sync all external job postings.
Open the production CSB site and search for jobs to confirm that all jobs synced.
If not, check the Export Automated Process Log in Command Center.

Summary

CSB XML files should be imported into production in the sequence of Site Settings, CSB Settings, Category Pages, and Translations, with each file uploaded individually to ensure a clean and consistent migration.
A unique SSO security key must be generated and applied in both CSB and Provisioning so that production (and stage) environments authenticate correctly and securely.
After the import is complete, Recruiter Sync must be run, and jobs must be synchronized separately through the external job posting sync process, followed by validating that job search results appear correctly on the live site.
It is important to understand what content transfers during migration: site design, locales, brands, category pages, CRM assets within CSB, and all images will move over, while items such as jobs, draft pages, integration credentials, CRM objects, and certain configurations (including RBP roles, job alert templates, source tracking, and analytics) must be recreated or configured directly in the target environment.

Next lesson