Not able to create New Scenarios and Scenario Templates - Button is disbled

-
How to enable the scenario buttons in ACC ?
Normally Scenarios are not enabled by default in ATG,You need to do a small tweak here to start working with Scenarios,Scenario Templates.

There are basically two places you need to do change before working with scenarios 

Database changes

Use any client tool(toad or sqlplus or heidisql for this)to connect your database,find the table dss_server_id and modify the value like below.










Note - Your server_id is the computer name,to find it,go to
MyComputer->Properties->Computer name,and the port is the drp_prt,
to find it go to atg component administration view
navigate to /atg/dynamo/server/DrpServer -> port,ideally it should be
8850,unless specified other wise.

Local Config Changes

Create a file scenarioManager.xml inside the folder
C:\ATG\ATGXXX\home\localconfig\atg\scenario
Add the entry like below and restart your server.






Go to ATG Control Center and you can now able to create/edit and delete your Scenarios,ScenarioTemplates etc.

atg.workflow.WorkflowException: The project type named /Content Administration/import.wdl is invalid.

This is also a similiar issue where the current Process Editor Server is configured or registered with the first Server, So you need to edit this in workflowProcessManager.xml file which would be located in the path \config\atg\epub\workflow\process\workflowProcessManager.xml.Otherwise create it under localconfig\
\atg\epub\workflow\process\workflowProcessManager.xml.

 
OR  there is an alternate solution.

1. Run the query select * from epub_wf_server_id; 
   in publishing schema which will give you the registered process  
   editor server name and port.
2. Update the epub_wf_server_id table with the actual hostname 
   and drp port.
3. Update epub_wf_server_id set SERVER_ID='Sebastian-
   HP:8851' where SERVER_ID='hostname:8851'
4. Restart BCC server.
 

Also see the below topics

Scenario Internal Working

Comments

Post a Comment

Popular posts from this blog

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more