Access Manager + Portal Server + Zones + Subnets

Hi
Appreciate your help.
I'm installing Access Manager and Portal Server, this is the environment:
- 3 machines - Solaris 10, 2 local zones per machine
ie
root@global1 # zoneadm list -cv
ID NAME STATUS PATH
0 global running /
1 accesclbp1 running /zone-access
2 portalclbp1 running /zone-portal
Every local zone assigned to Portal Server and the global zone lives on the same VLAN, and every local zone assigned to AM lives on a different VLAN.
The failover of AM is been working rigth now, but I have a problem trying to install the Portal Server's, when I try to connect to AM through the VIP I'm loosing the connections to AM, sometimes I can connect and sometimes is not possible.
Somebody has an environment like this? PS + AM + zones + subnets???

We have this configuration as well.
A few things we have experienced during installation:
1. If Access Manager is https the Portal install fails even the cert is included in the installer JVM.
2. Zones: We use DNS and in nsswitch.conf - hosts and ipnodes were both set to files dns. Once I changed ipnodes to files only problem disappeared.
3. Check that Password Encryption Key is the same across the AMSDKs and the Access Manager servers.

Similar Messages

  • Error 400 when trying to access management portal

    Hi
    When i go to windowsazure.com and click portal in the top navigation bar, i am sent to login.
    When i try to login with my Microsoft account, i am sent to an error message stating that:
    400 The server does not understand the request.
    This happens from multiple pc's and multiple browsers, so i'm guessing its server related.
    Can anyone help?
    BR David Bojsen 
    Regards David

    Hi,
    Based on your description, it seems that you have met an account issue, I would suggest you contact with support, may be it's the best choice for you. Please contact support team by creating a support ticket at
    http://www.windowsazure.com/en-us/support/contact/
    Or if that doesn't work because you don't have an active subscription you will need to contact general customer support to have them create a support ticket for you
    http://support.microsoft.com/gp/customer-service-phone-numbers?wa=wsignin1.0
    Best Regards
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Access manager installation on solaris zone

    Hi
    I have installed the Access manager 7.0, Sun java system app server 8.1, Sun sirectory server 5.2 through JES installer on solaris 10 zone AM55-zone. Installer summarry is below, which shows installtion complete without error, but I am not able to launch the amserver login page.
    Any suggestion, what I did wrong? any thoughts?
    Sid
    Installation Complete
    Software installation has completed successfully. You can view the installation
    summary and log by using the choices below. Summary and log files are available
    in /var/sadm/install/logs/.
    Your next step is to perform the postinstallation configuration and
    verification tasks documented in the Postinstallation Configuration and Startup
    Chapter of the Sun Java(TM) Enterprise System Installation Guide. See: http:
    //docs.sun.com/doc/819-2328.
    Enter 1 to view installation summary and Enter 2 to view installation logs
    [1] {"!" exits} 1
    Installation Summary Report
    Install Summary
    Java Enterprise System : Installed
    Sun Java(TM) System Message Queue 3 2005Q4 Enterprise Edition : Installed
    Sun Java(TM) System Application Server Enterprise Edition 8.1 2005Q4 : Installed
    Sun Java(TM) System Directory Preparation Tool : Installed
    Sun Java(TM) System Directory Server 5 2005Q4 : Installed
    Sun Java(TM) System Access Manager 7 2005Q4 : Installed
    Configuration Data
    Sun Java(TM) System Application Server Enterprise Edition 8.1 2005Q4 :
    Domains and Instance Configuration Directory : /var/opt/SUNWappserver
    Application Server Installation Directory : /opt/SUNWappserver
    Sun Java(TM) System Directory Preparation Tool :
    Directory Preparation Tool Installation Directory : /opt/SUNWcomds
    Sun Java(TM) System Directory Server 5 2005Q4 :
    Directory Server Admin User : admin
    Directory Server Manager : cn=Directory Manager
    Directory Server Identifier : AM55-zone
    Directory Server Port : 389
    Directory Server Root Suffix : dc=ipsolutionshowcase,dc=com
    <--[33%]--[ENTER To Continue]--[n To Finish]--> {"!" exits}
    Directory Server Administration Domain : ipsolutionshowcase.com
    System User : root
    System Group : root
    Existing Configuration Directory : 0
    Configuration Directory Host : AM55-zone.ipsolutionshowcase.com
    Configuration Directory Port : 389
    Configuration Directory Admin User : admin
    Existing User Directory : 0
    User Directory Host : AM55-zone.ipsolutionshowcase.com
    User Directory Port : 389
    User Directory Admin User : admin
    User Directory Suffix : dc=ipsolutionshowcase,dc=com
    Disable Schema Checking : 0
    Add Sample Entries : 0
    Populate Database : 1
    Sun Java(TM) System Access Manager 7 2005Q4 :
    Access Manager Installation Directory : /opt
    Access Manager Protocol : http
    Access Manager Port : 8080
    LDAP User ID : amldapuser
    <--[66%]--[ENTER To Continue]--[n To Finish]--> {"!" exits}
    Administrator User ID : amAdmin
    Web Container : AppServer
    Access Manager Application Server Installation Directory :
    /opt/SUNWappserver/appserver
    Document Root : /var/opt/SUNWappserver/domains/domain1/docroot
    Access Manager Console Host (for Existing console) : AM55-zone.
    ipsolutionshowcase.com
    Access Manager Console Deploy URI : amconsole
    Access Manager Password Deploy URI : ampassword
    Access Manager Host : AM55-zone.ipsolutionshowcase.com
    Access Manager Services Deploy URI : amserver
    Access Manager Cookie Domain List : .ipsolutionshowcase.com
    Access Manager Common Domain Deploy URI : amcommon
    Access Manager Directory Server Host Name : AM55-zone
    Access Manager Directory Server Host : AM55-zone.ipsolutionshowcase.com
    Access Manager Directory Server Port : 389
    Access Manager Directory Root Suffix : dc=ipsolutionshowcase,dc=com
    Access Manager Directory Manager DN : cn=Directory Manager
    Organization Marker Object Class : sunISManagedOrganization
    User Marker Object Class : inetorgperson
    Organization Naming Attribute : o
    User Naming Attribute : uid
    <--[100%]--[ENTER To Continue]--[n To Finish]--> {"!" exits}
    Enter 1 to view installation summary and Enter 2 to view installation logs
    [1] {"!" exits} !
    You have new mail in /var/mail/root
    bash-3.00#
    bash-3.00# cd /var/opt/mps/serverroot/slapd-AM55-zone
    bash-3.00# ./start-slapd

    Thanks samk,
    After the installation, I have started the Directory server,admin,and console with following commands:
    bash-3.00# directoryserver start
    bash-3.00# directoryserver start-admin
    SunONE-WebServer-Enterprise/6.0SP3 B05/19/2004 02:48
    warning: daemon is running as super-user
    [LS ls1] http://AM55-zone.ipsolutionshowcase.com <http://AM55-zone.ipsolutionshowcase.com> , port 390 ready to accept requests
    startup: server started successfully
    bash-3.00# directoryserver startconsole
    Recieved the Login console window,logged in and got the ipsolutionshowcase tree.
    What are the next steps I need to folow in order to launch the Access Manager page?
    Ant thoughts?
    Thanks for ye help
    Sid

  • SSL connection between Dist Auth UI Server and Access Manager

    Hi,
    I have a Dist Auth UI Server installed in Web Server 7 and working properly, but now i want to configure it to talk with Access Manager with a secure port.
    I have configured Access Manager (also deployed in Web Server 7) in a secure port (443). I have requested and installed the server certificate in the Access Manager Web Server instance and also the root entity certificate.
    My question is: how must i configure the UI Server to communicate with the Access Manager Server in a secure way and trust the certificate that the WS of the AM presents ?
    Regards,

    There have been a few reports of the same behaviour with other customers - specifically with the handling of the encoding of "+" characters to " ". It relates to how cookie encoding/decoding is performed (as you have already observed).
    The solution for these customers was the following:
    => AM server/client side:
    Ensure that com.iplanet.am.cookie.encode=false in AMConfig.properties and AMAgent.properties on all systems.
    => AM client (UWC) side:
    - Set <property name="encodeCookies" value="false"/> in /var/opt/SUNWuwc/WEB-INF/sun-web.xml. This will prevent UWC from trying to urldecode the cookie it receives and therefore stops it turning the + into a space e.g.
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE sun-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 Servlet 2.3//EN' 'file:///net/wajra.india.sun.com/export/share/dtd/sun-web-app_2_3-1.dtd'>
    <sun-web-app>
       <property name="encodeCookies" value="false"/>
       <session-config>
          <session-manager/>
       </session-config>
       <jsp-config/>
    <property name="allowLinking" value="true" />
    </sun-web-app>Regards,
    Shane.

  • Multiple portal server instances

    Hello,
    I have one solaris box with JES 2005Q4 installed. I need to set up portal application development environment for multiple developers. I'm thinking about having multiple portal server instances. Is this configuration possible? Should I create multiple directory server and access manager instances as well or is it possible use one with multiple configuration instances?

    Installing multiple instances of portal is only possible if you are installing in a Solaris 10 Whole-Root Zone. Create a new zone for each developer and then install all of the necessary JES components in each zone. This includes Directory, Access Manager, Application Server, and Portal.

  • Sun Java System Portal Server 6.0 FAQs

    Sun Java System Portal Server 6.0 FAQs.
    Author: Sanjeev Agarwal
    Q. How to connect to external URLs from Sun ONE Portal Server? I want to use URL Scrapper for some of external sites/URLs.
    Ans:
    You can connect to external URLs if you have a Proxy Server running.
    If you are using Web Server addition of Sun ONE the Portal Server then
    go to /opt/SUNWam/servers/https-hostname.domainname/config/ dir
    In the jvm12.conf file, enter the followings:
    http.proxyHost=proxyservername.domainname
    http.proxyPort=80 (or the appropriate proxy server port number)
    https.proxyHost=proxyservername.domainname
    https.proxyPort=80 (or the appropriate proxy server port number)
    If you are using Sun ONE AppServer addition of Sun ONE Portal Server then
    go to /var/opt/SUNWappserver/domains/domain1/<server-instance>/config dir
    In the server.xml file, enter the followings:
    <jvm-options>-Dhttp.proxyHost=proxyservername.domainname </jvm-options>
    <jvm-options>-Dhttp.proxyPort=80 (or the appropriate proxy server port number) </jvm-options>
    <jvm-options>-Dhttps.proxyHost=proxyservername.domainname </jvm-options>
    <jvm-options>-Dhttps.proxyPort=80 (or the appropriate proxy server port number) </jvm-options>
    After this modification restart the server.
    Q. Explain all the processes (solaris 8 and S1 Portal Server 6.0) which runs when I start the Sun ONE Portal Server.
    Ans.
    These are the processes that a running Portal Server installation (Sun ONE WebServer addition, without SRAP) generally has by default.
    1. Directory server processes:
    - ns-slapd (LDAP server instance)
    - uxwdog (admin server process) (parent process)
    --- ns-httpd
    ----- ns-httpd
    2. Auth Helper processes:
    - doUnix
    3. Web-Server/Identity-Server/Portal-Server processes:
    As the Portal Server and Identity Server runs as web application on the Web Server, so they share the same JVM and processes.
    - uxwdog (web server admin server process) (parent process)
    --- ns-httpd
    ----- ns-httpd
    (for each web server instance)
    - uxwdog (parent process)
    - ns-httpd
    - ns-httpd
    or (in case of MaxProc=n )
    - uxwdog (parent process)
    --- ns-httpd
    ----- ns-httpd
    ----- ns-httpd
    ----- n
    Q. I have created a custom Provider but getting this error when I access the desktop, what do I do?
    > error in the desktop.debug file:
    > ERROR: DesktopServlet.handleException()
    > java.util.MissingResourceException: Can't find bundle for base name CustomTabContainerProvider,
    Ans:
    It needs a resource bundle for the custom provider. You need to create a file CustomTabContainerProvider.properties (as mentioned in the error message) and put it into the /etc/opt/desktop/classes directory. If you are not using any properties defined in this resource file then it can be a empty file. Have a look on the properties files that bundled containerProviders uses in dir <portal-install-dir>/SUNWps/web-apps/https-<host.domain>/portal/WEB-INF/classes.
    As you are extending JSPTabContainerProvider class, you can just copy the file JSPTabContainerProvider.properties from the above directory after renaming it to the <defined-provider-name>.properties (in your case CustomTabContainerProvider.properties) and move it into /etc/opt/desktop/classes directory.
    Q. what is actually multiple instances of Portal Server means?
    Ans:
    Multiple instance of Portal Server means, you will have more http listeners for the same desktop contents and the same identity profiles stored in a single Directory Server which all the instances share.
    In simple words you can have your Portal Server listening on different http ports, but uses same configuration, desktop and identities.
    It can help you to share the load for Portal Server http requests. The alternate methods are to create more web server virtual server processes (maxProc=n, but in this case the listening port will be 1 only) or use some hardware load balancer.
    You can achieve more from multiple instances if you have a multi level organization, you can change the look and feel of all the instances, images, services, components and can assign each instance to different organization or sub-organization.
    Q. How do I check the availability of the Sun ONE Portal Server/Identity Server services.
    Ans:
    You can check the availability of Sun ONE Identity Server services from following urls.
    http://<host.domainname>:<port>/amserver/sessionservice
    http://<host.domainname>:<port>/amserver/loggingservice
    To know the availability of components of Sun ONE Portal Server like Desktop/providers/Rewriter/Netmail you have to login into desktop. These are not services, but just the programming identities which will work if your Web Server and Identity Server is running.
    Just go to URL http://<server>:<port>/portal/dt , if it shows up that means your portal server is fine, and these entities will work for sure.
    Q. I am able to add the yahoo channels to existing users. But I am getting the weather for London not for local New Jersey. My language pref is to en|en_US and also the server is the default U.S server and not europe. How do I add the cities I want to see on weather channel?
    Ans:
    A Portal user himself (after login) can select what cities he want to see in weather channel.
    Steps:
    - click the edit button of weather channel
    - click on the area you belong to from Available Sections
    - select the cities from Available Cities select box and add them to Your Choices.
    - click finished from select city page and then again click finished from select area page.
    It will come back to the Portal Desktop and you will see all the cities you have selected in the weather channel.
    Q. How to use getContent() method to use in custom jsp providers (developed by ourselves) so that it can be used to retrieve a jsp page. I have already placed the JSP file in the directory structure /etc/opt/SUNWps/desktop/default/channel_dir. But still the jsp is not being displayed.
    Ans:
    You don't have to do anything in the custom JSPProvider's getContent method except the call { return super.getContent(request,response); } . If all you want is just to show your jsp, then create a channel from the default JSPProvider, and edit the property contentPage of that channel from samplecontent.jsp to your jsp name, save the changes and login again. You should see your JSP.
    Q. I want to remove all the buttons (help/edit etc.) from all the channels/one particular channel in my desktop?
    Ans:
    You can hide any buttons you want from any channel.
    These steps show how to hide all the buttons.
    1. Create a channel say "myNetlet" from netlet provider.
    2. Set the channel title to "myNetlet"
    3. Go to the dir /etc/opt/SUNWps/desktop/default/JSPTableContainerProvider and edit the file providerCommands.jsp, and modify the last line :
    from :
    <%=minMaximizeCommand%><%=helpCommand%><%=editCommand%><%=detachAtachCommand%><%=removeCommand%>
    to:
    <% if ( !(title.equals("myNetlet"))){ %><%=minMaximizeCommand%><%=helpCommand%><%=editCommand%><%=detachAtachCommand%><%=removeCommand%><% } %>
    4. Clean the dir mentioned below which contains compiled JSPs. /var/opt/SUNWps/https-<host>.<domain>/portal/tmp/_jsps/_etc/_opt/_SUNWps/_desktop/_default_en/_JSPTableContainerProvider/_html and reload the page.
    Relogin, and you would not see any buttons on "myNetlet" channel. You can customize this logic as per your needs.
    Q. How to change the title of SampleJSP Channel. I tried to change the channel properties title value via iplanet directory Server Access Management GUI. But it is not getting reflected.
    Ans:
    Through Admin console you can change the channel property "title", and as soon as you refresh the page (Shift reload) of relogin in the portal it get's reflected.
    The reason to this problem may be due to the channel property "title" is having "propagate" value as false and you are setting the channel title in the org level display profile not in the user level display profile.
    So better you change the channel name in user's display profile also.
    For this login into admin console and go to :
    - View: "User Management" -> click on organization -> Show: Users
    - click on the blue arrow of that user
    - click on Edit in section Desktop (this will open a window)
    - then change the channel properties same way you do for Organization display profile.
    Q. Login Problem with SunOne Portal 6.0.
    I was able to download and install sun one portal 6 on Solaris 8. The sample portal page came up after installation. However whenever I try to login to the Login channel with "amadmin" and the passphrase I used during installation, it takes me to another page - iPlanet/LDAP authentication page. Here I tried using the same login, but fails every time (the same login page appears). The url that shows is "http://<hostname>/amserver/login?module=dproadmin&goto=/amconsole/base/AMAdminFrame"
    I tried registering myself as a new user as well. This too fails.
    Ans:
    Make sure you are giving fully qualifying the hostname in the url which invoked the desktop. This in fact is documented in the administration documentation. If the hostname is not fully-qualified, the login page goes into an endless mode. Again, the correct url is "http://<fully-qualified-hostname>/portal". Once you get to the desktop, the login and the new user registration works.
    Q. How to send variables/parameters from 1 app to another app deployed on Sun ONE Portal Server? It may be the apps or different JSPs of JSP provider channel.
    How to achieve inter channel communication in Sun ONE Portal Server?
    Ans:
    You can use servlet context object or session, or may be the request object itself to store the information from one channel and use that in another channel. The use of either of these 3 approaches may depend on your requirements. Using session, the information will be available to that user's channels only, using request, the information will be available for that user and that request only and by using ServletContext you can share the information across users and sessions. You can obtain DesktopServlet's ServletContext object inside JSP/JSPProvider.
    Q. I am trying to modify the default desktop JSPs in TableContainerProvider and TabCotntainerProvider dirs, but it is not picking my modified JSPs ? what do I do?
    Ans:
    One easiest way to 100% ensure that it updates all your new jsp pages is to remove all the compiled jsps so that with next request the Sun ONE Portal Server compiles all the jsps and will make sure that your modification will be taken care of in next request.
    Go to /var/opt/SUNWps/https-<instance_name>/portal/tmp/_jsp/_etc/_opt/_SUNWps/_desktop/_default_<locale>/ and remove everything. and access the Portal server, it will be little slow as it has to compile all the JSPs again. Here you will find directories in the name of Containers and Channels, so if you are modifying any particular Container/Channel you can just delete that only. This approach can help a lot during development time.
    Q. What is the location of compiled JSPs in Sun ONE portal Server and what servlet spec does it supports?
    Ans: The Portal server 6.0 runs on Sun ONE Web Server 6.0 sp2, which supports only jdk 1.3 and servlet spec 2.2 only. The Sun ONE Portal Server keeps the compiled jsps of desktop and channels in : /var/opt/SUNWps/https-<instance_name>/portal/tmp/_jsp/_etc/_opt/_SUNWps/_desktop/_default_<locale>/ dir as per the channels/container names.
    Servlet 2.3 is supported if you run the Portal Server edition that runs on Sun ONE Application Server 7.0.
    Q. How do I change jdk for Sun ONE Portal Server to another jdk? I want to change the JDK of only one of my Portal Server instances, is it possible? how?
    Ans:
    Yes you can achieve both.
    A. To change the JDK for all the server instances:
    Open <portal-install-dir>/SUNWam/servers/https-admserv/start-jvm file and modify the first line
    NSES_JDK=/usr/java_1.3.1_04; export NSES_JDK
    to
    NSES_JDK=<your-jdk-location> ; export NSES_JDK
    then open <portal-install-dir>/SUNWam/servers/https-<instance-name>/config/jvm12.conf file of all the server instances and add a line
    jvm.option=-server after the first line
    B. To change the JDK for a particular server instances:
    Make a another copy of the start-jvm file rename it and modify the jdk location in it as mentioned above.
    Open the start script from <portal-install-dir>/SUNWam/servers/https-<instance-name> dir and modify these lines :
    if test -r {SERVER_ROOT}/https-admserv/start-*
    then
    for STARTSCRIPT in {SERVER_ROOT}/https-admserv/start-*
    modify this to
    if test -r {SERVER_ROOT}/https-admserv/<changed_name_of_start-jvm-file>
    then
    for STARTSCRIPT in {SERVER_ROOT}/https-admserv/<changed_name_of_start-jvm-file>
    Note: As Portal Server 6.0 uses Web server 6.0 sp2, jdk 1.4 is not supported.
    Q. How do I create a custom login page or a link, which will just log me into the portal server.
    Ans:
    You can create a custom page in your jsp page, just add this portion of html into your web page :
    <FORM action="http://<server>:<port>/amserver/login?module=<login-module>&page=1" method=post name=login_form2 target=_top>
    Login page using <login-module><br>
    <P>Enter UserId<BR><INPUT name=TOKEN0 size=22></P>
    <P>Enter Password<BR><INPUT name=TOKEN1 size=22 type=password></P>
    <P><INPUT name=Submit type=submit value=Submit> </P>
    </FORM>
    The <login-module> can be LDAP or Unix or Membership which ever you have enabled. Or instead of this you can create a link. For example for LDAP auth module :
    "<a href="http://<server>:<port>/amserver/login?module=LDAP&page=1&TOKEN0=user&TOKEN1=password" target=_top> Login into Portal </a>"
    where user and password are the user credential for the portal server.
    Q. Can I install a portal server pointing to another Identity server? I want to install few postal servers (on different machines) pointing to same identity server, is it possible?
    Ans:
    No, right now the Sun ONE Portal Server is tightly integrated with Sun ONE Identity Server so you can't just install only Sun ONE Portal Server and point it to another Sun ONE Identity Server. You can have a common Directory server if you want.
    Q. I have an application which takes input in from anonymous user and then to complete the request the user than has to login. I am having problem in passing the taken input from anonymous page to logged in user. all the request parameters are lost when I log in. How do i get the request parameters after I log in
    Ans:
    You can create a custom login page and submit the form to "/amserver/login" with a hidden parameter "goto" through which you basically specify which url to go after you log in. So you can use this mechanism to create a query string with all your request parameters you want to pass after login. For example:
    You can create a jsp which take few inputs from user and to complete the request you have to login so it posts the input form to a login jsp and stores the parameters taken from user in a hidden field (goto) :
    <FORM action="/amserver/login?module=LDAP&page=1" method=post name=login_form2 target=_top>
    Login page using LDAP<br>
    <P>Enter UserId<BR><INPUT name=TOKEN0 size=22></P>
    <P>Enter Password<BR><INPUT name=TOKEN1 size=22 type=password></P>
    <INPUT TYPE=HIDDEN NAME="goto" VALUE="/portal/dt?param1=<%=request.getParameter("param1")%>&param2=<%=request.getParameter("param2")%>">
    <P><INPUT name=Submit type=submit value=Submit> </P>
    </FORM>
    After you login through this page both the param1 and param 2 will be available in the request object after you login and you can retrieve them in your application or jsp.
    Q. I have few System.out.println in my jsp which i am using in my JSP provider channel, but when I look at the portal server's /var/opt/SUNWam/debug/desktop.debug file, none are there. I looked at the web server's access and error logs too, but it is not there also. Can somebody tell me how do it get those ? Do we have any other mechanism to put debug logs ?
    Ans
    By default the binary which web server runs is uxwdog which eats up System.out.println output. If you want to see the System.out.println then you need to change the product binary from the start script of the portal server instance.
    - Go to <portal-install-dir>/SUNWam/servers/https-<instance-name> and open the start script
    - Change the PRODUCT_BIN=uxwdog to PRODUCT_BIN=ns-httpd , save the file
    - Run the script ./start to start the portal server
    Note : with ns-httpd ON the server will not leave that shell, and in the same window/shell you will be able to see all your System.out.println statements. To close the server you have to kill the server process with "kill -9 pids" command
    Alternate way is to use api inside your application or jsp:
    <%@page import="com.sun.portal.providers.jsp.JSPProvider, com.sun.portal.providers.*, com.sun.portal.providers.containers.*, com.sun.portal.providers.context.*" %>
    <% JSPProvider p=(JSPProvider)pageContext.getAttribute("JSPProvider");
    ProviderContext pc = p.getProviderContext(); %>
    <%-- after that you can use these lines any where in your jsp --%>
    <%
    pc.debugError("your error msg");
    pc.debugMessage("your msg");
    pc.debugWarning("your warning msg");
    %>
    The particular mgs will be shwon in /var/opt/SUNWam/debug/desktop.debug file as per your "debugLevel" parameter setting in /etc/opt/SUNWps/desktop/desktopconfig.properties file. By default the debugLevel is set to error so only pc.debugError("error msg") will be shown.
    Q. Multipart form (file upload) processing in providers? Is it supported
    Ans:
    The Sun ONE Portal Server's DesktopServlet does not have the ability to process a request with the content encoding type of multipart/form-data. DesktopServlet does not pass the input stream for the request on to the Provider.
    To accomplish handling of multipart/form-data type requests, it is necessary to create a companion servlet or JSP that process the multipart/form-data. This servlet can then pass control back to the Portal channel. The data from the file can be shared between the servlet and the provider by using static Java members or by storing the data in a back-end database and then passing a reference to the data over to the provider.
    Q. After installing the Portal Server I am trying to login as admin, but it is failing and coming back to login page every time. How do I login?
    Ans:
    The Default Admin user is 'amadmin' and the password is the PASSPHRASE you give during Portal Server installation. Try login using these credentials.
    Also in the browser give the complete URL for the Portal Server like : Http://<myhost>.<mydomain>:<port>/amserver/login or Http://<myhost>.<mydomain>:<port>/amconsole. You can't login into portal server's IDSAME console by giving IP Address or just the hostname, also your machine should be listed in the DNS server so that it can resolve the name.
    Q. I installed Sun ONE Portal Server 6.0 some time back, and now I want to know all the installation parameters and user/passwords for whole portal installation. How do I do that?
    Ans:
    The Default Admin user is 'amadmin' and the password is the PASSPHRASE you give during Portal Server installation. Also in the browser give the complete URL for the Portal Server like : Http://<myhost>.<mydomain>:<port>/amserver/login or Http://<myhost>.<mydomain>:<port>/amconsole. You can't login into portal server's IDSAME console by giving IP Address or just the hostname, also your machine should be listed in the DNS server so that it can resolve the name.
    In case you have forgotten the port numbers and PASSPHRASE that you give during installation, you still can see all the information for each component of your Portal Server Installation. The Portal server and it's components like Directory Server, Web Server and IDSAME are installed as Solaris package so the system has all the information for these packages.
    Portal Server : See file /var/sadm/pkg/SUNWps/pkginfo
    Directory Server : See files /var/sadm/pkg/SUNWamds/pkginfo and /var/sadm/pkg/SUNWamdsc/pkginfo
    Web Server : See file /var/sadm/pkg/SUNWamws/pkginfo
    Identity Server : See file /var/sadm/pkg/SUNWamsam/pkginfo
    Note: In any case you should never edit/modify these files.
    Q. Controlling the display of the help (?) button.
    Where are the links/image elements defined for the help/edit/minimize buttons? the leafWrapper.jsp pulls the hashtable out of the HttpRequest, and that hashtable is being used by providerCommands.jsp:
    Hashtable commands = (Hashtable)request.getAttribute("provider_cmds");
    Any idea where this is being set?
    Ans:
    - You can remove the help/edit button of any channel by adding the line into the Channel's properties by editing the Xml of display profile in the admin console.
    <String name="helpURL" value="" advanced="false" merge="replace" lock="false" propagate="true"/>
    <Boolean name="isEditable" value="false" advanced="false" merge="replace" lock="false" propagate="true"/>
    The Attribute 'provider_cmds' is set into /etc/opt/SUNWps/desktop/default/JSPTableContainerProvider/tablecolumn.jsp :
    <dttable:getProviderCommand id="provider_cmds" scope="request" />, and after that only the leafwrapper.jsp is included, but the Hashtable is generated by a class com.sun.portal.providers.util.ProviderCommands.java and made available through taglib classes. So you can't change the generated contents/string in the Hashtable.
    But you can change the default 'alt' text displayed and the images linked to the help/edit icons. As this modification is at Provider level, it will change the icons for all the channels in the desktop.
    Please see the file:
    /opt/SUNWps/web-apps/https-<host>.<domain>/portal/WEB-INF/classes/JSPTABLEContainerProvider.properties.
    Here you will find the mapping. The image location are given from the context root of portal server which is by default : /opt/SUNWps/web-apps/https-<host>.<domain>/portal.
    Q. I have a number of web applications needed to integrate to portal server. Any pointers or tips of what my option is?
    Ans:
    You can very well integrate all your web application with Portal server. Portal Server 6.0 has web container same as Sun ONE web server 6.0 Sp2, which runs on Jdk-1.3.
    If your web applications are just Servlets/Jsps then you can very well port them on Portal server's webserver which supports war module deployment. (infect for Web server the Portal server and Identity server is like a war module.)
    There can be two possibilities in this case, either you put the whole of your application on portal server and make the link available into the desktop via 'Application Provider Channels' or you can create a client to your web application into portal server.
    If your web application is on Sun ONE Application server 7.0 and needs authentication, you can also have SSO. If you just want to show the link of your web application into desktop then you can either use URL Scrapper to show the first page of your web application or use Bookmark channel to provide just the url.
    The easiest way to make a client of your web application is to use JSP Channel using JSPProvider and put your logic into the samplecontents.jsp file or you can create your own custom Provider extending JSPProvider. There can be a lot of different configurations, depending on the web application you want to integrate and your needs
    Q. I removed few channels from the org level display profile but still they are coming to the desktop of users, I had accessed the desktop before. why?
    Ans:
    If you still see any channel after you remove it from the display profile at organization lever, that means you have to edit the user's display profile. So go to admin console and select User from Show: menu and click on the blue arrow near the user. In the right frame under the 'Desktop' category click on the Edit link (right side). This will open user's display profile in a window. Now edit it as per your requirements.

    Unfortunately Web Server 6.0SP2 is no longer available for download.
    If you must use Web Server 6.0, you should use the most current Service Pack. It is backward compatible and contains many performance and security fixes.

  • How to Create a system in portal server

    I am trying to do the tutorial: How to Create a JDBC-based iView for Add/Update/Delete Record.
    Its pre-requisite is: A system – with an alias “JDBC” – defined on your portal server, and mapped to a database.
    Since I am new to VC, I do not know how to create a system, and I also do not know how to access the portal server.
    Please help...

    Hi Makarand,
    Do you have any one who has the access to portal with administrator rights. I am hereby sending you the steps on how to create a system.
    To define a system:
    1. Create a new system; define all its properties
    2. Create a default system alias.
    3. Create a user mapping (from the user you use in VC) to the system alias, using the user\password to the backend system.
    4. TEST the connection in the portal. If the test succeeds, it should be visible in VC discovery panel.
    VC retrieves the systems via the portal.
    You have to define the systems or use the defined systems in the portal you are connected.
    To define systems in the portal:
    System Administration => system configuration => system landscape:
    in the PCD: right click on a folder and Add new system.
    Then you have to define all the mandatory properties: Connector / Was / User management ...
    don’t forget to map your portal user with an R3/JDBC user...
    thank you very much.

  • Cannot acces the login page of Access Manager 7.1 amserver

    I am new to Access Manager 7.1. After a successfull installation on Solaris 10 11/06 x86, SUN Java Directory Server 6 EE, SUN Java Application Server 8.2 i cannot reach the login page of amserver. The Application Server registers properly the Web Applications, the configuration of the Access Manager was good in my best knowledge. The exeption is as follows
    type Exception report
    message
    description The server encountered an internal error () that prevented it from fulfilling this request.
    exception
    javax.servlet.ServletException: AMSetupFilter.doFilter
         com.sun.identity.setup.AMSetupFilter.doFilter(AMSetupFilter.java:100)
    root cause
    com.iplanet.jato.CompleteRequestException
         com.sun.identity.authentication.UI.AuthenticationServletBase.onUncaughtException(AuthenticationServletBase.java:122)
         com.iplanet.jato.ApplicationServletBase.fireUncaughtException(ApplicationServletBase.java:1164)
         com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:639)
         com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.java:459)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
         sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
         sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         java.lang.reflect.Method.invoke(Method.java:585)
         org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
         java.security.AccessController.doPrivileged(Native Method)
         javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
         org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
         java.security.AccessController.doPrivileged(Native Method)
         com.sun.identity.setup.AMSetupFilter.doFilter(AMSetupFilter.java:86)
    note The full stack trace of the root cause is available in the Sun-Java-System/Application-Server logs.
    Could anybody help me to solve this situation.
    Thanks

    Hey,
    were you able to resolve this issue???
    I am getting the same error after I re-installed the SUN suite(including portal,access manager ,directory server etc)
    Please let me know If you can help.!
    Thanks
    Deepak

  • Installing Portal server, does it include App server?

    Hi All,
    I hope that you can give me a pointer on this one.
    I want to use Portal server to develop portlets for .
    when i will install it, would it automatically install Sun Application server with it or do i have to do it seperately.
    I understand there is a Identity Server that must exist.
    Will it be installed too or should i do it manually and then somehow show where app server/identity servers are?
    If so , how can i show portal server where App Server is.
    Thank you all very much
    Serge

    Hi Serge,
    Just run the JES installer and select to install the portal server, the installer will automatically select the pre-requisites. When doing a sandbox installation, just install all components on one server:
    - application server
    - portal server
    - access manager
    - directory server
    Be sure to read the release notes and the JES installation guide.
    Regards, Robert

  • Please help : "Configuring Windows SSO for Sun portal server 7.1"

    Hello friends,
    I have a problem when create Single Sign On ( SSO ) on the portal server 7.0
    If you have configured successfully.Please give me the way you have used.
    Thank you very much.
    DungT
    Related document and information :
    http://docs.sun.com/app/docs/doc/819-4670/6n6qardtu?a=view#gbaqc
    http://forum.java.sun.com/thread.jspa?threadID=5140689&messageID=9519196
    Edited by: dungtran on Mar 13, 2008 4:35 AM

    There is a ZIP Install available for Windows that bundles the Access Manager, Directory Server,and Portal Server in a pre-configured deployment. Try this download instead:
    PS 7.1u1
    [https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_us/-/USD/ViewProductDetail-Start?ProductRef=PortalSvr7.1U1-OTH-G-F@CDS-CDS_SMI]
    PS 7.2
    [https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=PortalSvr7.2-OTH-G-F@CDS-CDS_SMI]
    - Jim

  • Portal Server Admin Console login problem....

    When I installed Sun Java Studio Enterprise 7 (trial edition) I also installed the server package (The second zip file). During the install I was only prompted to enter ID and password my Application server. But I do not know or have an ID and password for the portal server. When I launch the Portal Server Admin Console which is really the Access Manager's Admin console, it prompts me to enter my ID and password. The ID and password I have setup for the Application server does not work. Now my problem is, I cannot access the portal server on my machine. Does any one know how I can find out what my ID and password is? or how I can access the portal server?

    hi,
    I'm a newbie , who has just installed the java enterprise server. i installed it on windows platform and installation was successful. I don't know how to login to the portal server.
    please provide the address of the portal webpage if the one given below is incorrect:
    http://localhost:8080/portal/dt
    which username and password can i use for loggin in ? .....
    what is the default username and password ?
    is the username amadmin ?? if so what is the password ? ...
    kindly help me .....thanks in advance.... :)

  • Portal Server

    Hi,
    I want to know how to determine the number of Users logged on to Portal server?
    and how many of them have a access to Portal server?
    Thanks
    Vijay

    Please check the faq area of the portal wiki (link at the top of the page...)
    Check this thread
    How do I monitor the number of logged on users in EP6.0 SP11?
    U can view currently acitive server sessions at System Administration -> Support -> Wed Dynpro Test Tools -> User Management.
    Cheers,
    Gaurav

  • Problem with second instance of access manager

    Well, after sorting out things with the first install of access manager, I went on to install a second instance on a different host (it's required for delegated admin..)
    Here are the options I used on install:
    Access Manager: Administration (1 of 6)
    Administrator User ID: amAdmin
    Administrator Password [] {"<" goes back, "!" exits}:
    Retype Password [] {"<" goes back, "!" exits}:
    LDAP User ID: amldapuser
    LDAP Password [] {"<" goes back, "!" exits}:
    Retype Password [] {"<" goes back, "!" exits}:
    Password Encryption Key [gFoe4t8UlUW3wEApngAY3S8bCQFVMlGk] {"<" goes back,
    "!" exits}: weW5jtopMLQsODiBZDp+hlEp1/CtbiXX
    Install type (Realm/Legacy) Mode [Legacy] {"<" goes back, "!" exits}:
    Access Manager: Web Container (2 of 6)
    1. Sun Java System Application Server
    2. Sun Java System Web Server
    Select the container to deploy the component and hit enter key [2] {"<" goes
    back, "!" exits}
    Access Manager: Sun Java System Web Server (3 of 6)
    Host Name [zone2.corenode.com] {"<" goes back, "!" exits}:
    Web Server Instance Directory [opt/SUNWwbsvr/https-zone2.corenode.com] {"<"
    goes back, "!" exits}:
    Web Server Port [80] {"<" goes back, "!" exits}:
    Document Root Directory [opt/SUNWwbsvr/docs] {"<" goes back, "!" exits}:
    Secure Server Instance Port [No] {"<" goes back, "!" exits}:
    Access Manager: Web Container for running Access Manager Services(4 of 6)
    Host Name [zone2.corenode.com] {"<" goes back, "!" exits}:
    Services Deployment URI [amserver] {"<" goes back, "!" exits}:
    Common Domain Deployment URI [amcommon] {"<" goes back, "!" exits}:
    Cookie Domain(Assure it is not a top level domain) [.corenode.com] {"<" goes
    back, "!" exits}:
    Administration Console [Yes] {"<" goes back, "!" exits}:
    Console Deployment URI [amconsole] {"<" goes back, "!" exits}:
    Password Deployment URI [ampassword] {"<" goes back, "!" exits}:
    Access Manager: Directory Server Information (5 of 6)
    Directory Server Host [] {"<" goes back, "!" exits}: zone1.corenode.com
    Directory Server Port [] {"<" goes back, "!" exits}: 389
    Directory Root Suffix [dc=corenode,dc=com] {"<" goes back, "!" exits}:
    Directory Manager DN [cn=Directory Manager] {"<" goes back, "!" exits}:
    Directory Manager Password [] {"<" goes back, "!" exits}:
    Access Manager: Directory Server Information (6 of 6)
    Is Directory Server provisioned with user data [No] {"<" goes back, "!"
    exits}? Yes
    Organization Marker Object Class [sunISManagedOrganization] {"<" goes back,
    "!" exits}:
    Organization Naming Attribute [o] {"<" goes back, "!" exits}:
    User Marker Object Class [inetorgperson] {"<" goes back, "!" exits}:
    User Naming Attribute [uid] {"<" goes back, "!" exits}:
    Yes, I am using the same key as was used on host1 for access manager. Yes, access manager on host 1 is quite functional right now. Yes, that directory server works. Now I'm really stumped on what to do! Everything in JES seems to work great except access manager, the exceptions it throws really don't help any at all in troubleshooting.
    Any ideas?

    More info from error logs:
    # pwd
    /var/opt/SUNWam/debug
    # tail -200 amAuth
    04/12/2006 09:56:47:127 AM HST: Thread[main,5,main]
    ERROR: AuthD failed to get auth session
    04/12/2006 09:56:47:165 AM HST: Thread[main,5,main]
    ERROR: AuthD init()
    com.iplanet.dpro.session.SessionException: AuthD failed to get auth session
    at com.sun.identity.authentication.service.AuthD.initAuthSessions(AuthD.java:709)
    at com.sun.identity.authentication.service.AuthD.<init>(AuthD.java:229)
    at com.sun.identity.authentication.service.AuthD.getAuth(AuthD.java:494)
    at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
    at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
    at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
    at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
    at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
    at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
    # tail -200 amSession
    04/12/2006 09:56:47:098 AM HST: Thread[main,5,main]
    ERROR: SessionService.SessionService(): Initialization Failed
    com.iplanet.services.naming.ServerEntryNotFoundException: Cannot find server ID.
    at com.iplanet.services.naming.WebtopNaming.getServerID(WebtopNaming.java:350)
    at com.iplanet.dpro.session.service.SessionService.<init>(SessionService.java:1540)
    at com.iplanet.dpro.session.service.SessionService.getSessionService(SessionService.java:382)
    at com.sun.identity.authentication.service.AuthD.getSS(AuthD.java:685)
    at com.sun.identity.authentication.service.AuthD.initAuthSessions(AuthD.java:706)
    at com.sun.identity.authentication.service.AuthD.<init>(AuthD.java:229)
    at com.sun.identity.authentication.service.AuthD.getAuth(AuthD.java:494)
    at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
    at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
    at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
    at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
    at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
    at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
    04/12/2006 09:56:47:126 AM HST: Thread[main,5,main]
    ERROR: Error creating service session
    java.lang.NullPointerException
    at com.iplanet.dpro.session.service.SessionService.generateEncryptedID(SessionService.java:588)
    at com.iplanet.dpro.session.service.SessionService.generateSessionId(SessionService.java:612)
    at com.iplanet.dpro.session.service.SessionService.newInternalSession(SessionService.java:557)
    at com.iplanet.dpro.session.service.SessionService.getServiceSession(SessionService.java:501)
    at com.iplanet.dpro.session.service.SessionService.getAuthenticationSession(SessionService.java:408)
    at com.sun.identity.authentication.service.AuthD.initAuthSessions(AuthD.java:706)
    at com.sun.identity.authentication.service.AuthD.<init>(AuthD.java:229)
    at com.sun.identity.authentication.service.AuthD.getAuth(AuthD.java:494)
    at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
    at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
    at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
    at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
    at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
    at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
    #

  • Too  Slow - Domino 6.5.4  with access manager agent 2.2 ?

    I don't know how to tune Domino 6.5.4 with access manager agent 2.2?
    I think AMAgent.properties is not good for SSO.
    Please help me to tune it.
    # $Id: AMAgent.properties,v 1.103 2005/09/19 22:08:34 madan Exp $
    # Copyright ? 2002 Sun Microsystems, Inc. All rights reserved.
    # U.S. Government Rights - Commercial software. Government users are
    # subject to the Sun Microsystems, Inc. standard license agreement and
    # applicable provisions of the FAR and its supplements. Use is subject to
    # license terms. Sun, Sun Microsystems, the Sun logo and Sun ONE are
    # trademarks or registered trademarks of Sun Microsystems, Inc. in the
    # U.S. and other countries.
    # Copyright ? 2002 Sun Microsystems, Inc. Tous droits r&#38303;erv&#38303;.
    # Droits du gouvernement am&#38302;icain, utlisateurs gouvernmentaux - logiciel
    # commercial. Les utilisateurs gouvernmentaux sont soumis au contrat de
    # licence standard de Sun Microsystems, Inc., ainsi qu aux dispositions en
    # vigueur de la FAR [ (Federal Acquisition Regulations) et des suppl&#38297;ents
    # ? celles-ci.
    # Distribu? par des licences qui en restreignent l'utilisation. Sun, Sun
    # Microsystems, le logo Sun et Sun ONE sont des marques de fabrique ou des
    # marques d&#38300;os&#38289;s de Sun Microsystems, Inc. aux Etats-Unis et dans
    # d'autres pays.
    # The syntax of this file is that of a standard Java properties file,
    # see the documentation for the java.util.Properties.load method for a
    # complete description. (CAVEAT: The SDK in the parser does not currently
    # support any backslash escapes except for wrapping long lines.)
    # All property names in this file are case-sensitive.
    # NOTE: The value of a property that is specified multiple times is not
    # defined.
    # WARNING: The contents of this file are classified as an UNSTABLE
    # interface by Sun Microsystems, Inc. As such, they are subject to
    # significant, incompatible changes in any future release of the
    # software.
    # The name of the cookie passed between the Access Manager
    # and the SDK.
    # WARNING: Changing this property without making the corresponding change
    # to the Access Manager will disable the SDK.
    com.sun.am.cookie.name = iPlanetDirectoryPro
    # The URL for the Access Manager Naming service.
    com.sun.am.naming.url = http://sportal.yjy.dqyt.petrochina:80/amserver/namingservice
    # The URL of the login page on the Access Manager.
    com.sun.am.policy.am.login.url = http://sportal.yjy.dqyt.petrochina:80/amserver/UI/Login
    # Name of the file to use for logging messages.
    com.sun.am.policy.agents.config.local.log.file = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAgent
    # This property is used for Log Rotation. The value of the property specifies
    # whether the agent deployed on the server supports the feature of not. If set
    # to false all log messages are written to the same file.
    com.sun.am.policy.agents.config.local.log.rotate = true
    # Name of the Access Manager log file to use for logging messages to
    # Access Manager.
    # Just the name of the file is needed. The directory of the file
    # is determined by settings configured on the Access Manager.
    com.sun.am.policy.agents.config.remote.log = amAuthLog.Dominoad.yjy.dqyt.petrochina.80
    # Set the logging level for the specified logging categories.
    # The format of the values is
    #     <ModuleName>[:<Level>][,<ModuleName>[:<Level>]]*
    # The currently used module names are: AuthService, NamingService,
    # PolicyService, SessionService, PolicyEngine, ServiceEngine,
    # Notification, PolicyAgent, RemoteLog and all.
    # The all module can be used to set the logging level for all currently
    # none logging modules. This will also establish the default level for
    # all subsequently created modules.
    # The meaning of the 'Level' value is described below:
    #     0     Disable logging from specified module*
    #     1     Log error messages
    #     2     Log warning and error messages
    #     3     Log info, warning, and error messages
    #     4     Log debug, info, warning, and error messages
    #     5     Like level 4, but with even more debugging messages
    # 128     log url access to log file on AM server.
    # 256     log url access to log file on local machine.
    # If level is omitted, then the logging module will be created with
    # the default logging level, which is the logging level associated with
    # the 'all' module.
    # for level of 128 and 256, you must also specify a logAccessType.
    # *Even if the level is set to zero, some messages may be produced for
    # a module if they are logged with the special level value of 'always'.
    com.sun.am.log.level =
    # The org, username and password for Agent to login to AM.
    com.sun.am.policy.am.username = UrlAccessAgent
    com.sun.am.policy.am.password = LYnKyOIgdWt404ivWY6HPQ==
    # Name of the directory containing the certificate databases for SSL.
    com.sun.am.sslcert.dir = c:/Sun/Access_Manager/Agents/2.2/domino/cert
    # Set this property if the certificate databases in the directory specified
    # by the previous property have a prefix.
    com.sun.am.certdb.prefix =
    # Should agent trust all server certificates when Access Manager
    # is running SSL?
    # Possible values are true or false.
    com.sun.am.trust_server_certs = true
    # Should the policy SDK use the Access Manager notification
    # mechanism to maintain the consistency of its internal cache? If the value
    # is false, then a polling mechanism is used to maintain cache consistency.
    # Possible values are true or false.
    com.sun.am.notification.enable = true
    # URL to which notification messages should be sent if notification is
    # enabled, see previous property.
    com.sun.am.notification.url = http://Dominoad.yjy.dqyt.petrochina:80/amagent/UpdateAgentCacheServlet?shortcircuit=false
    # This property determines whether URL string case sensitivity is
    # obeyed during policy evaluation
    com.sun.am.policy.am.url_comparison.case_ignore = true
    # This property determines the amount of time (in minutes) an entry
    # remains valid after it has been added to the cache. The default
    # value for this property is 3 minutes.
    com.sun.am.policy.am.polling.interval=3
    # This property allows the user to configure the User Id parameter passed
    # by the session information from the access manager. The value of User
    # Id will be used by the agent to set the value of REMOTE_USER server
    # variable. By default this parameter is set to "UserToken"
    com.sun.am.policy.am.userid.param=UserToken
    # Profile attributes fetch mode
    # String attribute mode to specify if additional user profile attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user profile attributes will be introduced.
    # HTTP_HEADER - additional user profile attributes will be introduced into
    # HTTP header.
    # HTTP_COOKIE - additional user profile attributes will be introduced through
    # cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.profile.attribute.fetch.mode=NONE
    # The user profile attributes to be added to the HTTP header. The
    # specification is of the format ldap_attribute_name|http_header_name[,...].
    # ldap_attribute_name is the attribute in data store to be fetched and
    # http_header_name is the name of the header to which the value needs
    # to be assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.profile.attribute.map=cn|common-name,ou|organizational-unit,o|organization,mail|email,employeenumber|employee-
    number,c|country
    # Session attributes mode
    # String attribute mode to specify if additional user session attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user session attributes will be introduced.
    # HTTP_HEADER - additional user session attributes will be introduced into HTTP header.
    # HTTP_COOKIE - additional user session attributes will be introduced through cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.session.attribute.fetch.mode=NONE
    # The session attributes to be added to the HTTP header. The specification is
    # of the format session_attribute_name|http_header_name[,...].
    # session_attribute_name is the attribute in session to be fetched and
    # http_header_name is the name of the header to which the value needs to be
    # assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.session.attribute.map=
    # Response Attribute Fetch Mode
    # String attribute mode to specify if additional user response attributes should
    # be introduced into the request. Possible values are:
    # NONE - no additional user response attributes will be introduced.
    # HTTP_HEADER - additional user response attributes will be introduced into
    # HTTP header.
    # HTTP_COOKIE - additional user response attributes will be introduced through
    # cookies.
    # If not within these values, it will be considered as NONE.
    com.sun.am.policy.agents.config.response.attribute.fetch.mode=NONE
    # The response attributes to be added to the HTTP header. The specification is
    # of the format response_attribute_name|http_header_name[,...].
    # response_attribute_name is the attribute in policy response to be fetched and
    # http_header_name is the name of the header to which the value needs to be
    # assigned.
    # NOTE: In most cases, in a destination application where a "http_header_name"
    # shows up as a request header, it will be prefixed by HTTP_, and all
    # lower case letters will become upper case, and any - will become _;
    # For example, "common-name" would become "HTTP_COMMON_NAME"
    com.sun.am.policy.agents.config.response.attribute.map=
    # The cookie name used in iAS for sticky load balancing
    com.sun.am.policy.am.lb.cookie.name = GX_jst
    # indicate where a load balancer is used for Access Manager
    # services.
    # true | false
    com.sun.am.load_balancer.enable = false
    ####Agent Configuration####
    # this is for product versioning, please do not modify it
    com.sun.am.policy.agents.config.version=2.2
    # Set the url access logging level. the choices are
    # LOG_NONE - do not log user access to url
    # LOG_DENY - log url access that was denied.
    # LOG_ALLOW - log url access that was allowed.
    # LOG_BOTH - log url access that was allowed or denied.
    com.sun.am.policy.agents.config.audit.accesstype = LOG_DENY
    # Agent prefix
    com.sun.am.policy.agents.config.agenturi.prefix = http://Dominoad.yjy.dqyt.petrochina:80/amagent
    # Locale setting.
    com.sun.am.policy.agents.config.locale = en_US
    # The unique identifier for this agent instance.
    com.sun.am.policy.agents.config.instance.name = unused
    # Do SSO only
    # Boolean attribute to indicate whether the agent will just enforce user
    # authentication (SSO) without enforcing policies (authorization)
    com.sun.am.policy.agents.config.do_sso_only = true
    # The URL of the access denied page. If no value is specified, then
    # the agent will return an HTTP status of 403 (Forbidden).
    com.sun.am.policy.agents.config.accessdenied.url =
    # This property indicates if FQDN checking is enabled or not.
    com.sun.am.policy.agents.config.fqdn.check.enable = true
    # Default FQDN is the fully qualified hostname that the users should use
    # in order to access resources on this web server instance. This is a
    # required configuration value without which the Web server may not
    # startup correctly.
    # The primary purpose of specifying this property is to ensure that if
    # the users try to access protected resources on this web server
    # instance without specifying the FQDN in the browser URL, the Agent
    # can take corrective action and redirect the user to the URL that
    # contains the correct FQDN.
    # This property is set during the agent installation and need not be
    # modified unless absolutely necessary to accommodate deployment
    # requirements.
    # WARNING: Invalid value for this property can result in the Web Server
    # becoming unusable or the resources becoming inaccessible.
    # See also: com.sun.am.policy.agents.config.fqdn.check.enable,
    # com.sun.am.policy.agents.config.fqdn.map
    com.sun.am.policy.agents.config.fqdn.default = Dominoad.yjy.dqyt.petrochina
    # The FQDN Map is a simple map that enables the Agent to take corrective
    # action in the case where the users may have typed in an incorrect URL
    # such as by specifying partial hostname or using an IP address to
    # access protected resources. It redirects the browser to the URL
    # with fully qualified domain name so that cookies related to the domain
    # are received by the agents.
    # The format for this property is:
    # com.sun.am.policy.agents.config.fqdn.map = [invalid_hostname|valid_hostname][,...]
    # This property can also be used so that the agents use the name specified
    # in this map instead of the web server's actual name. This can be
    # accomplished by doing the following.
    # Say you want your server to be addressed as xyz.hostname.com whereas the
    # actual name of the server is abc.hostname.com. The browsers only knows
    # xyz.hostname.com and you have specified polices using xyz.hostname.com at
    # the Access Manager policy console, in this file set the mapping as
    # com.sun.am.policy.agents.fqdn.map = valid|xyz.hostname.com
    # Another example is if you have multiple virtual servers say rst.hostname.com,
    # uvw.hostname.com and xyz.hostname.com pointing to the same actual server
    # abc.hostname.com and each of the virtual servers have their own policies
    # defined, then the fqdnMap should be defined as follows:
    # com.sun.am.policy.agents.fqdn.map = valid1|rst.hostname.com,valid2|uvw.hostname.com,valid3|xyz.hostname.com
    # WARNING: Invalid value for this property can result in the Web Server
    # becoming unusable or the resources becoming inaccessible.
    com.sun.am.policy.agents.config.fqdn.map =
    # Cookie Reset
    # This property must be set to true, if this agent needs to
    # reset cookies in the response before redirecting to
    # Access Manager for Authentication.
    # By default this is set to false.
    # Example : com.sun.am.policy.agents.config.cookie.reset.enable=true
    com.sun.am.policy.agents.config.cookie.reset.enable=false
    # This property gives the comma separated list of Cookies, that
    # need to be included in the Redirect Response to Access Manager.
    # This property is used only if the Cookie Reset feature is enabled.
    # The Cookie details need to be specified in the following Format
    # name[=value][;Domain=value]
    # If "Domain" is not specified, then the default agent domain is
    # used to set the Cookie.
    # Example : com.sun.am.policy.agents.config.cookie.reset.list=LtpaToken,
    # token=value;Domain=subdomain.domain.com
    com.sun.am.policy.agents.config.cookie.reset.list=
    # This property gives the space separated list of domains in
    # which cookies have to be set in a CDSSO scenario. This property
    # is used only if CDSSO is enabled.
    # If this property is left blank then the fully qualified cookie
    # domain for the agent server will be used for setting the cookie
    # domain. In such case it is a host cookie instead of a domain cookie.
    # Example : com.sun.am.policy.agents.config.cookie.domain.list=.sun.com .iplanet.com
    com.sun.am.policy.agents.config.cookie.domain.list=
    # user id returned if accessing global allow page and not authenticated
    com.sun.am.policy.agents.config.anonymous_user=anonymous
    # Enable/Disable REMOTE_USER processing for anonymous users
    # true | false
    com.sun.am.policy.agents.config.anonymous_user.enable=false
    # Not enforced list is the list of URLs for which no authentication is
    # required. Wildcards can be used to define a pattern of URLs.
    # The URLs specified may not contain any query parameters.
    # Each service have their own not enforced list. The service name is suffixed
    # after "# com.sun.am.policy.agents.notenforcedList." to specify a list
    # for a particular service. SPACE is the separator between the URL.
    com.sun.am.policy.agents.config.notenforced_list = http://dominoad.yjy.dqyt.petrochina/*.nsf http://dominoad.yjy.dqyt.petrochina/teamroom.nsf/TROutline.gif?
    OpenImageResource http://dominoad.yjy.dqyt.petrochina/icons/*.gif
    # Boolean attribute to indicate whether the above list is a not enforced list
    # or an enforced list; When the value is true, the list means enforced list,
    # or in other words, the whole web site is open/accessible without
    # authentication except for those URLs in the list.
    com.sun.am.policy.agents.config.notenforced_list.invert = false
    # Not enforced client IP address list is a list of client IP addresses.
    # No authentication and authorization are required for the requests coming
    # from these client IP addresses. The IP address must be in the form of
    # eg: 192.168.12.2 1.1.1.1
    com.sun.am.policy.agents.config.notenforced_client_ip_list =
    # Enable POST data preservation; By default it is set to false
    com.sun.am.policy.agents.config.postdata.preserve.enable = false
    # POST data preservation : POST cache entry lifetime in minutes,
    # After the specified interval, the entry will be dropped
    com.sun.am.policy.agents.config.postcache.entry.lifetime = 10
    # Cross-Domain Single Sign On URL
    # Is CDSSO enabled.
    com.sun.am.policy.agents.config.cdsso.enable=false
    # This is the URL the user will be redirected to for authentication
    # in a CDSSO Scenario.
    com.sun.am.policy.agents.config.cdcservlet.url =
    # Enable/Disable client IP address validation. This validate
    # will check if the subsequent browser requests come from the
    # same ip address that the SSO token is initially issued against
    com.sun.am.policy.agents.config.client_ip_validation.enable = false
    # Below properties are used to define cookie prefix and cookie max age
    com.sun.am.policy.agents.config.profile.attribute.cookie.prefix = HTTP_
    com.sun.am.policy.agents.config.profile.attribute.cookie.maxage = 300
    # Logout URL - application's Logout URL.
    # This URL is not enforced by policy.
    # if set, agent will intercept this URL and destroy the user's session,
    # if any. The application's logout URL will be allowed whether or not
    # the session destroy is successful.
    com.sun.am.policy.agents.config.logout.url=
    #http://sportal.yjy.dqyt.petrochina/amserver/UI/Logout
    # Any cookies to be reset upon logout in the same format as cookie_reset_list
    com.sun.am.policy.agents.config.logout.cookie.reset.list =
    # By default, when a policy decision for a resource is needed,
    # agent gets and caches the policy decision of the resource and
    # all resource from the root of the resource down, from the Access Manager.
    # For example, if the resource is http://host/a/b/c, the the root of the
    # resource is http://host/. This is because more resources from the
    # same path are likely to be accessed subsequently.
    # However this may take a long time the first time if there
    # are many many policies defined under the root resource.
    # To have agent get and cache the policy decision for the resource only,
    # set the following property to false.
    com.sun.am.policy.am.fetch_from_root_resource = true
    # Whether to get the client's hostname through DNS reverse lookup for use
    # in policy evaluation.
    # It is true by default, if the property does not exist or if it is
    # any value other than false.
    com.sun.am.policy.agents.config.get_client_host_name = false
    # The following property is to enable native encoding of
    # ldap header attributes forwarded by agents. If set to true
    # agent will encode the ldap header value in the default
    # encoding of OS locale. If set to false ldap header values
    # will be encoded in UTF-8
    com.sun.am.policy.agents.config.convert_mbyte.enable = false
    #When the not enforced list or policy has a wildcard '*' character, agent
    #strips the path info from the request URI and uses the resulting request
    #URI to check against the not enforced list or policy instead of the entire
    #request URI, in order to prevent someone from getting access to any URI by
    #simply appending the matching pattern in the policy or not enforced list.
    #For example, if the not enforced list has the value http://host/*.gif,
    #stripping the path info from the request URI will prevent someone from
    #getting access to http://host/index.html by using the URL http://host/index.html?hack.gif.
    #However when a web server (for exmample apache) is configured to be a reverse
    #proxy server for a J2EE application server, path info is interpreted in a different
    #manner since it maps to a resource on the proxy instead of the app server.
    #This prevents the not enforced list or policy from being applied to part of
    #the URI below the app serverpath if there is a wildcard character. For example,
    #if the not enforced list has value http://host/webapp/servcontext/* and the
    #request URL is http://host/webapp/servcontext/example.jsp the path info
    #is /servcontext/example.jsp and the resulting request URL with path info stripped
    #is http://host/webapp, which will not match the not enforced list. By setting the
    #following property to true, the path info will not be stripped from the request URL
    #even if there is a wild character in the not enforced list or policy.
    #Be aware though that if this is set to true there should be nothing following the
    #wildcard character '*' in the not enforced list or policy, or the
    #security loophole described above may occur.
    com.sun.am.policy.agents.config.ignore_path_info = false
    # Override the request url given by the web server with
    # the protocol, host or port of the agent's uri specified in
    # the com.sun.am.policy.agents.agenturiprefix property.
    # These may be needed if the agent is sitting behind a ssl off-loader,
    # load balancer, or proxy, and either the protocol (HTTP scheme),
    # hostname, or port of the machine in front of agent which users go through
    # is different from the agent's protocol, host or port.
    com.sun.am.policy.agents.config.override_protocol =
    com.sun.am.policy.agents.config.override_host =
    com.sun.am.policy.agents.config.override_port =
    # Override the notification url in the same way as other request urls.
    # Set this to true if any one of the override properties above is true,
    # and if the notification url is coming through the proxy or load balancer
    # in the same way as other request url's.
    com.sun.am.policy.agents.config.override_notification.url =
    # The following property defines how long to wait in attempting
    # to connect to an Access Manager AUTH server.
    # The default value is 2 seconds. This value needs to be increased
    # when receiving the error "unable to find active Access Manager Auth server"
    com.sun.am.policy.agents.config.connection_timeout =
    # Time in milliseconds the agent will wait to receive the
    # response from Access Manager. After the timeout, the connection
    # will be drop.
    # A value of 0 means that the agent will wait until receiving the response.
    # WARNING: Invalid value for this property can result in
    # the resources becoming inaccessible.
    com.sun.am.receive_timeout = 0
    # The three following properties are for IIS6 agent only.
    # The two first properties allow to set a username and password that will be
    # used by the authentication filter to pass the Windows challenge when the Basic
    # Authentication option is selected in Microsoft IIS 6.0. The authentication
    # filter is named amiis6auth.dll and is located in
    # Agent_installation_directory/iis6/bin. It must be installed manually on
    # the web site ("ISAPI Filters" tab in the properties of the web site).
    # It must also be uninstalled manually when unintalling the agent.
    # The last property defines the full path for the authentication filter log file.
    com.sun.am.policy.agents.config.iis6.basicAuthentication.username =
    com.sun.am.policy.agents.config.iis6.basicAuthentication.password =
    com.sun.am.policy.agents.config.iis6.basicAuthentication.logFile = c:/Sun/Access_Manager/Agents/2.2/debug/C__Lotus_Domino/amAuthFilter

    Hi,
    I installed opensso (so Sun Java(TM) System Access Manager 7.5) and the agent for Domino 6.5.4 and I have the message in logs "amAgent"
    2007-07-11 18:40:16.119 Error 1708:3dbcf768 PolicyAgent: render_response(): Entered.
    I have the box to identify but it doesnot connect me on my opensso server.
    It still identify with Domino's server
    Thanks for your response
    Thomas

  • Sun Java System Access Manager 7.1 config. failed during installation

    {color:#0000ff}Hi,
    I have installed sun java communication suite 5 on a single host on sun solaris 10.
    I have installed required packages and it works fine.
    But as per organization need, I have to change domain name.
    So i have uninstalled everything and tried to install again with new domain name.
    I have made proper entries in hosts file and resolve.conf file.
    But duing the first phase of installation only , i failed in configuring access manager 7.1
    I have also cerate same scenario in my test environment, but everytime i face the same error.
    and sun java access manager 7.1 fails in first stage of installation only.
    So would like to know the proper installation procedure while i change the domain name on same hardware...
    I have checked both installation logs & summary logs.
    But no error, no failed , no severe.
    Attached is the summary of installation logs.
    Summary Logs :
    Installation Summary Report
    Install Summary
    Sun Java(TM) Communications Suite : Installed
    Sun Java(TM) System Web Server 7.0 : Installed, Configured
    Java DB : Installed, Configure After Install
    Sun Java(TM) System Message Queue 3.7 UR1 : Installed
    Sun Java(TM) System Monitoring Console 1.0 : Installed, Configure After Install
    Sun Java(TM) System Directory Preparation Tool : Installed
    Sun Java(TM) System Directory Server Enterprise Edition 6.0 : Installed, Configured
    Sun Java(TM) System Access Manager 7.1 : Installed, Configuration Failed
    Sun Java(TM) System Messaging Server 6.3 : Installed, Configure After Install
    Sun Java(TM) System Communications Express 6 : Installed, Configure After Install
    Communication Services Delegated Administrator : Installed, Configure After Install
    Configuration Data
    Sun Java(TM) System Web Server 7.0 :
    Web Server Instance installation Directory : /var/opt/SUNWwbsvr7
    Web Server installation Directory : /opt
    Web Server Administration Server Host : RADAGWMSG221.myreliancemail.com
    Web Server Admin Server Mode : true
    Web Server only CLI installation : false
    Sun Java(TM) System Directory Preparation Tool :
    Directory Preparation Tool Installation Directory : /opt/SUNWcomds
    Sun Java(TM) System Directory Server Enterprise Edition 6.0 :
    Directory Server Installation Directory : /opt/SUNWdsee
    Sun Java(TM) System Access Manager 7.1 :
    Access Manager Installation Directory : /opt
    Access Manager Protocol : http
    Access Manager Port : 80
    LDAP User ID : amldapuser
    Administrator User ID : amAdmin
    Web Container : WebServer
    Access Manager Web Server Host Name : RADAGWMSG221.myreliancemail.com
    Access Manager Web Server Instance Directory : /var/opt/SUNWwbsvr7/https-RADAGWMSG221.myreliancemail.com
    Access Manager Web Server Port : 80
    Access Manager Console Host (for Existing console) : RADAGWMSG221.myreliancemail.com
    Access Manager Console Deploy URI : amconsole
    Access Manager Password Deploy URI : ampassword
    Access Manager Host : RADAGWMSG221.myreliancemail.com
    Access Manager Console Port(for Existing console) : 80
    Access Manager Services Deploy URI : amserver
    Access Manager Cookie Domain List : .myreliancemail.com
    Access Manager Common Domain Deploy URI : amcommon
    Access Manager Directory Server Host Name : RADAGWMSG221
    Access Manager Directory Server Host : RADAGWMSG221.myreliancemail.com
    Access Manager Directory Server Port : 389
    Access Manager Directory Root Suffix : o=rmail
    Access Manager Directory Manager DN : cn=Directory Manager
    Organization Marker Object Class : sunISManagedOrganization
    User Marker Object Class : inetorgperson
    Organization Naming Attribute : o
    User Naming Attribute : uid
    Sun Java(TM) System Messaging Server 6.3 :
    Messaging Server Installation Directory : /opt/SUNWmsgsr
    Sun Java(TM) System Communications Express 6 :
    Communications Express Installation Directory : /opt/SUNWuwc
    Communication Services Delegated Administrator :
    Communication Services Delegated Administrator Installation Directory : /opt/SUNWcomm
    {color}

    Rushi-Reliance wrote:
    Kindly let us know how to proceed further as we are waiiting some reply from your team.As I already advised in your previous posting (http://forums.sun.com/thread.jspa?threadID=5359095), you are best off re-installing solaris from scratch and installing Communication Suite 6 update 1 if you cannot get Access Manager 7.1 configured.
    Regards
    Shane.

Maybe you are looking for

  • Problem with IWDTable in webDynpro

    Hi, I am using IWDTable ui element in my web dynpro application to display records, it works fine with IE-6 & IE-7, but in Mozilla firefox, if I click on the scroll buttons nothing happens. I am using NWDS - 7.0.9, Mozilla - 2.0.0 & WAS - 6.40 How to

  • [Solved] Gnome 3.14 crashes on session start

    Hello, I'm currently experimenting issues on my PC after making an update to gnome 3.14. After the update, I'm no longer able to launch any gnome session. GDM seems to work fine, but after the login the session launch always crash as I get the famous

  • Could I be refused Applecare if I was to buy a MacBook Pro from Ebay?

    So, I'm looking to buy a MacBook Pro. Only problem is, I'd rather not have to spend the £1000 I'd need to do so.. Mainly because I haven't exactly got it all, and even if I do, I'd rather not spend it all.. I've been browsing ebay looking at Pros for

  • How to trigger an ABAP program in a Process chain

    Hello Forum, 1. In a process chain, if a program fails, how can we re-run it? 2. If the process preceeding the ABAP program fails, how can we start the program? 3. If an Infospoke fails in a process chain, how can we trigger that? Thank you, Its my p

  • Pricing , freight conditon type, import procedure in pricing , taxes

    I understood the pricing , but what with some exercises from where get this? How many conditon type will be used in MM ? <b>pricing , freight conditon type, import procedure in pricing , taxes</b> which conditon types used ? what make the settings in