TDI:Colocando em Producao: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
== Criando uma bat para | == Criando uma bat para testar os AssemblyLines == | ||
Estaremos executando as duas AssemblyLines '''SyncUsersAD_to_Domino''' ,'''SyncGroupAD_to_Domino''' configuradas no nosso arquivo xml '''AD_Domino_Sync.xml'''. | Estaremos executando as duas AssemblyLines '''SyncUsersAD_to_Domino''' ,'''SyncGroupAD_to_Domino''' configuradas no nosso arquivo xml '''AD_Domino_Sync.xml'''. | ||
| Line 18: | Line 18: | ||
Configuration file(s). If you don't specify this option, the items in the Autostart folder will be loaded and started (unless suppressed by specifying -D). Wildcards, as in *.xml, are allowed too. | Configuration file(s). If you don't specify this option, the items in the Autostart folder will be loaded and started (unless suppressed by specifying -D). Wildcards, as in *.xml, are allowed too. | ||
-r <al...> | '''-r <al...>''' | ||
List of AssemblyLine names to start. To start AssemblyLine a and b, use the command -r a b. Other syntaxes are supported as well: -ra,b; -ra -rb. | List of AssemblyLine names to start. To start AssemblyLine a and b, use the command -r a b. Other syntaxes are supported as well: -ra,b; -ra -rb. | ||
Note: | '''Note:''' | ||
If you use includes and namespaces, the AssemblyLine can be myNamespace:/AssemblyLines/alName (assuming namespace myNamespace and AssemblyLine name alName). | If you use includes and namespaces, the AssemblyLine can be myNamespace:/AssemblyLines/alName (assuming namespace myNamespace and AssemblyLine name alName). | ||
Revision as of 19:00, 10 December 2007
Após desenvolver todo o script de integração no Config Editor (CDE) do Tivoli Directory Integrator, está na hora de colocar em produção.
Abaixo temos alguns passos para colocar em Produção:
Criando uma bat para testar os AssemblyLines
Estaremos executando as duas AssemblyLines SyncUsersAD_to_Domino ,SyncGroupAD_to_Domino configuradas no nosso arquivo xml AD_Domino_Sync.xml.
ibmdisrv -c"C:\IBM\TDI\V6.1.1\WorkingWithDomino\AD_Domino_Sync.xml"
-r"SyncUsersAD_to_Domino,SyncGroupAD_to_Domino"
-l"c:\IBM\TDI\logs\AD_Domino_Sync.log"
Onde:
-c <Arquivo...> Configuration file(s). If you don't specify this option, the items in the Autostart folder will be loaded and started (unless suppressed by specifying -D). Wildcards, as in *.xml, are allowed too.
-r <al...> List of AssemblyLine names to start. To start AssemblyLine a and b, use the command -r a b. Other syntaxes are supported as well: -ra,b; -ra -rb. Note: If you use includes and namespaces, the AssemblyLine can be myNamespace:/AssemblyLines/alName (assuming namespace myNamespace and AssemblyLine name alName).
-l <file> Log file (default console output). Does very little as few messages go to the console. To change the log file for most of the logging, change log4j.properties.
Mais Detalhes:
Opções de Comando do TDI Server
Configurando o Tivoli Directory Integrator como um serviço do Windows
Um exemplo completo do arquivo ibmdiservice.props seria da seguinte maneira:
path=C:\Program Files\IBM\TDI\V6.1.1\jvm\jre\bin;C:\Program Files\IBM\TDI\V6.1.1\libs; ibmdiroot=C:\Program Files\IBM\TDI\V6.1.1 configfile=rs.xml assemblylines=AssemblyLine1,AssemblyLine2 eventhandlers=EventHandler1,EventHandler2 cmdoptions=-d debug=false
Configurando o Tivoli Directory Integrator como um serviço do Windows
Configurando o Tivoli Directory Integrator como um serviço no Linux
Configurando o Tivoli Directory Integrator como um serviço no Linux