ScenarioManager & WorkFlowManager startup errors


While starting weblogic server, following exceptions thrown with "unknown protocol: dynamosystemresource" while starting ScenarioManger:

 Error stack trace:

 **** info       Mon Jul 31 09:22:43 EDT 2017    1501507363023   /atg/scenario/XrefParserManager XrefParserManager startup complete
**** Error      Mon Jul 31 09:22:43 EDT 2017    1501507363708   /       Unable to start service "/atg/scenario/ScenarioManager": atg.nucleus.ServiceException: The configuration file XMLFile(/atg/scenario/scenarioManager.xml) could not be read: java.net.MalformedURLException: unknown protocol: dynamosystemresource

**** Error      Mon Jul 31 09:22:44 EDT 2017    1501507364054   /       Unable to set configured property "/com/tap/commerce/pricing/ShippingChargeManager.defaultShippingOptions" atg.nucleus.ConfigurationException: Unable to resolve component /sparkred/paypal/PayPalProcessor.defaultShippingOptions 
**** Error      Mon Jul 31 09:22:47 EDT 2017    1501507367908   /       Unable to start service "/atg/scenario/InternalScenarioManager": atg.nucleus.ServiceException: The configuration file XMLFile(/atg/scenario/internalScenarioManager.xml) could not be read: java.net.MalformedURLException: unknown protocol: dynamosystemresource
**** Error      Mon Jul 31 09:22:48 EDT 2017    1501507368112   /       Unable to start service "/atg/epub/workflow/process/WorkflowProcessManager": atg.nucleus.ServiceException: The configuration file XMLFile(/atg/epub/workflow/process/workflowProcessManager.xml) could not be read: java.net.MalformedURLException: unknown protocol: dynamosystemresource
**** Error      Mon Jul 31 09:22:48 EDT 2017    1501507368191   /atg/scenario/ScenarioManager   Unable to combine messaging information from the process manager component /atg/scenario/ScenarioManager. The process manager has not been classified yet so it cannot be determined if global messages should be listened for. This error indicates a problem with component startup order - the /atg/scenario/ScenarioManager component has been started before the /atg/dynamo/messaging/MessagingManager component
**** Error      Mon Jul 31 09:22:48 EDT 2017    1501507368191   /atg/scenario/InternalScenarioManager   Unable to combine messaging information from the process manager component /atg/scenario/InternalScenarioManager. The process manager has not been classified yet so it cannot be determined if global messages should be listened for. This error indicates a problem with component startup order - the /atg/scenario/InternalScenarioManager component has been started before the /atg/dynamo/messaging/MessagingManager component
**** Error      Mon Jul 31 09:22:48 EDT 2017    1501507368192   /atg/epub/workflow/process/WorkflowProcessManager       Unable to combine messaging information from the process manager component /atg/epub/workflow/process/WorkflowProcessManager. The process manager has not been classified yet so it cannot be determined if global messages should be listened for. This error indicates a problem with component startup order - the /atg/epub/workflow/process/WorkflowProcessManager component has been started before the /atg/dynamo/messaging/MessagingManager component

**** Error      Mon Jul 31 09:22:48 EDT 2017    1501507368208   /atg/dynamo/messaging/MessagingManager  An exception occurred while trying to parse XML definition file "XMLFile(/atg/dynamo/messaging/dynamoMessagingSystem.xml)"      java.net.MalformedURLException: unknown protocol: dynamosystemresource

Solution:

 Make sure protocol.jar has been added to CLASSPATH and lib directory of weblogic managed servers and domain respectively.

 - Copy $DYNAMO_ROOT/DAS/lib/protocol.jar file to weblogic domain lib directory $WL_HOME/user_projects/domains/<YOUR_DOMAIN>/lib/protocol.jar

 - Make sure ATG Managed server (Instance) startup script in weblogic console tab has CLASSPATH set for protocol.jar (specify the location of the protocol.jar file)

 - Restart all ATG Managed servers to reflect the chnages

 - Verify server logs for SscenarioManager component startup

 Example:

 **** info       Mon Jul 31 10:26:43 EDT 2017    1501511203083   /atg/scenario/XrefParserManager XrefParserManager startup complete

**** info       Mon Jul 31 10:26:43 EDT 2017    1501511203939   /atg/scenario/ScenarioManager   Initializing Process Editor Server myserver.domain.com:8050

Comments

Post a Comment

Popular posts from this blog

Weblogic 12c & Apache 2.4 troubleshooting

Error -   libonssys.so: cannot open shared object file : httpd: Syntax error on line 355 of /etc/httpd/conf/httpd.conf: Syntax error on line 1 of /data/apps/apache2/conf.d/vhost.conf: Cannot load /etc/httpd/modules/mod_wl_24.so into server: libonssys.so: cannot open shared object file: No such file or directory Solution: 1) Copy all supported  Download Oracle WebLogic Web Server Plug-Ins 12c from Oracle website : http://www.oracle.com/technetwork/middleware/webtier/downloads/index-jsp-156711.html Extract the downloaded archive and find (correct file according to your architecture) mod_wl_24.so (This is for Apache2.4.x) & libonssys.so & libonsssl.so & libdms2.so copy into /etc/httpd/modules/ folder. 2) Set the  LD_LIBRARY_PATH inside the  /etc/sysconfig/httpd file.  echo $ LD_LIBRARY_PATH first and copy paste the same in httpd file along with  /etc/httpd/modules location. Example in my case: File:  /etc/syscon...
Read more

Enabling WL-Proxy-SSL HTTP header in WebLogic

Scenario : Weblogic server will be always behind the LoadBalancer or Apache layer. Most of the time the SSL's will be either offloaded in LoadBalancer or Apache layer.  To construct applicaitons URL's with the right protocol will be a challenge while using weblogic as application server.  To achieve this scenario we have to enable  WL-Proxy-SSL and WebLogic Plug-In Enabled. Solution: - Update the LoadBalancer configurations/iRules to set the RequestHeader WL-Proxy-SSL to  true . - Follow the below steps to set the WebLogic 'Plugin Enabled' flag to Yes. (Following steps are based on the weblogic version 12.1.2)    - Login into weblogic console    - Click on Lock & Edit button     - Click on the domain name    - Under Configurations tab go to "Web Applications" sub tab    - Select the check box "WebLogic Plugin Enabled" and click "save" button    - Finally click on "Activate C...
Read more