You are on page 1of 14

Data Hub Pre-Installation Planning Guide

Critical things to know before


deployment!

INTERNAL
Agenda

• Critical
Documentation
• Project Issues

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 2


Agenda

• Critical
Documentation
• Project Issues

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 3


Critical Documentation
Pre-installation planning guide -
https://help.hybris.com/6.4.0/hcd/b6249b95017c4a7fa0ec73fb8bd7efca.html

Hardware Guidelines -
https://help.hybris.com/6.4.0/hcd/2e17d39b612840648c76690dd2696645.html

Dynamic Publication - https://help.hybris.com/6.4.0/hcd/7cb1b38932bd4da0a4f02c5ccdaad0ce.html

Logging Item Behavior -


https://help.hybris.com/6.4.0/hcd/923a906ebb23453782ebe8c6f89560de.html

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 4


Pre-installation planning guide
• Only send relevant data
• Extra data incurs extra processing cost
• Enable cleanup to keep database volume manageable
• Always use raw, canonical, target item cleanups
• Published item cleanup with adequate delay is ideal
• Check special database concerns
• Oracle 11g query plans
• MS SQL index fragmentation

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 5


Hardware Guidelines
• Determine required KPIs and plan accordingly

• Hybris Commerce must be sized to handle the inbound load


• Data Hub can not increase the impex speed of Commerce
• To increase Data Hub performance
• Add more memory and increase batch sizes
• Increase concurrency by dividing across pools – with enough cores available

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 6


Dynamic Publication

ALWAYS USE IN_MEMORY MODE

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 7


Logging Item Behavior
• Critical debugging tool
• Can be run full time in production with adequate disk and log management

• Identify issues with


• Data
• Custom mappings
• ‘Lost’ items

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 8


Agenda

• Critical
Documentation
• Project Issues

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 9


Underestimating Integration Complexity
• Must be adequately planned for

• Will always be issues with


• Bad/Missing data
• Unclear business requirements
• Unstable infrastructure
• Complex system architectures
• Testing a few sample items does not guarantee immediate success with full data loads

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 10


Lack of Expertise
• Ideal to have experts available in
• Hybris Commerce
• Back end systems
• Data Hub
• Business domain

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 11


Performance / Stability
• Documented steps and guidelines not followed

• Unstable infrastructure – the basics must work!


• DB Connection issues
• System to System connectivity issues
• Inadequate System Architecture
• DB resources should NOT be shared by Commerce and DataHub in any significant sized project
• Every subsystem must be sized appropriately

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 12


Q&A
THANK
YOU!

You might also like