This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
2_x:administrators:install-standalone [2020/08/12 17:44] – [Configuring the CMDB] cnaud | 2_x:administrators:install-standalone [2020/08/12 18:05] – cnaud | ||
---|---|---|---|
Line 16: | Line 16: | ||
{{: | {{: | ||
+ | ==== Fresh installation ==== | ||
If you select to install a new instance then third step of the wizard will prompt you to accept the license agreement. | If you select to install a new instance then third step of the wizard will prompt you to accept the license agreement. | ||
Line 26: | Line 27: | ||
Note that the database server does not need to be on the same physical server as the PHP/web server. It can be a remote host if you prefer to have a two-tier architecture, | Note that the database server does not need to be on the same physical server as the PHP/web server. It can be a remote host if you prefer to have a two-tier architecture, | ||
- | {{:2_x:install4.png? | + | {{:2_x:install41.png? |
The next step of the wizard prompts you for the information about the administrator account. TeemIp authentication can rely on external mechanisms (LDAP, Active Directory or JASIG-CAS) but the installation requires that at least one administrator account be created with a local password. | The next step of the wizard prompts you for the information about the administrator account. TeemIp authentication can rely on external mechanisms (LDAP, Active Directory or JASIG-CAS) but the installation requires that at least one administrator account be created with a local password. | ||
Line 42: | Line 43: | ||
In case you have multiple virtual hosts pointing to TeemIp or if you are using a test system with a dynamic IP address (DHCP) and you want to connect anyway from another system, the “address” of the TeemIp server cannot be fixed at installation time. In this case you can use the placeholder **$_SERVER_NAME_$** in the URL parameter. For example you can type: < | In case you have multiple virtual hosts pointing to TeemIp or if you are using a test system with a dynamic IP address (DHCP) and you want to connect anyway from another system, the “address” of the TeemIp server cannot be fixed at installation time. In this case you can use the placeholder **$_SERVER_NAME_$** in the URL parameter. For example you can type: < | ||
</ | </ | ||
+ | |||
+ | ==== Upgrade ==== | ||
+ | Should you decide to upgrade an existing instance, then the following step will ask you to specify that existing instance... | ||
+ | |||
+ | {{: | ||
+ | |||
+ | .. before displaying the current and next version of the product | ||
+ | |||
+ | {{: | ||
+ | |||
+ | .. and asking you to double check some additional parameters. | ||
+ | |||
+ | {{: | ||
Line 58: | Line 72: | ||
{{: | {{: | ||
- | ==== Configuring IP and DNS Management ==== | + | ==== Configuring IP, DHCP and DNS Management ==== |
- | In the current version, there is only one module | + | In the current version, there are 4 modules |
* The base/core IP module will allow you to manage your IPv4 and IPv6 spaces. It must always be present in TeemIp. | * The base/core IP module will allow you to manage your IPv4 and IPv6 spaces. It must always be present in TeemIp. | ||
+ | * The IP Discovery extension that discovers active IPs on networks. This extension works in conjunction with IP Discovery Collectors installed outside TeemIp. It is optional. | ||
+ | * The DNS Zone Management module helps you manage DNS views, zones and DNS records in relation with IP addresses. This module is optional as well. | ||
+ | * And finally, the DHCP Management module to define and register the DHCP options in use within your DHCP infrastructure. Optional as well. | ||
{{: | {{: |