cancel
Showing results for 
Search instead for 
Did you mean: 

BI 4.2 Promotion Managment LCMSchedulingService

former_member596274
Discoverer
0 Kudos

We have BI 4.2 installed in AWS. The dev and QA environments are installed in the non-PROD Virtual Private Cloud (VPC) and the Prod environment is installed in the PROD VPC. To promote objects to PROD from QA a VPC-peering connection has been opened and ports 6400-6499 are allowed through. The APS for Promotion Management, Adaptive Job Server, Input File Server and Output File Server all have their ports hard coded in the CMC as well as the CMC server as well. The ports match between prod and qa for their respective servers.

When on PROD, pulling objects from QA, the process takes less than a munute. Pushing from QA to PROD takes 30-40 minutes. Looking at WireShark captures while the promotion is running is showing attempted communications between prod and QA over five diget ports like the ports were auto selected. Tracing the port to a pid I have found the culprit to be

"D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/win64_x64/sapjvm/jre/bin//java.exe" -server "-Dcom.sap.vm.tag=AWSAPAPPWQ01.AdaptiveJobServer.LCMSchedulingService.CHILD0" "-Dbobj.enterprise.home=D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/" "-Dbusinessobjects.logging.path=D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging/" "-Ddestination.dll.path=D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/win64_x64/" "-Ddestination.wrapper.path=D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/win64_x64/DestinationWrapper.dll" -Djava.net.preferIPv4Stack=false -Xmx1024m -Xrs "-Xloggc:D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging//jobserver_AWSAPAPPWQ01.AdaptiveJobServer_LCMSchedulingService_CHILD0_gc.log" -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:LogGcMaxFileCount=3 -XX:LogGcMaxFileSize=5m -XX:+ExitVMOnOutOfMemoryError "-XtraceFile=D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging//jobserver_AWSAPAPPWQ01.AdaptiveJobServer_LCMSchedulingService_CHILD0_jvm_@PID.log" "-XX:ErrorFile=D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging/jobserver_AWSAPAPPWQ01.AdaptiveJobServer_LCMSchedulingService_CHILD0_dump_@PID.log" "-XX:GCHistoryFilename=D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging//jobserver_AWSAPAPPWQ01.AdaptiveJobServer_LCMSchedulingService_CHILD0_gc.prf" -XX:+HeapDumpOnOutOfMemoryError "-XX:HeapDumpPath=D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging/" "-Dbusinessobjects.connectivity.directory=D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0//dataAccess/connectionServer" "-Dcom.businessobjects.mds.cs.ImplementationID=csEX" "-Djava.awt.headless=true" "-XX:MaxMetaspaceSize=192m" "-Djava.security.auth.login.config=C:/Windows/bscLogin.conf" "-Djava.security.krb5.conf=C:/Windows/krb5.ini" -classpath "D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/java/lib//JobServerChild.jar" com.businessobjects.js.child.JobServerChild -cmdLine cmdLine=%22D%3A%2FProgram+Files+%28x86%29%2FSAP+BusinessObjects%2FSAP+BusinessObjects+Enterprise+XI+4.0%2Fwin64_x64%2Fsapjvm%2Fjre%2Fbin%2F%2Fjava.exe%22+%2Djavaargs+%22Dbusinessobjects.connectivity.directory%3DD%3A%2FProgram+Files+%28x86%29%2FSAP+BusinessObjects%2FSAP+BusinessObjects+Enterprise+XI+4.0%2F%2FdataAccess%2FconnectionServer%2CDcom.businessobjects.mds.cs.ImplementationID%3DcsEX%2CDjava.awt.headless%3Dtrue%2CXX%3AMaxMetaspaceSize%3D192m%2CDjava.security.auth.login.config%3DC%3A%2FWindows%2FbscLogin.conf%2CDjava.security.krb5.conf%3DC%3A%2FWindows%2Fkrb5.ini%22+%2DloggingPath+%22D%3A%2FProgram+Files+%28x86%29%2FSAP+BusinessObjects%2FSAP+BusinessObjects+Enterprise+XI+4.0%2Flogging%2F%22+%2DmaxDesktops+0+%2DjsTypeDescription+%22Crystal+Reports+Job+Server%22+%2DobjectType+CrystalEnterprise.Report+%2Drequestport+6425+%2Dfg+%2Drestart+%2Dpidfile+%22D%3A%2FProgram+Files+%28x86%29%2FSAP+BusinessObjects%2FSAP+BusinessObjects+Enterprise+XI+4.0%2Fserverpids%2FAWSAPAPPWQ01_AWSAPAPPWQ01.AdaptiveJobServer.pid%22+%2Dfips+%2Dns+AWSAPAPPWQ02.XXXXXXTEST.COM%3A6400+%2Dname+AWSAPAPPWQ01.AdaptiveJobServer+%2Ddir+%22D%3A%5CProgram+Files+%28x86%29%5CSAP+BusinessObjects%5CSAP+BusinessObjects+Enterprise+XI+4.0%5CData%5CprocSched%5CAWSAPAPPWQ01.AdaptiveJobServer%22+%2Durlfile -type mixedproc -parentIOR IOR:010000001b00000049444c3a506172656e744368696c642f506172656e743a312e30000001000000000000009e000000010101001c0000004157534150415050575130312e524a52415753544553542e434f4d001919730020000000000000008ea8cb5bd841040000000000a359d191b96932c62e9ba2903af06ec102000000010000001400000001003200010001000000000000010100000000000300000028000000015753411c0000004157534150415050575130312e524a52415753544553542e434f4d00191906000200 -lib com.businessobjects.lcm.processingsubsystem.LCMSubsystemFactory -requestPort 1119 -childPID CHILD94

Can anyone point me in the direction of where to specify the ports for this process?

I am not seeing the same issue when pulling objects from QA to PROD

Accepted Solutions (0)

Answers (5)

Answers (5)

dafang_zhang
Explorer
0 Kudos

Hi holderp, knowing that it's a pretty old thread, but wondering if you've found a solution passing parameters to the child process spawn from the AJS?

former_member596274
Discoverer
0 Kudos

The Promotion Job is going through but I believe it is being slowed down by a process on QA trying to communicate to PROD using auto assigned ports. All of the servers that LCM uses have static ports but there is a process that is auto-assigning ports that are not opened in the firewall. I cannot open the ports on the firewall as these auto-assign ports change.

  • CMS - 6401
  • IFR - 6435
  • OFR - 6436
  • APS LMS - 6419
  • AJS Promotion Mgmt - 6425
former_member596274
Discoverer
0 Kudos

Yes I have. These were done at the install.

I did find the Adaptive Job Server on QA is not using port 6425 even though it has been configured to do so and has been stopped and restarted.

Since I discovered this I selected Auto assign saved and restarted. Went back in and selected 6425 saved and restarted. Same result. It is trying to communicate with prod as if Auto assign is selected.

former_member596274
Discoverer
0 Kudos

This has been done already.

Server QA PROD CMS 6401 6401 IFR 6435 6435 OFR 6436 6436 APS LMS 6419 6419 AJS PROMOTION MGMT 6425 6425

AdaptiveJobServer.LCMSchedulingService.CHILD0 seems to be selecting its own port

amitrathi239
Active Contributor
0 Kudos

have you update the ports in production also?

amitrathi239
Active Contributor
0 Kudos

Assign dedicated ports between 6400-6499 on below servers in both envirnemnts and check after restarting the servers.

  • Central Management Server
  • Input File Repository server
  • Output File Repository Server
  • Adaptive Processing Server (listed under Lifecycle Management Services)