The Flow

Command of a Job , let us suppose. Understand it

C:\xx\yy\zz\aa.exe /WF=\\some.xml /ES.CutDate=20160318 /ES=\\some.xml

.exe.config is the Application Config file.

Below are the various sections in the config file. This is a Workflow Console Application config.

Windows Workflow Foundation (WF) allows you to create workflows for executing system or human processes. The Windows Workflow Designer provides the design surface for creating these workflows. The Workflow Designer can be used to create workflows from within Visual Studio or it can be integrated into other applications that rehost the designer.

As you can see the above is a console App. What exactly is a console App ?

It is a computer program designed to be used via a text only interface. Basically You can use in your command line Apps. Here is text interface is the Autosys box.

log4net

The Apache log4net library is a tool to help the programmer output log statements to a variety of output targets. log4net is a port of the excellent Apache log4j™ framework to the Microsoft® .NET runtime. We have kept the framework similar in spirit to the original log4j while taking advantage of new features in the .NET runtime. For more information on log4net see the features document.

log4net.Appender.ConsoleAppender Writes logging events to the application’s Console. The events may go to either the standard our stream or the standard error stream.

log4net is configured using an XML configuration file. The configuration information can be embedded within other XML configuration files (such as the application’s .config file) or in a separate file. The configuration is easily readable and updateable while retaining the flexibility to express all configurations.

<assemblyBinding> Element for <runtime>

Contains information about assembly version redirection and the locations of assemblies.
<configuration>
<runtime>
<assemblyBinding>

The configSections element specifies configuration section and handler declarations. This is required because ASP.NET makes no presumptions about how to handle settings within a configuration file. Instead, ASP.NET delegates the processing of configuration data to configuration section handlers.

<appSettings> Element
Contains custom application settings. This is a predefined configuration section provided by the .NET Framework.

 

k2.jpg

For each transition, you specify a set of reasons for changing the state of the work item, including a default reason. You can assign values for each state, transition, or reason, and you can place conditions on the values of one or more fields by using the FIELD (Workflow) element. In addition, you can trigger an action to occur during a transition by specifying the ACTION element.

the ES file contains various internal values for the job . The WF has all the actions

What is ADT (Application Deployment Tool)

it is a tool which allows application developers to deploy their Windows Application onto the user desktop. It is a Hosted self service.

Advantages or ADT

-New app releases can be launched without service restarts

-secure

k3.jpg

ADT client is installed on the user desktop . It retrieves shortcuts, validates packages and launches applications

workflow for a ADT.

Build ADT package by creating a ZIP files with all the app components

What is an Assembly in .Net

simple terms: A chunk of (precompiled) code that can be executed by the .NET runtime environment.

as in to compare with JAVA

Java =.Net
==== ====
Class= Class
Package= Namespace
Jar =Assembly

Assembly is the smallest unit of deployment of a .net application. It can be a dll or an exe.There are mainly two types to it:

Private Assembly: The dll or exe which is sole property of one application only. It is generally stored in application root folder
Public/Shared assembly: It is a dll which can be used by multiple applications at a time. A shared assembly is stored in GAC i.e Global Assembly Cache.

When you compile an application, the MSIL code created is stored in an assembly . Assemblies include both executable application files that you can run directly from Windows without the need for any other programs (these have a .exe file extension), and libraries (which have a .dll extension) for use by other applications.

In addition to containing MSIL, assemblies also include meta information (that is, information about the information contained in the assembly, also known as metadata ) and optional resources (additional data used by the MSIL, such as sound files and pictures). The meta information enables assemblies to be fully self – descriptive. You need no other information to use an assembly, meaning you avoid situations such as failing to add required data to the system registry and so on, which was often a problem when developing with other platforms.

This means that deploying applications is often as simple as copying the files into a directory on a remote computer. Because no additional information is required on the target systems, you can just run an executable file from this directory and (assuming the .NET CLR is installed) you ’ re good to go.

Of course, you won ’ t necessarily want to include everything required to run an application in one place. You might write some code that performs tasks required by multiple applications. In situations like that, it is often useful to place the reusable code in a place accessible to all applications. In the .NET Framework, this is the Global Assembly Cache (GAC) . Placing code in the GAC is simple — you just place the assembly containing the code in the directory containing this cache.