Enterprise Advanced Configuration Winfried de Vries May 13, 2009
Enterprise Advanced Configuration Performance Hardware set-up Issues Security Trouble-shooting
Enterprise System Components Database Application Server Clients: InDesign, InCopy, Content Station etc. FileStore
Enterprise System Components Application Server nts: InDesign, Memory++ opy, Content Station etc.
Enterprise System Components Database Application Server Memory++ Disk IO++
Database THE FAST TRACK TO ONLINE Enterprise System Components Application Server FileStore Memory++ Disk IO++
Enterprise System Components Database Application Server Clients: InDesign, InCopy, Content Station etc. FileStore
Performance Issues How is your system performing
Performance Issues How is your system performing
Performance Issues How is your system performing or
Performance Issues How is your system performing or
Why can there be performace issues?
Why can there be performace issues? Woodwing has got no control over the setup of the components
Why can there be performace issues? Woodwing has got no control over the setup of the components Because the hardware, OS and database choices are a partner/customer decision.
Why can there be performace issues? Woodwing has got no control over the setup of the components Because the hardware, OS and database choices are a partner/customer decision. Customizations and interfaces that are not optimized.
Measuring performace, how?
Measuring performace, how? specify the ʻscopeʼ of the measurement: limit the scope to what can be measured accurately.
Measuring performace, how? specify the ʻscopeʼ of the measurement: limit the scope to what can be measured accurately. create a reproducible scenario and prerequisites. Make a copy of the used files for future comparisons.
Measuring performace, how? specify the ʻscopeʼ of the measurement: limit the scope to what can be measured accurately. create a reproducible scenario and prerequisites. Make a copy of the used files for future comparisons. Test on a ʻcleanʼ system: switch off additional server-plugins and client side scripting.
Measuring performace keep in mind that writing down logfiles has got influence on performance. look ʻtop-downʼ, first total time, then start narrowing down. User functions Enterprise commands, Database actions, Data transfer, Client Performance
Performance logging Switch on debugging on server Configserver.php // ---------------------------------------------------------------------------- // Debugging - Low-level logging of SQL, SOAP details etc. // ---------------------------------------------------------------------------- define ('DEBUGLEVEL', 'INFO'); // NONE, ERROR, WARN, INFO, DEBUG define ('OUTPUTDIRECTORY', '/log/'); // including '/', e.g. "c:/enterpriselog/output/" define ('PROFILELEVEL', 1); // [0,5] 0: no profiling, 5: most detailed define ('LOGSQL', false); // log the SQL, requires DEBUGLEVEL DEBUG or INFO For performance logging, use INFO For functional debugging, use DEBUG
Performance logging Set profilelevel to 5 to get maximum server info peformanceprofiler.dat sce_profile_mysq.htm
Database performance pitfall Table scans, caused by: Queries on columns that have no index Mostly in interfaces and customizations Use database monitoring tools: phpmyadmin:
Security
Why security?
Why security? Information abuse
Why security? Information abuse Production disturbance
Why security? Information abuse Production disturbance User mistakes
Why security? Information abuse Production disturbance User mistakes Hardware failure
Secure Enterprise installation
Secure Enterprise installation Change password of default WoodWing user
Secure Enterprise installation Change password of default WoodWing user SSL (HTTPS)
Secure Enterprise installation Change password of default WoodWing user SSL (HTTPS) Separate database user for woodwing
Secure Enterprise installation Change password of default WoodWing user SSL (HTTPS) Separate database user for woodwing File access (config.php, directories,...)
Secure Enterprise set-up
Secure Enterprise set-up Full / Limited Administrators
Secure Enterprise set-up Full / Limited Administrators Workflow
Secure Enterprise set-up Full / Limited Administrators Workflow Password rules
Secure Enterprise set-up Full / Limited Administrators Workflow Password rules config/configserver.php
Secure Enterprise set-up Full / Limited Administrators Workflow Password rules config/configserver.php Customize with a plug-in
Enterprise backup Standard version control Settings in config/configserver.php Workflow Status property Trash Can Database / FileStore / AS backup
Troubleshooting
Troubleshooting in Enterprise
Troubleshooting in Enterprise Why: To get detailed information about a problem in the system.
Troubleshooting in Enterprise Why: To get detailed information about a problem in the system. With as goal: To solve the problem yourself! To send an issue report to woodwing
Approach
Approach Make sure the issue is reproducible:
Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise
Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario.
Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario. 1. from InDesign, logon as user ʻxxxʼ on server ʻmyserverʼ
Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario. 1. from InDesign, logon as user ʻxxxʼ on server ʻmyserverʼ 2. create a layout and save-version with name ʻlayout1ʼ
Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario. 1. from InDesign, logon as user ʻxxxʼ on server ʻmyserverʼ 2. create a layout and save-version with name ʻlayout1ʼ 3. place uploaded image with name ʻproblem1.jpgʼ on layout ʻlayout1ʼ
Approach Make sure the issue is reproducible: Write down/collect prerequisites (if any). upload attached image ʻproblem1.jpgʻ to Enterprise Write a scenario. 1. from InDesign, logon as user ʻxxxʼ on server ʻmyserverʼ 2. create a layout and save-version with name ʻlayout1ʼ 3. place uploaded image with name ʻproblem1.jpgʼ on layout ʻlayout1ʼ 4. From SCE-panel, rename ʻlayout1ʼ to ʻlayout123ʼ Result: Error back from server ʻUnable to renameʼ On client, switch of all client side scripting.
Test on a clean system To create a clean system: Remove or switch of all non-standard server plugins. test without any other users, or : create a separate Application Server with debug on, using the same database and filestore create a complete copy of the system as test system. Production Debug Application Server Application Server
Is the scenario still valid? Replay the scenario on the clean system. Is the issue still there? No? -> Switch on customizations one-by-one until problem appears again. Yes? -> Switch on logging and run scenario
Switch on logging Server side: configserver.php Text // ---------------------------------------------------------------------------- // Debugging - Low-level logging of SQL, SOAP details etc. // ---------------------------------------------------------------------------- define ('DEBUGLEVEL', 'DEBUG'); // NONE, ERROR, WARN, INFO, DEBUG define ('OUTPUTDIRECTORY', '/log/'); // including '/', e.g. "c:/enterpriselog/output/" define ('PROFILELEVEL', 1); // [0,5] 0: no profiling, 5: most detailed define ('LOGSQL', false); // log the SQL, requires DEBUGLEVEL DEBUG or INFO Client side wwsettings.xml <SCEnt:LogFile RequestBuffer ="Macintosh HD:ClientLog:" ResponseBuffer="Macintosh HD:ClientLog:" SOAPResponse ="Macintosh HD:ClientLog:" SOAPRequest ="Macintosh HD:ClientLog:" Advanced ="true"/>
Support@woodwing.com
Support@woodwing.com Send all info to woodwing support:
Support@woodwing.com Send all info to woodwing support: System information. OS, PHP version, database type
Support@woodwing.com Send all info to woodwing support: System information. OS, PHP version, database type Prerequisites & Scenario
Support@woodwing.com Send all info to woodwing support: System information. OS, PHP version, database type Prerequisites & Scenario Logfiles
Support@woodwing.com Send all info to woodwing support: System information. OS, PHP version, database type Prerequisites & Scenario Logfiles Severity of the issue (reseller guide)
Support@woodwing.com Send all info to woodwing support: System information. OS, PHP version, database type Prerequisites & Scenario Logfiles Severity of the issue (reseller guide)
Questions?
Questions? Thank you for your attention