Integration Framework of SAP Business One Settings for
Integration Framework of SAP Business One Settings for Development Environment 10, 2015 INTE RNA L
Objectives At the end of this course, you will be able to: n Change the integration framework environment from a productive system to a development system n Configure the message log for use in a development environment n Further configure the development system by: § Setting up notifications for blocked queues § Changing the default error handling for scenario processing § Expanding Tomcat memory § Starting the integration framework in safe mode © 2015 SAP SE or an SAP affiliate company. All rights reserved. 2
System Profiles
Development and Productive System Profiles § The integration framework can operate as either a productive system or a development system § After installation, default is a productive system profile § To create and test new scenarios, you need to switch the system profile to a development system Productive system indicated by blue upper line Development system indicated by gold upper line © 2015 SAP SE or an SAP affiliate company. All rights reserved. 4
Version and System Information Path: Maintenance → System Info Integration framework information: n Version Number of installed integration framework n Version Information: list of changes with each version n Functions: available inbound and outbound channels, atoms and functions in current release © 2015 SAP SE or an SAP affiliate company. All rights reserved. 5
Switching to the Development Profile Path: Maintenance → System Info § The development system profile contains the recommended configuration settings for scenario development, testing and debugging. § To switch to the development system profile, select the ellipsis button for the System Profile field and choose Development System Then restart the SAP Business One Integration Service © 2015 SAP SE or an SAP affiliate company. All rights reserved. 6
Development System Profile Path: Maintenance → System Info § Choose the icon to open the System Profiles § The development system profile is optimized for scenario development: § § The session timeout is increased § Web. DAV support is enabled § Remote access enabled Productive System Development System You should enter a development prefix and description for your company © 2015 SAP SE or an SAP affiliate company. All rights reserved. 7
Development System Profile - 2 Settings in the development profile for testing and debugging scenarios: § Record test messages at runtime for later use § Activate scenarios with detailed logging for step-by-step process flow debugging § Allow modification of an activated step during testing § Embedded XML editor © 2015 SAP SE or an SAP affiliate company. All rights reserved. Productive System Development System 8
Development System Profile - 3 Settings for detailed logging of messages: § Message log level is Full message § B 1 Event Monitor switched on § Message log entries enforced for HTTP and Web service calls § Logged messages can be updated during processing (Final message only checkbox unchecked) © 2015 SAP SE or an SAP affiliate company. All rights reserved. Productive System Development System 9
Development System Profile - 4 Settings for capture of detailed transaction information: § x. Cellerator log level set to CONFIG § Scenario debug enabled © 2015 SAP SE or an SAP affiliate company. All rights reserved. Productive System Development System 10
Additional Message Log Configuration -1 Path: Maintenance → Cfg Msg. Log To avoid large log files, make sure daily deletion is enabled § Daily Deletion: Enable automatic daily deletion of message logs § Indexed Access: improves performance of accessing message logs (default) § Blocksize: Number of messages displayed § User Interface Refresh Timeout: controls how long time filters are displayed in message log view © 2015 SAP SE or an SAP affiliate company. All rights reserved. 11
Additional Message Log Configuration -2 Path: Maintenance→ Cfg Msg. Log – Daily Deletion Parameters for daily deletion of logs: n Deletion Time: hour n Backup Buffer: number of days to exclude from deletion n Delete Imported Messages: imported messages included in daily deletion Option to instantly delete log by selecting Manual Deletion checkbox © 2015 SAP SE or an SAP affiliate company. All rights reserved. 12
Error Handling
Maintenance Default Error Handling Path: Maintenance → Cfg Error Handling n View the default error handling for synchronous and asynchronous transaction processing n Select the error handling option for Processing phase You can also define error handling in the scenario package. Choose Scenarios > Package Design, and select the Definitions button. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 14
Maintenance Error Handling – Overall Actions Path: Maintenance → Cfg Error Handling → Overall Actions n Choose the Overall Actions button to enable a notification to be sent when a message blocks an internal queue n Choose the Configure button to provide the email details © 2015 SAP SE or an SAP affiliate company. All rights reserved. 15
Maintenance Error Handling – Outbound Error Actions - 1 Path: Maintenance → Cfg Error Handling → Outbound Error Actions n Option to define specific error actions that apply at package, step, or outbound channel level n Choose Outbound Error Actions button n Choose to define a new error action © 2015 SAP SE or an SAP affiliate company. All rights reserved. 16
Maintenance Error Handling – Outbound Error Actions - 2 Path: Maintenance → Cfg Error Handling → Outbound Error Actions To define the error actions: 1. Select the error action type (scenario, step, or outbound) 2. Select the event that triggers the error action 3. Click the Select Actions button then select applicable actions to respond to the error action type and event 4. Choose the Activate button to activate the action © 2015 SAP SE or an SAP affiliate company. All rights reserved. 3 5 4 17
Other Development Settings
Configuration Tomcat Memory n Assign more RAM to improve performance: Path: . . SAP Business OneSAP Business One Integration Integration ServerTomcatbin_64 (or bin)tomcat 6 w. exe ● To assign Tomcat memory: ● Open tomcat 6 w. exe ● Select the Java tab ● Recommended values for a 32 bit system: ● Initial memory pool: 256 MB ● Maximum memory pool: 1024 MB ● Recommended values for a 64 bit system: ● Initial memory pool: 256 MB ● Maximum memory pool: 2048 MB or more, depends on server memory, no limit defined by Tomcat © 2015 SAP SE or an SAP affiliate company. All rights reserved. 19
Safe Mode Configuration xcellerator. cfg File n You can start the integration framework in safe mode by changing the parameter in the configuration file: Path: . . SAP Business OneSAP Business One Integration Integration ServerTomcatwebappsB 1 i. Xcellerator xcellerator. cfg Safe Mode Use cases • • • Locked administrator user – see SAP Note # 1556041 An error-prone process blocks the integration framework, even after restart Integration framework will not start due to application deployment problems © 2015 SAP SE or an SAP affiliate company. All rights reserved. Activation • Set xcl. safemode=true • Restart the integration service Safe Mode Limitations • All adapters are disabled • User authentication is disabled • Access is only possible from the local machine. 20
Summary n The integration framework provides system profiles for a development and productive environment. These profiles contain the recommended configuration settings for each environment n After installation, the integration framework is set to a productive environment. To develop and test scenarios, you need to switch to the development system profile n Development profile is optimized for scenario testing and debugging, including: § § § Web. DAV client access Remote access Modification of active scenario step information Full message logging to enable scenario monitoring Detailed transaction logging and scenario debugging n You can optionally set email notifications for blocked queues and select actions for outbound channel errors n You have the possibility to expand Tomcat memory and start the integration framework in safe mode © 2015 SAP SE or an SAP affiliate company. All rights reserved. 21
Thank You!
© 2015 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http: //global 12. sap. com/corporateen/legal/copyright/index. epx for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 23
- Slides: 23