Page 1 of 1

Execute Process by command line

Posted: Wed Jan 15, 2014 6:50 pm
by aleferrer
Hello to all!

Has anyone run a Turbo Integrator process through a command line? If yes, could provide an example?




Regards,

Alessandro

Re: Execute Process by command line

Posted: Wed Jan 15, 2014 7:03 pm
by declanr
Google TM1RunTI or search the forum for it.

There have been a few posts on here and IBM provided a document showing how to use it that appears up near the top of a google search.

Re: Execute Process by command line

Posted: Fri Jan 17, 2014 12:53 pm
by aleferrer
declanr wrote:Google TM1RunTI or search the forum for it.

There have been a few posts on here and IBM provided a document showing how to use it that appears up near the top of a google search.

I have found the document. I do not understand how to apply. I do not know if I apply the syntax in a configuration file, or via cmd ... has no more explanatory tutorial.

Re: Execute Process by command line

Posted: Fri Jan 17, 2014 4:10 pm
by qml
Please let us know which part of the following paragraph you found difficult to understand and we will try to help.
tm1runti.pdf wrote:Parameters

Parameters can be either in a configuration file or passed on the command line.
Command line parameters take precedence over parameters that are in the
configuration file.
This makes it possible to have persistent default parameters for
relatively static parameters (such as adminhost and server) and to supply just the
few parameters needed to either override the defaults or to provide values that are
not easily defaulted, such as the user name or the TurboIntegrator process name.

The parameters have a different format when passed on the command line. While
all parameters are passed in a "-parameter_name value" fashion, everything that is
passed as "parameter_name=value" is treated as a TurboIntegrator process
parameter.

There are four types of parameters:
* Command parameters
Used to specify the config file to use, which group of connection parameters to
use, or which TurboIntegrator process to run.
* Connection parameters
Used to specify the servername, username and other information needed to
connect to a TM1 server.
* Password parameters
Can either be a username and plaintext password or can be a filename
containing an encrypted password and associated keyfile used for decryption.
* TurboIntegrator parameters
Passed to the named TurboIntegrator.

Parameters specified on the command line must begin with dash (-) or slash (/).
The parameter value is separated from the parameter name by a space, and the
value can be specified as is or in quotes (if there are embedded spaces).

For example:

tm1runti –server MyTM1Server –username John –pwd "my secret"
ti_parm1=yes ti_parm2="my value"

Re: Execute Process by command line

Posted: Fri Jan 17, 2014 5:30 pm
by aleferrer
qml wrote:Please let us know which part of the following paragraph you found difficult to understand and we will try to help.
tm1runti.pdf wrote:Parameters

Parameters can be either in a configuration file or passed on the command line.
Command line parameters take precedence over parameters that are in the
configuration file.
This makes it possible to have persistent default parameters for
relatively static parameters (such as adminhost and server) and to supply just the
few parameters needed to either override the defaults or to provide values that are
not easily defaulted, such as the user name or the TurboIntegrator process name.

The parameters have a different format when passed on the command line. While
all parameters are passed in a "-parameter_name value" fashion, everything that is
passed as "parameter_name=value" is treated as a TurboIntegrator process
parameter.

There are four types of parameters:
* Command parameters
Used to specify the config file to use, which group of connection parameters to
use, or which TurboIntegrator process to run.
* Connection parameters
Used to specify the servername, username and other information needed to
connect to a TM1 server.
* Password parameters
Can either be a username and plaintext password or can be a filename
containing an encrypted password and associated keyfile used for decryption.
* TurboIntegrator parameters
Passed to the named TurboIntegrator.

Parameters specified on the command line must begin with dash (-) or slash (/).
The parameter value is separated from the parameter name by a space, and the
value can be specified as is or in quotes (if there are embedded spaces).

For example:

tm1runti –server MyTM1Server –username John –pwd "my secret"
ti_parm1=yes ti_parm2="my value"

My main question is:
- As I start the procedure? Start with a file. Txt passes the parameters and saved in any specific directory?
- Parameters Step through a .bat file?
- The TM1RunTI has some interface so that I can pass these parameters?

My biggest difficulty is how to start the procedure.

Regards,

Alessandro

Re: Execute Process by command line

Posted: Fri Jan 17, 2014 6:46 pm
by David Usherwood
Where are you trying to run it from?
If you start a Windows command prompt then navigate to the TM1 BIN install directory you can see what the parameters are and get a command line working, then put the command into a .BAT or .CMD file. If you want to run it from TM1 then I would suggest getting the .CMD working and calling it using ExecuteCommand.

Re: Execute Process by command line

Posted: Tue Jan 21, 2014 2:21 pm
by aleferrer
David Usherwood wrote:Where are you trying to run it from?
If you start a Windows command prompt then navigate to the TM1 BIN install directory you can see what the parameters are and get a command line working, then put the command into a .BAT or .CMD file. If you want to run it from TM1 then I would suggest getting the .CMD working and calling it using ExecuteCommand.

I'm trying to run it through a file. Bat.
My demand is running a TM1 process through a file. Bat.
I'm not able to create the correct syntax through the documents made ​​available by IBM.

Re: Execute Process by command line

Posted: Tue Jan 21, 2014 2:59 pm
by qml
Any chance of showing us your batch script? Have you tried running it manually (i.e. not from TI)? If yes, what are the results?