Pb generating job on the command line

One Star

Pb generating job on the command line

TAC says "Connection to the generator failed" but the port 8002 is listening and I can see this log from the command line :
!SESSION 2009-08-05 11:41:08.116 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=fr_FR
Framework arguments: -application org.talend.commandline.CommandLine startServer -p 8002
Command-line arguments: -os linux -ws gtk -arch x86 -application org.talend.commandline.CommandLine -consoleLog -data commandline-workspace startServer -p 8002
!ENTRY org.talend.commandline 1 0 2009-08-05 11:41:09.477
!MESSAGE Starting up Command Line Application
talend>
!ENTRY org.eclipse.osgi 2 1 2009-08-05 11:41:31.282
!MESSAGE NLS unused message: resources_wrongMarkerAttributeValueType in: org.eclipse.core.internal.utils.messages
---------------------------------------------------------------
The "listProject" command show me the correct project, the "initDatabase" doesn't work though (it shows me only the std help output).
One Star

Re: Pb generating job on the command line

Nevermind, I cleaned up the "command line"'s workspace, and it generated successfully.
Community Manager

Re: Pb generating job on the command line

Hello Morbo
Which version of TIS do you install? I remember initDatabase was replaced by initRemote since 3.0.
Best regards
shong
----------------------------------------------------------
Talend | Data Agility for Modern Business
One Star

Re: Pb generating job on the command line

Hello shong,
I'm on 3.1.3, I used the pdf doc wich were talking about initDatabase (page 32/36).
But it's true it doesn't show in help from the shell of the commandLine :
talend> help
+--------------------------------------------------------------------------------------------------+
|Talend Commandline Plugin : |
| * arguments can be surrounded by (") or (') characters |
| * the semi-colon (;) character can be used to separate commands from each other |
| * special characters (space \ " ' ;) can be escaped using the character (\) |
+--------------------------------------------------------------------------------------------------+
|Usage: |
| |-jrdd <path>|-jt <time (in sec)>|-jactc exportAllJob -dd <path>|-jc <context |
|name>|-jactc executeJob <jobName> -i <path>|-jv <version>|-jc <context name>|-jcp <key=value1> |
||-jrdd <path>|-jt <time (in sec)>|-jactc executeJobOnServer <jobName> -jv |
|<version>|-jc <context name>|-jcp <key=value1> |-jactc|-es <name> exportJob |
|<jobName> -dd <path>|-jv <version>|-jc <context name>|-af <filename>|-jactc getCommandStatus |
|<commandId> importItems <source (dir|.zip)> -if <filterExpr>|-o exportItems <destination |
|(dir|.zip)> -if <filterExpr> deleteItems -if <filterExpr> changeVersion <newVersion> -if |
|<filterExpr> changeStatus <newStatusCode> -if <filterExpr> importDatabaseMetadata <filePath> |
|importDelimitedMetadata <filePath>] |
+--------------------------------------------------------------------------------------------------+
| stopServer stops server |
| -f (--force) don't wait for queued commands |
| help shows help |
| helpFilter shows filter help |
| showVersion shows product version |
| listCommand lists commands |
| -a (--all) lists all commands |
| listExecutionServer lists execution servers |
| listJob lists jobs |
| listProject lists available projects |
| initLocal init local repository |
| initRemote adminUrl init remote repository |
| logoffProject logs off |
| logonProject logs on a project |
| -pn (--project-name) technical name project name |
| -ul (--user-login) login user login |
| -up (--user-password) password user password |
| -gt (--generate-templates) generate templates |
| createProject creates a project |
| -pn (--project-name) technical name project name |
| -pd (--project-description) description project description |
| -pl (--project-language) language (java/perl) project language |
| -pa (--project-author) author login project author |
| executeAllJob executes all |
| -i (--interpreter) path perl/java interpreter path |
| -jc (--job-context) context name chooses a job context |
| -jcp (--job-context-param) key=value provides a job context param |
| -jrdd (--job-result-destination-dir) path job execution result destination dir |
| -jt (--job-timeout) time (in sec) timeout of execution |
| -jactc (--job-apply-context-to-children) apply context to children |
| exportAllJob exports all |
| -dd (--destination-directory) path destination directory |
| -jc (--job-context) context name chooses a job context |
| -jactc (--job-apply-context-to-children) apply context to children |
| executeJob jobName executes |
| -i (--interpreter) path perl/java interpreter path |
| -jv (--job-version) version chooses a job version |
| -jc (--job-context) context name chooses a job context |
| -jcp (--job-context-param) key=value provides a job context param |
| -jrdd (--job-result-destination-dir) path job execution result destination dir |
| -jt (--job-timeout) time (in sec) timeout of execution |
| -jactc (--job-apply-context-to-children) apply context to children |
| executeJobOnServer jobName executes on server |
| -jv (--job-version) version chooses a job version |
| -jc (--job-context) context name chooses a job context |
| -jcp (--job-context-param) key=value provides a job context param |
| -jactc (--job-apply-context-to-children) apply context to children |
| -es (--execution-server) name execution server name |
| exportJob jobName exports |
| -dd (--destination-directory) path destination directory |
| -jv (--job-version) version chooses a job version |
| -jc (--job-context) context name chooses a job context |
| -af (--archive-filename) filename archive filename (without .zip) |
| -jactc (--job-apply-context-to-children) apply context to children |
| getCommandStatus commandId gets command status |
| importItems source (dir|.zip) imports items |
| -if (--item-filter) filterExpr item filter expression |
| -o (--overwrite) overwrite existing items |
| exportItems destination (dir|.zip) exports items |
| -if (--item-filter) filterExpr item filter expression |
| deleteItems delete items |
| -if (--item-filter) filterExpr item filter expression |
| changeVersion newVersion changes items version |
| -if (--item-filter) filterExpr item filter expression |
| changeStatus newStatusCode changes items status |
| -if (--item-filter) filterExpr item filter expression |
| importDatabaseMetadata filePath imports database metadata |
| importDelimitedMetadata filePath imports delimited metadata |
+--------------------------------------------------------------------------------------------------+
| Copyright (C) 2006-2008 Talend - www.talend.com |
+--------------------------------------------------------------------------------------------------+
One Star

Re: Pb generating job on the command line

Actually, my commandLine doesn't seems to work very well, now I can never list project through the shell :
a commandline-workspace startServer -p 8002
!ENTRY org.talend.commandline 1 0 2009-08-05 17:04:35.753
!MESSAGE Starting up Command Line Application
talend> listProject
!ENTRY org.talend.commandline 4 0 2009-08-05 17:04:40.298
!MESSAGE a repository should be initialized
!STACK 0
java.lang.IllegalStateException: a repository should be initialized
at org.talend.commandline.command.CommandProcessor.checkInitialized(Unknown Source)
at org.talend.commandline.command.CommandProcessor.listProject(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.computeCommand(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.process(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.execute(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.execute(Unknown Source)
at org.talend.commandline.mode.ShellServerHandler.start(Unknown Source)
at org.talend.commandline.mode.ServerCommandLine$InteractiveServerShell.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)
java.lang.IllegalStateException: a repository should be initialized
at org.talend.commandline.command.CommandProcessor.checkInitialized(Unknown Source)
at org.talend.commandline.command.CommandProcessor.listProject(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.computeCommand(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.process(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.execute(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.execute(Unknown Source)
at org.talend.commandline.mode.ShellServerHandler.start(Unknown Source)
at org.talend.commandline.mode.ServerCommandLine$InteractiveServerShell.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)
talend> initLocal
ADDED_COMMAND 0
talend>
!ENTRY org.eclipse.osgi 2 1 2009-08-05 17:04:59.922
!MESSAGE NLS unused message: resources_wrongMarkerAttributeValueType in: org.eclipse.core.internal.utils.messages
talend> listProject
talend> listJob
!ENTRY org.talend.commandline 4 0 2009-08-05 17:05:22.052
!MESSAGE should be logged on a repository
!STACK 0
java.lang.IllegalStateException: should be logged on a repository
at org.talend.commandline.command.CommandProcessor.checkLogged(Unknown Source)
at org.talend.commandline.command.CommandProcessor.listJob(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.computeCommand(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.process(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.execute(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.execute(Unknown Source)
at org.talend.commandline.mode.ShellServerHandler.start(Unknown Source)
at org.talend.commandline.mode.ServerCommandLine$InteractiveServerShell.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)
java.lang.IllegalStateException: should be logged on a repository
at org.talend.commandline.command.CommandProcessor.checkLogged(Unknown Source)
at org.talend.commandline.command.CommandProcessor.listJob(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.computeCommand(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.process(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.execute(Unknown Source)
at org.talend.commandline.cli.CommandLineHandler.execute(Unknown Source)
at org.talend.commandline.mode.ShellServerHandler.start(Unknown Source)
at org.talend.commandline.mode.ServerCommandLine$InteractiveServerShell.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)

A project is deployed, visible, runnable through TAC.
One Star

Re: Pb generating job on the command line

Hi,
I am also facing the same issue. Please let me know if you have any suggestions.
Community Manager

Re: Pb generating job on the command line

Hello Arun
What's your problem now? "Connection to the generator failed" or "java.lang.IllegalStateException: a repository should be initialized"?
if "Connection to the generator failed", you need to check if the commandline is running and you able to ping to ip 8002 from your machine where tac is installed.
"java.lang.IllegalStateException: a repository should be initialized", as the message said, you need to initialize a remote connection first using the command:
initRemote adimUrl
Best regards
Shong
----------------------------------------------------------
Talend | Data Agility for Modern Business
One Star

Re: Pb generating job on the command line

Hi Shong,
I am getting an error "Connection to the generator failed" while running the job from TAC. But My commandLine is running on the port 8002 and also the Job server also running.
Actually am trying to execute the jobs from remote machines by exporting my SVN Repository and importing it into remote machine epository.
I can able to run the Jobs in TAC from my machine wherei am having connection from commandline to my Talend Studio.But when I want to execute the same jobs in Remote machines TAC with out opening the Talend in remote machine.
Please give me the solution for this.

Thanks In Advance,
Srinivas