Discussion:
TDI Server as windows service.
(too old to reply)
g***@gmail.com
2017-07-10 19:52:23 UTC
Permalink
Raw Message
Currently i'm trying to configure a windows for TDI, but i need that every time i start the service some config files must be load on startup.

I tried to modify this property.

com.ibm.di.server.autoload=configs

this seems to work when i start the server via command line

ibmdisrv.bat -d

or via the eclipse IDE

But, web i start the service via windows service console the configs files are not loaded.

There's any other solution to this problem??

"ibmdiservice.props"

path=D:\IBM\TDI\V7.1.1\jvm\jre\bin;D:\IBM\TDI\V7.1.1\libs;
ibmdiroot=D:\IBM\TDI\V7.1.1
jvmRoot=D:\IBM\TDI\V7.1.1\jvm
configfile=config
assemblylines=
cmdoptions=-d -c"*.xml"
jvmcmdoptions=
debug=false
controlledshutdown=false
servicename=Default

"solution.properties"

##
## Modify the line below to enable the config autoload feature. When this property is defined, the "ibmdisrv -d" command
## line will look for *.xml files in the directory specified by this property and start each one.
##
# com.ibm.di.server.autoload=autoload.tdi
com.ibm.di.server.autoload=configs\
##
## SYSTEM STORE
##
Eddie Hartman
2017-07-11 18:03:51 UTC
Permalink
Raw Message
Post by g***@gmail.com
Currently i'm trying to configure a windows for TDI, but i need that every time i start the service some config files must be load on startup.
I tried to modify this property.
com.ibm.di.server.autoload=configs
this seems to work when i start the server via command line
ibmdisrv.bat -d
or via the eclipse IDE
But, web i start the service via windows service console the configs files are not loaded.
There's any other solution to this problem??
"ibmdiservice.props"
path=D:\IBM\TDI\V7.1.1\jvm\jre\bin;D:\IBM\TDI\V7.1.1\libs;
ibmdiroot=D:\IBM\TDI\V7.1.1
jvmRoot=D:\IBM\TDI\V7.1.1\jvm
configfile=config
assemblylines=
cmdoptions=-d -c"*.xml"
jvmcmdoptions=
debug=false
controlledshutdown=false
servicename=Default
"solution.properties"
##
## Modify the line below to enable the config autoload feature. When this property is defined, the "ibmdisrv -d" command
## line will look for *.xml files in the directory specified by this property and start each one.
##
# com.ibm.di.server.autoload=autoload.tdi
com.ibm.di.server.autoload=configs\
##
## SYSTEM STORE
##
If you are running TDI as a service, i.e. using the win32_service/ibmdiservice.exe tool, you can specify the config to autoload using the ibmdiservice.props file. Note that auto-loading a config will only auto-start AssemblyLines if you specify these as auto-load in the CE.

I you want to start TDI from the commandline and load a config (or two) then you use the -c argument

ibmdisrv -c myConfig.xml myOtherConfig.xml -r ALtoStart1 ALtoStart2

and start ALs with the -r argument.
g***@gmail.com
2017-07-12 00:45:46 UTC
Permalink
Raw Message
Post by Eddie Hartman
Post by g***@gmail.com
Currently i'm trying to configure a windows for TDI, but i need that every time i start the service some config files must be load on startup.
I tried to modify this property.
com.ibm.di.server.autoload=configs
this seems to work when i start the server via command line
ibmdisrv.bat -d
or via the eclipse IDE
But, web i start the service via windows service console the configs files are not loaded.
There's any other solution to this problem??
"ibmdiservice.props"
path=D:\IBM\TDI\V7.1.1\jvm\jre\bin;D:\IBM\TDI\V7.1.1\libs;
ibmdiroot=D:\IBM\TDI\V7.1.1
jvmRoot=D:\IBM\TDI\V7.1.1\jvm
configfile=config
assemblylines=
cmdoptions=-d -c"*.xml"
jvmcmdoptions=
debug=false
controlledshutdown=false
servicename=Default
"solution.properties"
##
## Modify the line below to enable the config autoload feature. When this property is defined, the "ibmdisrv -d" command
## line will look for *.xml files in the directory specified by this property and start each one.
##
# com.ibm.di.server.autoload=autoload.tdi
com.ibm.di.server.autoload=configs\
##
## SYSTEM STORE
##
If you are running TDI as a service, i.e. using the win32_service/ibmdiservice.exe tool, you can specify the config to autoload using the ibmdiservice.props file. Note that auto-loading a config will only auto-start AssemblyLines if you specify these as auto-load in the CE.
I you want to start TDI from the commandline and load a config (or two) then you use the -c argument
ibmdisrv -c myConfig.xml myOtherConfig.xml -r ALtoStart1 ALtoStart2
and start ALs with the -r argument.
Thanks Eddie, i manage to start the configs, but now when i try to access the remote API only let me using "http://localhost:1098/dashboard", you know if there's any conflict using the same TDI default server? or if this process create another solution.properties in other path?
Eddie Hartman
2017-07-12 21:46:05 UTC
Permalink
Raw Message
Post by g***@gmail.com
Post by Eddie Hartman
Post by g***@gmail.com
Currently i'm trying to configure a windows for TDI, but i need that every time i start the service some config files must be load on startup.
I tried to modify this property.
com.ibm.di.server.autoload=configs
this seems to work when i start the server via command line
ibmdisrv.bat -d
or via the eclipse IDE
But, web i start the service via windows service console the configs files are not loaded.
There's any other solution to this problem??
"ibmdiservice.props"
path=D:\IBM\TDI\V7.1.1\jvm\jre\bin;D:\IBM\TDI\V7.1.1\libs;
ibmdiroot=D:\IBM\TDI\V7.1.1
jvmRoot=D:\IBM\TDI\V7.1.1\jvm
configfile=config
assemblylines=
cmdoptions=-d -c"*.xml"
jvmcmdoptions=
debug=false
controlledshutdown=false
servicename=Default
"solution.properties"
##
## Modify the line below to enable the config autoload feature. When this property is defined, the "ibmdisrv -d" command
## line will look for *.xml files in the directory specified by this property and start each one.
##
# com.ibm.di.server.autoload=autoload.tdi
com.ibm.di.server.autoload=configs\
##
## SYSTEM STORE
##
If you are running TDI as a service, i.e. using the win32_service/ibmdiservice.exe tool, you can specify the config to autoload using the ibmdiservice.props file. Note that auto-loading a config will only auto-start AssemblyLines if you specify these as auto-load in the CE.
I you want to start TDI from the commandline and load a config (or two) then you use the -c argument
ibmdisrv -c myConfig.xml myOtherConfig.xml -r ALtoStart1 ALtoStart2
and start ALs with the -r argument.
Thanks Eddie, i manage to start the configs, but now when i try to access the remote API only let me using "http://localhost:1098/dashboard", you know if there's any conflict using the same TDI default server? or if this process create another solution.properties in other path?
Each instance of the TDI server running must have its own Solution Directory with its own solution.properties that specifies the two ports: api.remote.naming.port and web.server.port.
Loading...