Hello,

I 'am evaluating the new SAP CPS Version: SAP 7.00 Build: M26.17-31458. Now I try to create jobs by using a precondition and the redwood expression language. The administration guide is not very useful, so I hope some of you have a few examples.

Here an example I would do:

A precondtion shoud check the the starttime of the chain. If the starttime < 08:00pm the returncode should be false.

Also I tried to understand substitution parameters, there is no useful example in the guid. Perhaps one of you can explain how to use them.

Thanks in advance!

Kind regards

Marc

Hi All,

I successfully upgraded the CPS component from SP12 (M28.51) to SP14(M33.73) on Solution Manager system(NetWeaver 7.02) via JSPM.

The component info is updated. But when I open the <host>:<port>/scheduler/ui, it says Startup Failure. How to solve this problem?

Default trace:

Error registering event listener [EXCEPTION] JCS-107002: Component manager currently unavailable.

JCS-107002: Component manager currently unavailable.

I found another discussion with the same error and someone said this is fixed in M33.59.

But in the information for installation package of SP14, it says it is M33.73.

Since the user I used is an administrator user, I haven't assigned the roles mentioned in document yet. But I can access CPS by this user before upgrading. I think it's not the problem.

Best Regards,

String

Hello,

I had recently upgraded SAP version from 7.01 to 7.3 sps 07 including M33.58 CPS component . ( Older CPS component was M28.44).

Upgrade happened successfully .. JavA engine come up fine.. all the component are upgraded fine.. Did not have any issues during upgrade.

-All the scheduler components are green in Applications area in Java NWA page.

Now when i launch scheduler page . Scheduler link opens with a message on screen as "" Startup Failure """ .

Default Trace file has following enteries:

#2.0 #2012 05 25 19:47:30:821#+00#Error#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C00099589C28008C0000000000005A36#477974450000000004#redwood.com/scheduler-ear#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#Guest#0##9AD15FADA6A111E1BDA500001C7D4FB2#76e11dd3a6a211e1aaf900001c7d4fb2#76e11dd3a6a211e1aaf900001c7d4fb2#0#Thread[HTTP Worker [@1380431624],5,Dedicated_Application_Thread]#Plain##

Error registering event listener JCS-107002: Component manager currently unavailable#

#2.0 #2012 05 25 19:47:30:822#+00#Error#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#

Error registering event listener JCS-107002: Component manager currently unavailable#XX-PART-REDWOOD#redwood.com/scheduler-ear#C00099589C28008C0000000200005A36#477974450000000004#redwood.com/scheduler-ear#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#Guest#0##9AD15FADA6A111E1BDA500001C7D4FB2#76e11dd3a6a211e1aaf900001c7d4fb2#76e11dd3a6a211e1aaf900001c7d4fb2#0#Thread[HTTP Worker [@1380431624],5,Dedicated_Application_Thread]#Plain##

Error registering event listener JCS-107002: Component manager currently unavailable#

#2.0 #2012 05 25 19:47:30:831#+00#Error#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#

JCS-MULTI: Multiple errors occurred#XX-PART-REDWOOD#redwood.com/scheduler-ear#C00099589C28008C0000000400005A36#477974450000000004#redwood.com/scheduler-ear#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#Guest#0##9AD15FADA6A111E1BDA500001C7D4FB2#76e11dd3a6a211e1aaf900001c7d4fb2#76e11dd3a6a211e1aaf900001c7d4fb2#0#Thread[HTTP Worker [@1380431624],5,Dedicated_Application_Thread]#Plain##

JCS-MULTI: Multiple errors occurred#

#2.0 #2012 05 25 19:47:30:831#+00#Error#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C00099589C28008C0000000500005A36#477974450000000004#redwood.com/scheduler-ear#com.redwood.scheduler.module.helper.ForwardingModuleEventListener#Guest#0##9AD15FADA6A111E1BDA500001C7D4FB2#76e11dd3a6a211e1aaf900001c7d4fb2#76e11dd3a6a211e1aaf900001c7d4fb2#0#Thread[HTTP Worker [@1380431624],5,Dedicated_Application_Thread]#Plain##

Error registering event listener

[EXCEPTION]

JCS-107002: Component manager currently unavailable

    at com.redwood.scheduler.lifecycle.api.ComponentManagerLocator.lookupComponentManager(ComponentManagerLocator.java:58)

    at com.redwood.scheduler.module.helper.ForwardingModuleEventListener.registerEventListener(ForwardingModuleEventListener.java:55)

    at com.redwood.scheduler.module.impl.ModuleFilter.doFilter(ModuleFilter.java:123)

    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

    at com.redwood.scheduler.security.filter.SecurityFilter.doFilter(SecurityFilter.java:621)

    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

    at com.redwood.scheduler.servlet.RequestCharsetFilter.doFilter(RequestCharsetFilter.java:197)

    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: JCS-112012: Cannot execute epoch initializer: com.redwood.scheduler.db.epoch.m30.M30Initializer

    at com.redwood.scheduler.db.DatabaseInitializer.initializeEpochs(DatabaseInitializer.java:670)

    at com.redwood.scheduler.db.DatabaseInitializer.initializeDatabase(DatabaseInitializer.java:381)

    at com.redwood.scheduler.db.DatabaseInitializer.start(DatabaseInitializer.java:210)

    at com.redwood.scheduler.lifecycle.impl.StartComponentVisitor.visit(StartComponentVisitor.java:34)

    at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.visitAllComponents(DefaultComponentLifecycleManager.java:106)

    at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.startComponents(DefaultComponentLifecycleManager.java:207)

    at com.redwood.scheduler.lifecycle.impl.DefaultComponentLifecycleManager.startComponents(DefaultComponentLifecycleManager.java:166)

    at com.redwood.scheduler.lifecycle.impl.DefaultStartup.start(DefaultStartup.java:146)

    at com.redwood.scheduler.lifecycle.impl.DefaultStartup$1.run(DefaultStartup.java:128)

    at java.lang.Thread.run(Thread.java:722)

Caused by: JCS-122035: Unable to persist: JCS-MULTI: Modification vetoed: JCS-XXXXX: Modification vetoed: Conflict propagating to job group, recurrence job attribute: Priority

    at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:907)

    at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSessionImpl.java:848)

    at com.redwood.scheduler.db.DatabaseInitializer.initializeEpochs(DatabaseInitializer.java:665)

    ... 9 more

Caused by: com.redwood.scheduler.persistence.impl.MultipleCauseException: JCS-MULTI: Modification vetoed: JCS-XXXXX: Modification vetoed: Conflict propagating to job group, recurrence job attribute: Priority

    at com.redwood.scheduler.persistence.impl.PersistenceListenerContextImpl.throwException(PersistenceListenerContextImpl.java:194)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectListRetry(LowLevelPersistenceImpl.java:254)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access$0(LowLevelPersistenceImpl.java:164)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteDirtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103)

    at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkManager.execute(OuterPersistenceUnitOfWorkManager.java:38)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectList(LowLevelPersistenceImpl.java:160)

    at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistence.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90)

    at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:886)

    ... 11 more

Caused by: com.redwood.scheduler.persistence.api.PersistenceException$ModelModificationVetoException: JCS-XXXXX: Modification vetoed: Conflict propagating to job group, recurrence job attribute: Priority

    at com.redwood.scheduler.model.method.impl.JobMethodImpl.copyRecurrenceFields(JobMethodImpl.java:621)

    at com.redwood.scheduler.model.method.impl.JobMethodImpl.preparePhaseHandler(JobMethodImpl.java:526)

    at com.redwood.scheduler.model.BaseSchedulerEntityImpl.preparePhaseHandler(BaseSchedulerEntityImpl.java:927)

    at com.redwood.scheduler.model.listeners.ConstraintCheckPrepareListener.modelModified(ConstraintCheckPrepareListener.java:48)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.informListeners(LowLevelPersistenceImpl.java:970)

    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectListRetry(LowLevelPersistenceImpl.java:245)

    ... 17 more

I am not sure if any one has tried upgrade like this.. All i know is we can deploy CPS file/patchs/new versions  via JSPM. But what exactly takes place when we do SAP Version upgrade to 7.3 including CPS component upgrade????

There is no spcefic note yet released which i could find out..

Please help me out/??

Thanks

Best Regards

Deepak Shamra

Hi,

We have two Non SAP process servers which are installed via Platform agent for Eg: (T01 & T02) are mapped to one queue.

When the job is scheduled to run in that queue, It runs either for T01 or T02 Process server.

When job is trigerred to run for T02 Process server, its connects to backend server and runs fine but the same job is triggered to run for T01 Process server, job failing with error message " "No Password supplied for OS account {virtual}vuser_XXX".

Even all the credentials maintained for vuser and back-end server is correct.

And even when we check in default trace of our CPS system we found the below error

"Process server for Queue Provider 443250 cannot be read, ignoring QueueProvider#"

"704#+0530#Error#com.redwood.scheduler.ui.theme.ResourceServlet#

Unable to find /black/javascript/clear.cache.gif#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000A421619F1A60000000200001420#2767150000000004#redwood.com/scheduler-ear#com.redwood.scheduler.ui.theme.ResourceServlet"

which we are not sure what exactly it means.

Kindly help us understanding the issue.

Thanks,

Shwetha Houde

Hi :

           I am getting the following error(screen shot attached) "404 Not Found"  Error: Cannot define forward location.

Error occurs on our new version of Sap cps version M33.116-80989.

This error never occurred on the old sap cps version M33.85-65736

I get the redwood logon screen, but after entering the userid and password I get this error.

Can anyone help on this ?

Patrick Donnelly

patrick.donnelly@agr.gc.ca

Hi All,

Can anyone help me in providing the steps of Migrating Control-M to Redwood CPS.

Thanks,

Peeyush

Hi All,

Whenever we try to restart only the failed processes of a process chain which is in Console state, CPS job is getting failed with the below error message. But the failed processes are restarted and successful in the BW system. Please help.

An error has occurred in the SAP connector: JCS-122035: Unable to persist: JCS-102200: Job 108708 (submitted from SAP_CcmsJob copy from 2015/02/26 13:54:24,218 America/New_York) already exists
Details:
JCS-122035: Unable to persist: JCS-102200: Job 108708 (submitted from SAP_CcmsJob copy from 2015/02/26 13:54:24,218 America/New_York) already exists
at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:941)
at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSessionImpl.java:882)
at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWorkManager.java:3)
at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWorkManager.java:43)
at com.redwood.scheduler.connector.sap.rfc.job.bw.restart.ProcessChainRestart.restart(ProcessChainRestart.java:326)
at com.redwood.scheduler.connector.sap.rfc.service.operation.OperatorReplyOperation.doWork(OperatorReplyOperation.java:63)
at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:38)
at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:76)
at java.lang.Thread.run(Thread.java:763)
Caused by: com.redwood.scheduler.model.exception.UniqueConstraintViolatedException: JCS-102200: Job 108708 (submitted from SAP_CcmsJob copy from 2015/02/26 13:54:24,218 America/New_York) already exists
at com.redwood.scheduler.model.ModelSQLExceptionMappingImpl.wrapUniqueConstraintViolatedException(ModelSQLExceptionMappingImpl.java:29)
at com.redwood.scheduler.persistence.helper.OracleSQLExceptionWrapper.wrapSQLException(OracleSQLExceptionWrapper.java:39)
at com.redwood.scheduler.persistence.helper.SAPSQLExceptionWrapper.wrapSQLException(SAPSQLExceptionWrapper.java:55)
at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper.wrapSQLException(RecoverySQLExceptionWrapper.java:51)
at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkManager.rethrowException(OuterPersistenceUnitOfWorkManager.java:91)
at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkManager.execute(OuterPersistenceUnitOfWorkManager.java:43)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectList(LowLevelPersistenceImpl.java:160)
at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistence.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90)
at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:920)
... 8 more
Caused by: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR3DB.JCS_JOB0B) violated

OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLExceptionFactory.java:125)
at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQLExceptionFactory.java:72)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJava6(DirectPooledConnection.java:1000)
at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(DirectPooledConnection.java:926)
at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectConnection.java:1544)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:376)
at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:354)
at com.sap.sql.jdbc.common.CommonPreparedStatement.execute(CommonPreparedStatement.java:867)
at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.execute(PreparedStatementWrapper.java:360)
at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.execute(PreparedStatementImpl.java:432)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.populateAndExecute(LowLevelPersistenceImpl.java:906)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.processModificationIfPossible(LowLevelPersistenceImpl.java:701)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectListRetry(LowLevelPersistenceImpl.java:292)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access$0(LowLevelPersistenceImpl.java:164)
at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteDirtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103)
at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkManager.execute(OuterPersistenceUnitOfWorkManager.java:38)
... 11 more
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR3DB.JCS_JOB0B) violated

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1046)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3613)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3694)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1354)
at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPreparedStatement.java:108)
at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Oracle11gPreparedStatement.java:167)
at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:373)

Regards,

Lohit

Hi all,

Has anyone seen similar to this?

A SAP system connection that

a) in the SAP system definition is AOK - system connect string and XBP connection both test AOK

b) BUT the Process Server will be unreliable - one of three things is likely to happen at startup

     i - starts up AOK

   ii -- starting up very slowly

    iii- fails to startup at all

Security traces reveal nothing, It seems to be something else.

There are no useful Op Messages in CPS.

In the NetWeaver AS Java server node logs we see something like this recurring - we are not certain if it is directly linked:

#2.#2013 09 30 12:44:08:622#+00#Warning#com.sap.engine.core.thread.ShmThreadLoggerImpl#
#BC-JAS-COR#kernel.sda#C0008F166847374F00000000000037BE##redwood.com/scheduler-ear#com.sap.engine.core.thread.ShmThreadLoggerImpl#deploy_service#0##6D7C74DA212C11E3A2B400000168884A##6d7c74da212c11e3a2b400000168884a#0#Thread[Redwood monitoring for SAP instance SS_<SID>.<SID> worker 1,5,Redwood monitoring for SAP instance SS_<SID>.<SID> workers]#Plain##
The predefined size of the shared memory monitoring slots for the thread system is reached: size[600], used[600], type[thread table]. Every thread started from now on will be fully functional but will not be visible in the MMC thread monitoring. You need to reconfigure the shared memory monitoring slots for threads.#


We're still testing to see if there are other logged symptoms that directly relate but so far this is inconclusive.

Hi Folks,

We have a production CPS system with 5000+ jobs running.

We are on Version 8.0

Build Id: M33.92-68971

Database Driver Version: Microsoft SQL Server JDBC Driver 3.0 3.0.1301.101

RAM = 32 GB

Cluster on Server0

Java version=1.6.0_51

OS=Windows Server 2008 R2

Memory info:

totalMemory: 4116054016

freeMemory : 1752108128

maxMemory  : 4116054016

Below are few concerns pertaining to our present landscape.

• Jobs are not maintaining the keep clause.
• We are told not to delete any previous jobs ( as per client )
• Garbage Collector values for optimization.
• Governance is not maintained.
• Attached is the app server info

This are the main aspects of the present issues, which we are facing. Can you please throw some inputs on how to overcome.

What is the right approach on stabilizing the system with stable performance?

Thanks.

Hi All,

I have been trying to send a text with multiple lines in this way

This is the first line <CR>

This is the second line

[Headers]

I have used as carriage return <CR>, <BR>, /n but without success.

Any idea?

Thanks in advance for your kind support.

Regards,

    Giovanni

Hi All,

Our Windows server drive is mounted on SAP Linux Box. We have few SAP files written directly on to the Linux box locally. Could you please provide the options to copy the files from Linux box to the window server.

Is the agent mandatory on any of the servers?

Thanks,

Chandu

Hey BPA community,

a few quick searches through the web, here and the official guides couldn't give me much information on this topic.

(Also just let me know if this question is substantially wrong and if so, feel free to explain why )

We did some tests on importing SAP CCMS jobs with the correct BPA process definition "SAP_ImportCCMSJobs". It did find the job I was looking for without problem, it showed the correct SAP job-number in the logs (stdout.log). But I wasn't able to find it anywhere. There was just no job definition created.

After quite some testing of different settings I finally arrived by trying out running the job and importing it afterwards.

It worked.

So is this the correct way of importing jobs? Only importing jobs which have already been run.

If so, I would love to understand the reasoning behind this. (I would guess BPA will know that the job can run in that way)

Feel free to link me to already existing information if its there, I couldn't find it

Benjamin

Hello All,

I am new to Rewood Cronacle. We are using Redwood Cronacle in SAP. Can any provide me the documentation of this software and also are there any training institutes in training this one. Thanks in advance.

Ram.

Dear all,

Is it possible to schedule a 40 Work Processes job to run on 2 SAP instances (DIA) only, while the SAP system has 6 SAP instances (CI + 5DIA).

We are using Control M  + CPS Redwood.

I suppose some RZ12/Logon groups or SM61 would be involved?  Or any concrete trick in CPS/ Control M?

Thanks in advance!

Marian

Hi All,

In the Job monitor, we are able to find the corresponding job by searching with the program or file name in the search job field. But we are not able to find the corresponding job definition when doing a search with the file name or program in the search job definition field.

Could you please help us the expression to find the corresponding job definition by providing the file name or program name in the search job definiton field.

Regards,

Tinku

Hi All,

This might be the simplest question but not sure how could I go forward with this.

I have 5k jobs in Job Def table and keep clause is not defined. System is up and running from past 4 years.

I want to get the list of Jobs that were defined but not ran never.

```

select jd.* from JobDefinition jd where jd.UniqueId not in (select j.JobDefinition from Job j);

```

The above query gives the list of jobs in job def but not in job. The problem is server is timing out due to humongous size of Job table. Please suggest some optimal solution to get the results.

Many thanks in advance.

Hi Folks,

We have a production CPS system with 5000+ jobs running. We have some performance issue related to Garbage Colelctor Values, below is the system technical information.

We are on Version 8.0

Build Id: M33.92-68971

Database Driver Version: Microsoft SQL Server JDBC Driver 3.0 3.0.1301.101

RAM = 32 GB

Cluster on Server0

Java version=1.6.0_51

OS=Windows Server 2008 R2

Memory info:

totalMemory: 4116054016

freeMemory : 1752108128

maxMemory  : 4116054016

-XX:PermSize=1024m

-Xmx4096m

-XX:MaxNewSize=1365m

-XX:MaxPermSize=1024m

-Xms4096m

-XX:NewSize=1365m

-XX:+UseConcMarkSweepGC

-XX:TargetSurvivorRatio=90

-verbose:gc

-XX:+DumpDetailedClassStatisticOnOutOfMemory

-XX:+PrintGCDetails

-XX:MaxErrorQueueLength=200

-XX:+PrintGCTimeStamps

-XX:+DisableExplicitGC

-XX:SoftRefLRUPolicyMSPerMB=1

-XX:-StringInternTableInPermGen

-XX:SurvivorRatio=6

-Xss2m

-XX:+HeapDumpOnOutOfMemoryError

-XX:HeapDumpPath=OOM.hprof

-XX:-TraceClassUnloading

Can you please suggest the recommended changes and values which are need to be adopted for fine tuning the garbage collection in our landscape from above information?

Hi,

We need to move our redwood system from one SID to another SID. We did the homogeneous backup restore method. Could share any document which talks about the specific post system copy procedure in redwood scheduler UI.

Our intention is to clear old data and create new queue entry.

Regards

Pratheep S

How to schedule the Powershell script in Redwood?

Please let me know whoever tried this.

I am getting an error like ""ps1 cannot be loaded because the execution of s cripts is disabled on this system. Please see "get-help about_signing" for more details. "

Hi

I am curious to know if there are any documentation on scheduling BO Reports using the Redwood CPS.

We are looking to integrate the Reports in line with the completion of ETL Loads for Facts that way we deliver the data in just the perfect time.

Please provide with some start-up and I can pick it up from there.

Thank You

Ganesh Sampath