Clarification: Will both Development and Test use the same PWX Listener, or will you have both a Dev and a Test PWX Listener?
If the same PWX Listener for both, then everything should be OK.
If distinct PWX Listener for each environment, then you will need to migrate the capture registrations and extraction maps from the Dev PWX Listener to the Test PWX Listener.
Hi Dan, Thanks for the reply
Both Dev and Test will have their own PWX Listener (for PC server and Client machine), but both Dev and Test will source data changes from the same machine / same source PWX listener on database DB2 / AS400.
I think this should be ok, right ? so we don't need to migrate the extraction maps because it's already exist in the source server ?
OK, now I'm confused.
Why are you running a PWX Listener on the client machine?
PWX Listener on AS/400 is required.
PWX Listener somewhere else is only required if you are re-logging the DB2/400 data via PWXCCL.
I mean because the windows client machine will be on different on test environment.
And there we didn't have PWX installed yet. So i think we will need to install the PWX to talk with the Source AS/400 DB2.
Installing PWX and running PWX Listener are two different things.
You only need to run PWX Listener if you need it to do something on that box.
We need to install it to client machine for PowerCenter CDC session to work using changes data on PWX navigator extraction maps.
Server (maybe DB server, maybe dedicated PWX server, maybe PC Int. Svc. server)
- PWXCCL runs here
- PWX Listener runs here
- - This is where both PWX Navigator and PC sessions connect (LOCATION)
IF PWXCCL/PWX Listener aren't running on the PC Int. Svc. machine, then:
PC Int. Svc. server
- PWX installed here
- - PC session LOCATION points to the PWX Listener on the Server above.
- PWX Navigator runs here
- PC client tools run here
- - both of these point to the PWX Listener on the server
Yes Dan, that's what i mean. Sorry for confusing you.
So we are planning to promote to Test environment.
So we just need to install PWX to PC Integration Service machine and PWX navigator on PC Client machine.
And still using the same DB Server.
So can we just let the PC client on Dev environment still running the CDC workflow and also run the PC Client on Test environment that point to the same DB server as Dev one ?
Not-CDC Data flow is really
SomeSource -> PWX Listener -> PWXPC -> PC session memory
But is started by PC session talking to PWXPC, and asking it to get data from PWX Listener.
CDC Data Flow is really two disjoint processes:
SomeSource(redo logs, for example) -> PWX Capture -> PWX Logger -> PWX log files.
(This part normally runs continuously)
PWX Log Files -> PWX Listener -> PWXPC -> PC session memory
(this part is started by PC session talking to PWXPC, and asking it to get data from PWX Listener)
"Using the same DB server" is vague.
Where is PWX Listener running?
Will you have a distinct PWX Listener for each environment?
Is this CDC?
If so, where is PWXCCL running?
Will you have a distinct PWXCCL for each environment?
PWX Listener will be running on DB Server and Integration Service Server. PWX Navigator on PC client.
We have 1 DB Server (AS/400) with PWX Listener installed to use for Dev environment and Test environment.
Yes, this is CDC and we didn't use PWXCCL.
Why are you running a PWX Listener on the PC Int. Svc. node?
Are you doing something like FTP'ing files down to that box, and sourcing them from there?
we installed PWX on PC Int node for the connection to the source DB server (AS400). When we didn't set the node in dbmover.cfg file, it just won't work for CDC workflow.
PWX Listener only needs to run on boxes where you need to source data.
NODE statements in DBMOVER / DBMOVER.CFG point to PWX Listeners.
You need NODE statements on the PS Int. Svc. nodes, the box where PWX Navigator runs, the box where PC Clients run, etc.
That's what we do.