خواندن ۸ دقیقه·۶ سال پیش

Explain briefly DataStage containers

A container is used to group stages and connections, as its name suggests. Containers help simplify and modularize job designs for servers and allow you to replace complex diagram areas with a single container level. For example, if you have a lookup that is used by multiple jobs, you can place in a sharing container the jobs and links that create the lookup, and use it for different jobs. In the programming language, you can look at it in a way like a process or method.

Containers are linked by input and output stages to other stages or containers within the job. datastage online course for more techniques and skills from industrial experts.

Types of DataStage containers

There are two types of Containers.

Local containers

These are created in a local job in dataStage, and can only be accessed through that job. A local container is edited in the Diagram window of a task tabbed page. You can use the local containers in Server jobs, or work in parallel.

Shared containers

These are created separately and stored in the Repository just like jobs in DataStage. There are two shared container types.

Shared container service

You may find this in application jobs and also in parallel activities as well.

Shared parallel container employed in parallel occupations.

In parallel jobs, you can also use shared application containers as a way of integrating cloud job features into a parallel stage.

Let us see about the features of local and shared containers.

Features of Local and shared containers

Local containers

Used primarily to ease the creation of the work.
You can combine pieces of logic and use them within a work.
Can only be used in a job once it has been developed.
Number of Local Containers assisted input and output connections.
On-the-job availability.Shared containers
Used for ease of job design as well as for sharing among workers.
Flexibility over the entire project.
The mapping of shared containers includes metadata.
Shared containers can be saved as standalone.
Job need to be repackaged once the shared container definition has changed.
Shared containers cannot be self-compiled.
If the code for shared containers is used within the job, it will be included in the code for the task.
Setting up local and shared containers in DataStageThe setup of local and shared containers are as follows.Local containerThe main purpose of using a local DataStage container is to visually simplify a complex design and make it easier to comprehend in the Diagram window. If there are lots of stages and connections in the DataStage job, it may be easier to create additional containers to represent a similar sequence of steps.
Do the following to construct a local container, from an established work design:
Press the Shift key and click on the steps you want to insert in the local container using the mouse.
Select Edit [Construct Container] Local from the menu bar. A new tab appears in the Diagram window which contains the contents of the new stage of the Local Container. You are warned if any disputes over the naming of ties arise when the container is installed. The new container is opened and shifts focus to its tab.As with any other stage in your job design, you can rename, move, and delete a container stage.
To display or change a local container in the Diagram window, simply double-click on the container stage. In a folder, you can edit the stages and links just the way you do for a work.
Drag and drop the Container icon in the General group on the tool palette to the Diagram window to build an empty container into which you can add stages and ties.In the Diagram window, a container stage is added, double-click on the stage to open it, and add stages and links to the container the same way you do for a job.Use of Local container Input and Output StagesPhases of input and output are used to describe the stages of the main job the container is connected to. datastage administrator training helps you to learn more effectively.If you are building a local container from an existing group of stages and links, the input and output stages will be added automatically.
The connection between the input or output stage and the container stage has the same name as the link in the Diagram window for the main job.In the example above the input link is the link from the Oracle OCI stage (oracle oci 0) of the main job connecting to the container. The output link is the connection that connects from the first container to the second.If you create a new container, the input and output stages will be placed in a container with no link.
You need to add stages between the input and output stages to the container Diagram window. Link the stages together, and edit the names of the links to match those in the main window.You can have any number of links in and out of a local container, in the job all the link names inside the container must match the link names within and outside it. Editing metadata on either side of the container edits the meta data on the connected stage in the job once a connection is established.
Shared ContainerShared containers also help you simplify the design but are reusable by other jobs unlike local containers. Shared containers can be used to make work components accessible in the project.Shared containers comprise groups of stages and connections, and are stored like DataStage jobs in the Repository. DataStage positions an instance of that container in the design when you insert a shared container into a job. When compiling the job which contains an instance of a shared container, the container code is included in the compiled job.
The DataStage debugger can be used on instances of shared containers that are used within jobs.You can create a shared container from scratch, or bring into a shared container a set of existing stages and links.Create a shared container out of the current job design.Press Shift and then press on the other stages and links to connect to the jar.
Select Edit [Construct Container] Shared from the menu bar. You will be asked via the Build New dialog box for a name for the container. The community is replaced with a Shared Container stage of the same sort in the Diagram window with the specified name.
Any parameters which occur in the components are copied as container parameters into the shared container. The generated instance has assigned all of its parameters to corresponding job parameters.Modify or display a Shared ContainerSelect File ->Open from the menu bar, then select Shared Folder to open. You can also highlight the Shared Container, right-click on the mouse and pick the address.Using a shared container
Drag a Shared Container icon in the Repository window from the Shared Container branch to the Diagram window of the job.
Update Tabs for Input and Output.Container Map ConnectionChoose the connection within the shared container to which you will map the incoming job link. You need to change the link to cause a validation process. Then you will be alerted if the metadata does not match and the meta data reconciliation option is provided as mentioned below.The Container ColumnsColumns page displays the metadata identified in a standard grid for the connection to the job point. In the Load Shared Containers button, you can use the Reconcile option to overwrite metadata on the job stage link with the container link meta data in the same way as defined for the Validate option.Conclusion:I hope you reach a conclusion about containers in DataStage. You can learn more about DataStage containers from DataStage online training.

snehacynixit

شاید از این پست‌ها خوشتان بیاید

snehacynixit

خواندن ۸ دقیقه·۶ سال پیش

Explain briefly DataStage containers

Containers are linked by input and output stages to other stages or containers within the job. datastage online course for more techniques and skills from industrial experts.

Types of DataStage containers

There are two types of Containers.

Local containers

Shared containers

These are created separately and stored in the Repository just like jobs in DataStage. There are two shared container types.

Shared container service

You may find this in application jobs and also in parallel activities as well.

Shared parallel container employed in parallel occupations.

In parallel jobs, you can also use shared application containers as a way of integrating cloud job features into a parallel stage.

Let us see about the features of local and shared containers.

Features of Local and shared containers

Local containers

Used primarily to ease the creation of the work.
You can combine pieces of logic and use them within a work.
Can only be used in a job once it has been developed.
Number of Local Containers assisted input and output connections.
On-the-job availability.Shared containers
Used for ease of job design as well as for sharing among workers.
Flexibility over the entire project.
The mapping of shared containers includes metadata.
Shared containers can be saved as standalone.
Job need to be repackaged once the shared container definition has changed.
Shared containers cannot be self-compiled.
If the code for shared containers is used within the job, it will be included in the code for the task.
Setting up local and shared containers in DataStageThe setup of local and shared containers are as follows.Local containerThe main purpose of using a local DataStage container is to visually simplify a complex design and make it easier to comprehend in the Diagram window. If there are lots of stages and connections in the DataStage job, it may be easier to create additional containers to represent a similar sequence of steps.
Do the following to construct a local container, from an established work design:
Press the Shift key and click on the steps you want to insert in the local container using the mouse.
Select Edit [Construct Container] Local from the menu bar. A new tab appears in the Diagram window which contains the contents of the new stage of the Local Container. You are warned if any disputes over the naming of ties arise when the container is installed. The new container is opened and shifts focus to its tab.As with any other stage in your job design, you can rename, move, and delete a container stage.
To display or change a local container in the Diagram window, simply double-click on the container stage. In a folder, you can edit the stages and links just the way you do for a work.
Drag and drop the Container icon in the General group on the tool palette to the Diagram window to build an empty container into which you can add stages and ties.In the Diagram window, a container stage is added, double-click on the stage to open it, and add stages and links to the container the same way you do for a job.Use of Local container Input and Output StagesPhases of input and output are used to describe the stages of the main job the container is connected to. datastage administrator training helps you to learn more effectively.If you are building a local container from an existing group of stages and links, the input and output stages will be added automatically.
The connection between the input or output stage and the container stage has the same name as the link in the Diagram window for the main job.In the example above the input link is the link from the Oracle OCI stage (oracle oci 0) of the main job connecting to the container. The output link is the connection that connects from the first container to the second.If you create a new container, the input and output stages will be placed in a container with no link.
You need to add stages between the input and output stages to the container Diagram window. Link the stages together, and edit the names of the links to match those in the main window.You can have any number of links in and out of a local container, in the job all the link names inside the container must match the link names within and outside it. Editing metadata on either side of the container edits the meta data on the connected stage in the job once a connection is established.
Shared ContainerShared containers also help you simplify the design but are reusable by other jobs unlike local containers. Shared containers can be used to make work components accessible in the project.Shared containers comprise groups of stages and connections, and are stored like DataStage jobs in the Repository. DataStage positions an instance of that container in the design when you insert a shared container into a job. When compiling the job which contains an instance of a shared container, the container code is included in the compiled job.
The DataStage debugger can be used on instances of shared containers that are used within jobs.You can create a shared container from scratch, or bring into a shared container a set of existing stages and links.Create a shared container out of the current job design.Press Shift and then press on the other stages and links to connect to the jar.
Select Edit [Construct Container] Shared from the menu bar. You will be asked via the Build New dialog box for a name for the container. The community is replaced with a Shared Container stage of the same sort in the Diagram window with the specified name.
Any parameters which occur in the components are copied as container parameters into the shared container. The generated instance has assigned all of its parameters to corresponding job parameters.Modify or display a Shared ContainerSelect File ->Open from the menu bar, then select Shared Folder to open. You can also highlight the Shared Container, right-click on the mouse and pick the address.Using a shared container
Drag a Shared Container icon in the Repository window from the Shared Container branch to the Diagram window of the job.
Update Tabs for Input and Output.Container Map ConnectionChoose the connection within the shared container to which you will map the incoming job link. You need to change the link to cause a validation process. Then you will be alerted if the metadata does not match and the meta data reconciliation option is provided as mentioned below.The Container ColumnsColumns page displays the metadata identified in a standard grid for the connection to the job point. In the Load Shared Containers button, you can use the Reconcile option to overwrite metadata on the job stage link with the container link meta data in the same way as defined for the Validate option.Conclusion:I hope you reach a conclusion about containers in DataStage. You can learn more about DataStage containers from DataStage online training.

snehacynixit

شاید از این پست‌ها خوشتان بیاید