SAP Catalog
Content
Management
1.0
Configuration
ASM-SRM
Field Services, Americas
© SAP AG 1
Session Objectives
This session provides a brief overview of configuration in SAP
Catalog Content Management (SAP CCM 1.0)
At the end of this session, you know about:
Configuration – CCM 1.0
© SAP AG 2004
© SAP AG 2
XI Configuration
Catalog Authoring Tool
TREX
Catalog Search Engine
Summary
© SAP AG 3
XI Configuration
Catalog Authoring Tool
TREX
Catalog Search Engine
Summary
© SAP AG 4
XI Configuration (1)*
Configure the SLD (System Landscape Directory)
Configure the technical system landscape
Configure the business system landscape
Define technical systems
Define business systems in the Integration Builder
Import business scenarios
© SAP AG 2004
*In order to avoid redundancy, XI configuration steps has been kept brief. Please review the XI 3.0
configuration guide for more information.
© SAP AG 5
XI Configuration (2)
Configuring communication and security
Create RFC destination for the HTTP connection to the HTTP adapter
of the Integration Server
2. Specify settings for catalog
upload HTTP adapter RFC
destination (XI)
1. Create RFC destination (make sure the
path prefix is changed to
/sap/xi/adapter_plain)
© SAP AG 2004
© SAP AG 6
XI Configuration
Catalog Authoring Tool
TREX
Catalog Search Engine
Summary
© SAP AG 7
Activate SICF Nodes
Activate nodes under
SICF (default_host →
sap → bc → bsp →
ccm)
© SAP AG 2004
© SAP AG 8
Logical Systems
The activities Define Logical Systems
and Assign Logical Systems to Client
must to be carried out once (given that
the same client is used for both CAT
and CSE)
© SAP AG 2004
© SAP AG 9
Generate Profile (CSV and Non-CSV)
CSV upload only:
Generate auth. profile for:
/CCM/CATALOG_MANAGER
/CCM/CATALOG_APPROVER
non-CSV upload:
Generate auth profile for:
/CCM/CATALOG_MANAGER
/CCM/CATALOG_APPROVER
SAP_XI_APPL_SERV_USER
Assign XI user specified for
receiver channel to:
/CCM/CATALOG_APPROVER
SAP_XI_APPL_SERV_USER
© SAP AG 2004
© SAP AG 10
Settings for Publishing Catalogs
Specify if local
publishing is required
© SAP AG 2004
© SAP AG 11
Settings for Catalog Upload
Specify settings for
catalog upload HTTP
adapter RFC destination
(XI)
© SAP AG 2004
© SAP AG 12
XI Configuration
Catalog Authoring Tool
TREX
Catalog Search Engine
Summary
© SAP AG 13
TREX: Some Brief Points*
TREX version used 6.1
SAP Catalog Content Management uses RFC connections to
communicate with TREX. Perform the steps to set up an RFC
destination only.
Automatic language recognition is not required. Adopt the default
settings for document languages during the installation of TREX.
No Python extensions are required
A search server relation is not required
CCM uses the TREX ABAP client only
© SAP AG 2004
*As with XI configuration, TREX installs are standard and need not be covered in detail
TREX: Text Retrieval and Extraction (6.1)
© SAP AG 14
XI Configuration
Catalog Authoring Tool
TREX
Catalog Search Engine
Summary
© SAP AG 15
Generate Profile (Search User)
Catalog search (user):
Generate auth. profile for:
/CCM/CATALOG_SEARCH
© SAP AG 2004
© SAP AG 16
TREX RFC Destination
1. Create RFC destination for
TREX (Activation type 2. Create connection between the
Registered) Catalog Search Engine and TREX (RFC)
© SAP AG 2004
© SAP AG 17
XI Configuration
Catalog Authoring Tool
TREX
Catalog Search Engine
Summary
© SAP AG 18
Summary
The following areas have been addressed in this session:
Configuration aspects in CAT and CSE
Overview of XI and TREX areas
© SAP AG 2004
© SAP AG 19
Copyright 2004 SAP AG. All Rights Reserved
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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of
Microsoft Corporation.
IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®,
OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix
and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
ORACLE® is a registered trademark of ORACLE Corporation.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and
other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
JAVA® is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, R/3, mySAP, mySAP.com, xApps, xApp 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.
© SAP AG 2004
© SAP AG 20
