Internet Protocol version 6 (IPv6) is supported in BusinessObjects Enterprise If you are planning to deploy to an IPv6 network environment, ensure that the all computers have an IPv6 stack enabled, verify IPv6-based network connectivity between all computers in the deployment, and ensure that all DNS names resolve to IPv6 addresses.
Note: To verify IPv6 network connectivity and DNS name resolution, use the command ping -6 <FULL_DNS_NAME> on Windows computers, or ping6<FULL_DNS_NAME> on UNIX. It should ping the localhost.
If it does not ping the local host on UNIX, add an IPv6 entry in the /etc/hosts file of that computer as follows:
|
<IPv6 address> |
<full qualified hostname> |
<hostname> |
|
::1 |
localhost.localdomain |
localhost |
For example:
|
fe##:#:###:##ff:fe##:ac##:###:ac#f |
abc00##.eg.com |
abc00## |
|
::1 |
localhost.localdomain |
localhost |
BusinessObjects Enterprise can run on IPv6-only hosts (with only an IPv6 stack enabled), IPv4-only hosts (only an IPv4 stack enabled), or mixed hosts (with both IPv6 and IPv4 stacks enabled). A host with both IPv4 and IPv6 enabled can accept and send both IPv4 and IPv6 traffic. A host using only IPv6 can only accept and send IPv6 traffic. You should determine which network protocol and the host type best fits your needs before deploying BusinessObjects Enterprise.
If you plan to use third-party software products in a BusinessObjects Enterprise IPv6 deployment, such as a database or LDAP server, you must ensure that they are also IPv6-compliant. To run non-IPv6-compliant products in an IPv6 BusinessObjects Enterprise deployment, use a mixed IPv6/IPv4 host.
If you are going to transition an existing BusinessObjects Enterprise deployment to an IPv6-only environment, consider the following recommendations:
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |