PORTAL SERVER 6.0 and Directory Server 5.1 existing

I have one istance on sunone directory server 5.1 . I want install secure portal server 6.0 and i want use this directory server? . In the installation manual there are't this procedure.
When I install the portal I select the installation with existing ldap and the portal server is installed . When I started the portal server this don't work.
Thank's

Go to Identity Server v5.1 documentation. It's well documented there. In two words, after you installed it this way, you have to apply 'existing.ldif' file to create ACIs and roles, then to create all services.
Please check existing.ldif before you will apply it. Depending on your DIT, it may be quite broken. Don't forget to change ums.xml to match your schema.

Similar Messages

Does the iplanet Portal server support other existing standalone Webservers/application Servers the likes of weblogic, websphere etc?

If so, will the session management aspect be looked after by the iPlanet Portal server?

The new version of Portal (6.0 I believe) will run on weblogic or websphere as well as iAS.
Kent

Configure WebSphere Portal Server to use LDAP (Oracle Internet Directory)

I did configuration for WebSphere Portal to use security with LDAP Oracle Internet Directory (OID). The script for configuring works well (WPSConfig.bat action-secure-portal-ldap)
But when i start Portal Server it cannot start successfully. I did check in log file and found a error on SystemOut.log as attachment log below. I don't know what happen with WebSphere Portal Server.
If you guys know how to fix it please let me know or point me some documents to configure this again.
Thanks in advanced.
Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.
com.ibm.wps.ac.DomainAdministratorNotFoundException: EJPSB0107E: Exception occurred while retrieving the identity of the domain adminuser/admingroup uid=wpsadmin,cn=Users,dc=localhost,dc=com.

There is no clear documentation available to enable custom security but IBM info center has decent documentation for LDAP based security. I would say follow the steps mentioned for IBM directory and then modify the necessary configuration parameters for OID. This should solve your issues. For better help open a PMR with IBM to get necessary quick help.

Missing Images and CSS when going to portal/server.pt can't login

Hi,
I installed WebCenterInteraction_10.3.0.0.0 on Windows and followed all the steps mentioned in the install doc. Deployed the portal.ear and here is what I see on the command line after deployment:
Task #1 (InitPortalObjects) END (OK)
Task #2 (CheckDevKit) END (OK)
Task #3 (InitializePaths) END (OK)
Task #4 (InitializeApplication) END (OK)
Task #5 (InitializeAppWarmUpHelper) END (OK)
Task #6 (InitializeImageServerHelper) END (OK)
Task #7 (InitializeConfigHelper) END (OK)
Task #8 (InitializeResourceManager) END (OK)
Task #9 (LoadVersionHelper) END (OK)
Task #10 (InitializeActivitySpaces) END (OK)
Task #11 (InitializeVarPacks) END (OK)
Task #12 (InitializeImageServerHelperPartII) END (OK)
Task #13 (InitializeObjects) END (OK)
Task #14 (LoadCustomLoads) END (OK)
Task #15 (CheckDBVersion) END (OK)
Aqualogic Interaction startup successful.
    ======= Diagnostic Run Complete =======
    Startup completion percentage: 100% (50 steps out of 50 complete)
    ===== Portal should now start successfully ===== But when I go to http://localhost:7001/portal/server.pt I don't see any images and the css is not applied so can't login. Any idea what might be wrong. Here is the Apache httpd.conf
Include "C:/bea/alui/plumtreeconf/"
# Based upon the NCSA server configuration files originally by Rob McCool.
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.0/> for detailed information about
# the directives.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
#     whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
#     which responds to requests that aren't handled by a virtual host.
#     These directives also provide default values for the settings
#     of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
#     different IP addresses or hostnames and have them handled by the
#     same Apache server process.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/Program Files/Apache Group/Apache2" will be interpreted by the
# server as "C:/Program Files/Apache Group/Apache2/logs/foo.log".
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default. It is recommended that you always supply
# an explicit drive letter in absolute paths, however, to avoid
# confusion.
### Section 1: Global Environment
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs/2.0/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
# Do NOT add a slash at the end of the directory path.
ServerRoot "C:/Program Files/Apache Group/Apache2"
# ScoreBoardFile: File used to store internal server process information.
# If unspecified (the default), the scoreboard will be stored in an
# anonymous shared memory segment, and will be unavailable to third-party
# applications.
# If specified, ensure that no two invocations of Apache share the same
# scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK.
#ScoreBoardFile logs/apache_runtime_status
# PidFile: The file in which the server should record its process
# identification number when it starts.
PidFile logs/httpd.pid
# Timeout: The number of seconds before receives and sends time out.
Timeout 300
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
KeepAlive On
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
MaxKeepAliveRequests 100
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
KeepAliveTimeout 15
## Server-Pool Size Regulation (MPM specific)
# WinNT MPM
# ThreadsPerChild: constant number of worker threads in the server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_winnt.c>
ThreadsPerChild 250
MaxRequestsPerChild 0
</IfModule>
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#Listen 12.34.56.78:80
# Listen 80
Listen 80
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule access_module modules/mod_access.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_module modules/mod_auth.so
#LoadModule auth_anon_module modules/mod_auth_anon.so
#LoadModule auth_dbm_module modules/mod_auth_dbm.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule headers_module modules/mod_headers.so
LoadModule imap_module modules/mod_imap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so
LoadModule weblogic_module modules/mod_wl_20.so
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#ExtendedStatus On
### Section 2: 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work. See also the UseCanonicalName directive.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make
# redirections work in a sensible way.
ServerName localhost:80
# UseCanonicalName: Determines how Apache constructs self-referencing
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client. When set "On", Apache will use the value of the
# ServerName directive.
UseCanonicalName Off
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs"
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# features.
<Directory />
    Options FollowSymLinks
    AllowOverride None
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "C:/Program Files/Apache Group/Apache2/htdocs">
# Possible values for the Options directive are "None", "All",
# or any combination of:
#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.0/mod/core.html#options
# for more information.
    Options Indexes FollowSymLinks
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
#   Options FileInfo AuthConfig Limit
    AllowOverride None
# Controls who can get stuff from this server.
    Order allow,deny
    Allow from all
</Directory>
# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received. Be especially careful to use
# proper, forward slashes here. On Windows NT, "Personal/My Website"
# is a more appropriate choice.
UserDir "My Documents/My Website"
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
# You must correct the path for the root to match your system's configured
# user directory location, e.g. "C:/WinNT/profiles/*/My Documents/My Website"
# or whichever, as appropriate.
#<Directory "C:/Documents and Settings/*/My Documents/My Website">
#    AllowOverride FileInfo AuthConfig Limit
#    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
#    <Limit GET POST OPTIONS PROPFIND>
#        Order allow,deny
#        Allow from all
#    </Limit>
#    <LimitExcept GET POST OPTIONS PROPFIND>
#        Order deny,allow
#        Deny from all
#    </LimitExcept>
#</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents. The MultiViews Option can be used for the
# same purpose, but it is much slower.
DirectoryIndex index.html index.html.var
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
AccessFileName .htaccess
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
</FilesMatch>
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
TypesConfig conf/mime.types
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
<IfModule mod_mime_magic.c>
    MIMEMagicFile conf/magic
</IfModule>
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
HostnameLookups Off
# EnableMMAP: Control whether memory-mapping is used to deliver
# files (assuming that the underlying OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. On some systems, turning it off (regardless of
# filesystem) can improve performance; for details, please see
# http://httpd.apache.org/docs/2.0/mod/core.html#enablemmap
#EnableMMAP off
# EnableSendfile: Control whether the sendfile kernel support is
# used to deliver files (assuming that the OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. Please see
# http://httpd.apache.org/docs/2.0/mod/core.html#enablesendfile
#EnableSendfile off
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog logs/error.log
# LogLevel: Control the number of messages logged to the error.log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# You need to enable mod_logio.c to use %I and %O
#LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
CustomLog logs/access.log common
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#CustomLog logs/referer.log referer
#CustomLog logs/agent.log agent
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog logs/access.log combined
# ServerTokens
# This directive configures what you return as the Server HTTP response
# Header. The default is 'Full' which sends information about the OS-Type
# and compiled in modules.
# Set to one of: Full | OS | Minor | Minimal | Major | Prod
# where Full conveys the most information, and Prod the least.
ServerTokens Full
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (internal error documents, FTP directory
# listings, mod_status and mod_info output etc., but not CGI generated
# documents or custom error documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
ServerSignature On
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL. So "/icons" isn't aliased in this
# example, only "/icons/". If the fakename is slash-terminated, then the
# realname must also be slash terminated, and if the fakename omits the
# trailing slash, the realname must also omit it.
# We include the /icons/ alias for FancyIndexed directory listings. If you
# do not use FancyIndexing, you may comment this out.
Alias /icons/ "C:/Program Files/Apache Group/Apache2/icons/"
<Directory "C:/Program Files/Apache Group/Apache2/icons">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>
# This should be changed to the ServerRoot/manual/. The alias provides
# the manual, even if you choose to move your DocumentRoot. You may comment
# this out if you do not care for the documentation.
AliasMatch ^/manual(?:/(?:de|en|es|fr|ja|ko|ru))?(/.*)?$ "C:/Program Files/Apache Group/Apache2/manual$1"
<Directory "C:/Program Files/Apache Group/Apache2/manual">
    Options Indexes
    AllowOverride None
    Order allow,deny
    Allow from all
    <Files *.html>
        SetHandler type-map
    </Files>
    SetEnvIf Request_URI ^/manual/(de|en|es|fr|ja|ko|ru)/ prefer-language=$1
    RedirectMatch 301 ^/manual(?:/(de|en|es|fr|ja|ko|ru)){2,}(/.*)?$ /manual/$1$2
</Directory>
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
ScriptAlias /cgi-bin/ "C:/Program Files/Apache Group/Apache2/cgi-bin/"
# "C:/Program Files/Apache Group/Apache2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "C:/Program Files/Apache Group/Apache2/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Example:
# Redirect permanent /foo http://www.example.com/bar
# Directives controlling the display of server-generated directory listings.
# IndexOptions: Controls the appearance of server-generated directory
# listings.
IndexOptions FancyIndexing VersionSort
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*
AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core
AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
DefaultIcon /icons/unknown.gif
# AddDescription allows you to place a short description after a file in
# server-generated indexes. These are only displayed for FancyIndexed
# directories.
# Format: AddDescription "description" filename
#AddDescription "GZIP compressed document" .gz
#AddDescription "tar archive" .tar
#AddDescription "GZIP compressed tar archive" .tgz
# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
# HeaderName is the name of a file which should be prepended to
# directory indexes.
ReadmeName README.html
HeaderName HEADER.html
# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing. Shell-style wildcarding is permitted.
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
# DefaultLanguage and AddLanguage allows you to specify the language of
# a document. You can then use content negotiation to give a browser a
# file in a language the user can understand.
# Specify a default language. This means that all data
# going out without a specific language tag (see below) will
# be marked with this one. You probably do NOT want to set
# this unless you are sure it is correct for all cases.
# * It is generally better to not mark a page as
# * being a certain language than marking it with the wrong
# * language!
# DefaultLanguage nl
# Note 1: The suffix does not have to be the same as the language
# keyword --- those with documents in Polish (whose net-standard
# language code is pl) may wish to use "AddLanguage pl .po" to
# avoid the ambiguity with the common suffix for perl scripts.
# Note 2: The example entries below illustrate that in some cases
# the two character 'Language' abbreviation is not identical to
# the two character 'Country' code for its country,
# E.g. 'Danmark/dk' versus 'Danish/da'.
# Note 3: In the case of 'ltz' we violate the RFC by using a three char
# specifier. There is 'work in progress' to fix this and get
# the reference data for rfc1766 cleaned up.
# Catalan (ca) - Croatian (hr) - Czech (cs) - Danish (da) - Dutch (nl)
# English (en) - Esperanto (eo) - Estonian (et) - French (fr) - German (de)
# Greek-Modern (el) - Hebrew (he) - Italian (it) - Japanese (ja)
# Korean (ko) - Luxembourgeois* (ltz) - Norwegian Nynorsk (nn)
# Norwegian (no) - Polish (pl) - Portugese (pt)
# Brazilian Portuguese (pt-BR) - Russian (ru) - Swedish (sv)
# Simplified Chinese (zh-CN) - Spanish (es) - Traditional Chinese (zh-TW)
AddLanguage ca .ca
AddLanguage cs .cz .cs
AddLanguage da .dk
AddLanguage de .de
AddLanguage el .el
AddLanguage en .en
AddLanguage eo .eo
AddLanguage es .es
AddLanguage et .et
AddLanguage fr .fr
AddLanguage he .he
AddLanguage hr .hr
AddLanguage it .it
AddLanguage ja .ja
AddLanguage ko .ko
AddLanguage ltz .ltz
AddLanguage nl .nl
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddLanguage pt .pt
AddLanguage pt-BR .pt-br
AddLanguage ru .ru
AddLanguage sv .sv
AddLanguage zh-CN .zh-cn
AddLanguage zh-TW .zh-tw
# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW
# ForceLanguagePriority allows you to serve a result page rather than
# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# [in case no accepted languages matched the available variants]
ForceLanguagePriority Prefer Fallback
# Commonly used filename extensions to character sets. You probably
# want to avoid clashes with the language extensions, unless you
# are good at carefully testing your setup after each change.
# See http://www.iana.org/assignments/character-sets for the
# official list of        .utf7
AddCharset utf-8       .utf8
AddCharset big5        .big5 .b5
AddCharset EUC-TW      .euc-tw
AddCharset EUC-JP      .euc-jp
AddCharset EUC-KR      .euc-kr
AddCharset shift_jis   .sjis
# AddType allows you to add to or override the MIME configuration
# file mime.types for specific file types.
#AddType application/x-tar .tgz
# AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#AddHandler cgi-script .cgi
# For files that include their own HTTP headers:
#AddHandler send-as-is asis
# For server-parsed imagemap files:
#AddHandler imap-file map
# For type maps (negotiated resources):
# (This is enabled by default to allow the Apache "It Worked" page
# to be distributed in multiple languages.)
AddHandler type-map var
# Filters allow you to process content before it is sent to the client.
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external

I am not expert in these, but please check out the following things and see whether it would solve your issue. (All these changes can be easily rolled back in case I'm wrong :). So make note of what you do)
As per your httpd.conf, you have chosen an automatic configuration of Apache by OWCI installer itself. What it does is create an imageserver.conf file in a separate directory and these settings will be included in your httpd.conf as you can see in the first line: Include "C:/bea/alui/plumtreeconf/".
If you check the imageserver.conf in that location, you would find a line like: Alias /imageserver/ "C:/bea/alui/ptimages/imageserver/". This aliases the original path "C:/bea/alui/ptimages/imageserver/" to /imageserver"
To confirm whether this is done right, check the following:
1. Acces 'http://<server ip / server name / localhost >/' from your browser
This should display the Apache home page (as per your httpd.conf, it uses the default port 80; so no port number required)
2. Access 'http://<server ip>/imageserver/' from your browser
This should display the directory structure (if its not disabled) inside your 'C:/bea/alui/ptimages/imageserver/' folder. Also confirm that all the subfolders are accessible.
3. If all the above is right, it means that your imageserver settings are right. Please check your portalconfig.xml for the correct settings: For example, <setting name="HTTPPort"> should be 7001 in your case. If its something else, change it and restart Weblogic for the settings to take effect.
Hope this helps.

Change Directory server for Portal Server 6.2

Hi there,
I have the following problem with Portal Server 6.2 configuration which hopefully someone here will be able to help me with.
Basically our current setup is the Sun Portal Server 6.2, ID server 6.1 and Directory server all sitting on one (Solaris 9) box. We now wish to separate the Portal / ID server components and the Directory Server component to separate boxes. In portal server 6.0 i think there was a pssetup tool which allowed configuration of a directory server which populated it with the necessary data for portal and ID server. The directory server we will be installing to will not necessarily be a clean install, i.e. it may already be populated with data.
Is there some way therefore to re-configure the existing directory server to allow us to point our portal / ID server at it?
Thanks in advance for any help
Laurence.

This can be done. You need to import the portal/identity server's schema into your new directory server and then export your existing directory server's content and import it into the new one.

How do I restrict access by domain and the rest of the world to the documents in the public_html folder in iPlanet Portal Server?

Hello,
We have multiple domains configured in our iPlanet Portal Server 3 demo environment. In addition we are using the gateway.
In one of these domains the userTemplate.html file is tailored to display Macromedia Flash components at dynamic positions on the page. The logical home for these Flash components (since the portal software cannot find them if we simply store them in iwtDesktop) is somewhere below the /opt/SUNWips/public_html directory.
The problem is that once the file is stored here I can access it if I know the url (http://server:8080/file_path) without being authenticated in the domain.
The allow/deny url policy settings are specific to a domain and seem to have no affect on the rest of the world.
Any advice you can provide is greatly appreciated.
Thanks!

Joel,
If your intent is to block access to the doc root, you can probably use access control lists (acl) to prevent anyone from accessing the files stored under public_html. You can get more information about how to create ACLs from the following URL
http://docs.iplanet.com/docs/manuals/enterprise/41/ag/esaccess.htm#1005439
You can even set up Basic Authentication for access to the direcory or ip based access or any which way you want. I've personally never blocked access to the doc root in portal, so I am not sure what the impact will be.
Hope this helps!

Portal Server 7.2 and Portlet

Hi ,
I have a serious problem with Portlet and Sun Portal 7.2
I don't understand how I can retrive user information (like username,password, email..) from a portlet.
I read about
Map userInfoMap = (Map) request.getAttribute(PortletRequest.USER_INFO);but is always null.
is a portlet.xml problem ?!?!
thanks in advance.
Alessandro
Edited by: Peritus on Aug 6, 2008 2:08 AM

You'll need something like the following in portlet.xml (the attribute names are from the spec):
<user-attribute>
    <description>Given name of user.</description>
    <name>user.name.given</name>
</user-attribute>
<user-attribute>
    <description>Family name of user.</description>
    <name>user.name.family</name>
</user-attribute>And something like the following in a users.properties file which is referenced when you deploy the portlet in Portal Server 7.2:
givenName=user.name.given
sn=user.name.familyWhat happens is the portal server manages the LDAP attribute to portal attribute mapping (eg, user.givenName in LDAP maps to user.name.given in portal) and the portlet container maps the attribute into the read-only USER_INFO map. I'm sure someone will correct my terminology, but it's something like that anyway. Check it out with an LDAP browser if you need to figure what's available in the Directory Server. The result is being able to call something like:
Map userInfoMap = (Map) request.getAttribute(PortletRequest.USER_INFO);
String firstName = (String) userInfoMap.get("user.name.given");
String lastName = (String) userInfoMap.get("user.name.family");Also, roles are handled in a similar way, defining them in portlet.xml, web.xml, and finally mapping in roles.properties at deploy time.
web.xml:
<web-app ... >
     <security-role>
          <description>Sample role.</description>
          <role-name>Sample</role-name>
     </security-role>
</web-app>portlet.xml:
<portlet-app ... >
     <portlet>
          <security-role-ref>
               <role-name>Sample</role-name>
               <role-link>Sample</role-link>
          <security-role-ref/>
     </portlet>
</portlet-app>roles.properties:
cn\=Sample,o\=Sandbox,dc\=example,dc\=com=SampleSo after all that you can do:
if (request.isUserInRole("Sample")) {
    // do stuff...
}HTH,
Rich
Edited by: RichardBarrington on Nov 2, 2008 4:48 PM
description element must be ahead of name element.
Edited by: RichardBarrington on Nov 2, 2008 4:50 PM
Added more complete role example.

Portal Server and Communications Channels

Hello
I would like to create new Portal users using script and ldif file.
How to preconfigure them settings like server. server port, username and password in Communications Channels ?
When i export user to ldif i see sth like that:
sunSSOAdapterConfigurations=undef://username:AQIC5wM2LY4SfcyMZKuECI6cXg%3D%[email protected]:143/?configName=imapmail_Mail&configDesc=imap&smtpServer=server.domain.com&clientPort=8070

Fortunately Communications channels don't use
portal user desktop profile - they use LDAP attributes
to store configuration for each user.
There are several good examples how to create/modify
ldap attributes from a script. See Directory server docs.
Cheers,
Alex :-)

File and Directory Maintenance on OSX Server

Are there any special considerations for using file and directory maintenance utilities such as Disk Warrior or TechTool, etc. when dealing with OSX Server, or can it be handled just like any other volume.
We have all of our data and our user home directories on the server and I would like to run some miantenance on them.
Thanks.

I am no expert on disk utilities.
Personally, I just have a separate 5G partition with a minimal OSX which I boot from once a month (or before a server update) and run Disk Repair & Repair Permissions from.
As far as I know, there is nothing going on on the server that is not going on on a 'normal' OSX machine (at file level mode). The OSX unix offering is miles from the previous OS9 model where the likes of Norton was almost mandatory. The built-in 'periodic' scripts and disk utility 'repair' (see "man fsck" in Terminal) all run at unix level, and have done for years, even before Apple II days!
Although I have both Disk Warrior & TechTool, I don't use them except in an 'emergency' (otherwise called: "try anything").
I would be interested in any other comments though.
-david

Internal and External Portals be hosted & Configured on Same Portal server?

Hi Experts,
Is it possible to host and configure the Internal portal and External Portal on the same portal server?
If yes, kindly provide the inputs.
We have a scenario wherein we have to use the same portal server for both kinds of users (Internal as well as External).
We want to provide separate URLs for both the portals and the datasource for the users management would be different for both the scenarios.
The user managemnet in case of Internal Portal has to be authenticated to an AD server whereas in case of External Portal the user management would be taken care by UME.
Please suggest and share some docs if possible.
Thanks & Regards,
Anurag

Hi,
Can we customise the Portal logon page for both the portals differently?
I've already customised the portal logon page by modifying the UME properties in the Config Tool but that was done keeping in mind the External Portal users. Now, we want to customise the page for Intranet users but with different options at the logon page.
How can we achieve this functionality as any property that we modify in either VA or Config Tool will affect both types of portal pages.
For an eg. we have a Self Registration link for the external users which we do not want for the Intranet users. How is this possible?
If we design a webdynpro java application for the logon page and for authentication purpose, can we call a home page iview on successful authentication?
And with this customised webdynpro java application, can we connect to the AD server for the user authentication?
Best Regards,
Anurag

Creation and deployment of web services on sun portal server

Hi
can you please tell me.
How we can create and deploy web service on sun portal server.
or provide me some document or URL, so that I can proceed forward
Thanks
Vikram

Hi
can you please tell me.
How we can create and deploy web service on sun portal server.
or provide me some document or URL, so that I can proceed forward
Thanks
Vikram

Can you access applications through BEA Portal Server and run applications on different BEA Application Server?

Is it possible to use common Corporate BEA Portal server and able to run different Business Unit applications on different BEA Application Servers?

Hi Akula,
You may want to read this article:
http://dev2dev.bea.com/products/wlportal81/articles/wsrp.jsp
It maybe related to what you want.
Regards,
--alex
Akula Venkata <[email protected]> wrote:
Is it possible to use common Corporate BEA Portal server and able to
run different Business Unit applications on different BEA Application
Servers?

Does Weblogic Portal Server provides caching services and multilingual support

I wanted to know whether Weblogic Portal Server 8.1 has got the facility for caching
services and multilingual support?

is this JSF-portlet.jar bridge file used to create .portlet file from the JSF file so that the portlet file may be added in the portal?
And if you were able to solve the issue by removing the bridge jar file itself, how does that help? if that is the one that would help in creating portlets.
If anyone have been able to create a .portlet file from JSF and deploy in Weblogic 8.1, let me know.
Thanks,
-RAJIV.

Seamless Integration Between Weblogic and Oracle Portal Server

Hi,
Can someone please give me some insight into Seamless integration from Weblogic Portal Server to Oracle Portal Server.
The Scenario is as:
A user logs into the Weblogic Portal, this Portal desktop displays some portlets. Links on these portlets navigate the user to the portlets deployed on Oracle Portal.
Is this feasible, and what version of the 2 servers would support this feature.
Can someone please snd across online resources which deal with my doubt.
many Tx.
Regards,
Mukta

You might want to consider using WSRP to aggregate portlets deployed on
Oracle into WLP. Check edocs and dev2dev for some info on WSRP in WLP.
You can use 8.1 SP3 or later.
Check with Oracle to find out which version of their product offers WSRP
support.
Subbu
Mukta Shetye wrote:
Hi,
Can someone please give me some insight into Seamless integration from Weblogic Portal Server to Oracle Portal Server.
The Scenario is as:
A user logs into the Weblogic Portal, this Portal desktop displays some portlets. Links on these portlets navigate the user to the portlets deployed on Oracle Portal.
Is this feasible, and what version of the 2 servers would support this feature.
Can someone please snd across online resources which deal with my doubt.
many Tx.
Regards,
Mukta

OAM and Directory Server Interaction

I am in the middle of continued fact finding for implementing OAM. One question that has come up is how does OAM use the directory server it is configured to connect to. We would like to use AD as our authentication source but the word is Hell No if OAM is going to try to write data back into the directory server or store data in the directory server as our AD Admins are mandating that OAM will only be given read only, normal user level rights even if it requires write privileges and directory admin rights to function. I have search the manuals and have yet to find a really good explanation of how it works and uses the Database Schema and Directory Server. I suspect it is read only but I need to know ahead of time so I can make everyone aware that were going to have to run multiple directory systems due to the imposed limitation on AD access.

Anybody??? I really need help with this....

PORTAL SERVER 6.0 and Directory Server 5.1 existing

Similar Messages

Maybe you are looking for