Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Pipeline process not visible in Adobe campaign process list

Avatar

Avatar
Ignite 1
Level 1
santanub4981128
Level 1

Like

1 like

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
Validate 1
Boost 1
View profile

Avatar
Ignite 1
Level 1
santanub4981128
Level 1

Like

1 like

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Ignite 1
Validate 1
Boost 1
View profile
santanub4981128
Level 1

16-09-2020

Hi,

 

We tried to enable pipeline process in Adobe campaign following below steps.

 

Steps:

  1. Install pipeline package 
  2. Install OpenSSL in server to create public/private keys
  3. Generate  public/private keys
  4. Register public key in Adobe Analytics
  5. Encrypt Private key using pipeline encrypted workflow
  6. Modify pipeline tag with AppName and privatekey in serverConf.xml
  7. Make sure imsorg id is defined in in serverConf.xml
  8. Modify pipeline tag with AppName and privatekey in instance config.xml
  9. Restart pipeline service using command-Nlserver start pipelined@<instanceName>

Pipeline service was running in CMD but when I logged in Adobe campaign instance I can't see pipeline process is listed in Process list . Can anybody let me know why pipeline process is not listed in Home->Monitoring->ProcessList?

 

processlist.JPG

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
wodnicki
MVP

Likes

960 likes

Total Posts

1,090 posts

Correct Reply

508 solutions
Top badges earned
Establish
Affirm 500
Contributor
Shape 1
Give Back 100
View profile

Avatar
Establish
MVP
wodnicki
MVP

Likes

960 likes

Total Posts

1,090 posts

Correct Reply

508 solutions
Top badges earned
Establish
Affirm 500
Contributor
Shape 1
Give Back 100
View profile
wodnicki
MVP

20-09-2020

Hi,

 

Set the <pipelined/> element to autostart="true" in your instance conf, then run `systemctl restart nlserver6`.

 

Thanks,

-Jon

Answers (0)