Shared Container and Local Container
Moderators: chulett, rschirm, roy
Shared Container and Local Container
Difference between a shared container and a local container?
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
A shared container can be shared between jobs and is great for re-usability while a local container can only be used in the job in which it is created, it is useful for simplifying job design by breaking the job into different sections.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
-
- Participant
- Posts: 26
- Joined: Fri Apr 08, 2005 12:58 am
Re: Shared Container and Local Container
Hi Sriram ,
Shared containers help you to simplify your design but, unlike local containers, they are reusable by other jobs. You can use shared containers to make common job components available throughout the project. You can create a shared container from a stage and associated meta data and add the shared container to the palette to make this pre-configured stage available to other jobs.
You can also insert a server shared container into a parallel job as a way of making server job functionality available. For example, you could use it to give the parallel job access to the functionality of a plug-in stage. (Note that you can only use shared containers on SMP systems, not MPP or cluster systems.)
The main purpose of using a DataStage local container is to simplify a complex design visually to make it easier to understand in the Diagram window. If the DataStage job has lots of stages and links, it may be easier to create additional containers to describe a particular sequence of steps. Containers are linked to other stages or containers in the job by input and output stages.
You can create a local container from scratch, or place a set of existing stages and links within a container. A local container is only accessible to the job in which it is created
I hope this will shed some light
Shared containers help you to simplify your design but, unlike local containers, they are reusable by other jobs. You can use shared containers to make common job components available throughout the project. You can create a shared container from a stage and associated meta data and add the shared container to the palette to make this pre-configured stage available to other jobs.
You can also insert a server shared container into a parallel job as a way of making server job functionality available. For example, you could use it to give the parallel job access to the functionality of a plug-in stage. (Note that you can only use shared containers on SMP systems, not MPP or cluster systems.)
The main purpose of using a DataStage local container is to simplify a complex design visually to make it easier to understand in the Diagram window. If the DataStage job has lots of stages and links, it may be easier to create additional containers to describe a particular sequence of steps. Containers are linked to other stages or containers in the job by input and output stages.
You can create a local container from scratch, or place a set of existing stages and links within a container. A local container is only accessible to the job in which it is created
I hope this will shed some light