Multiple proxy servers and session replication

          Hi,
          I'm in the middle of testing the 5.1sp10 that I set up recently.
          Say I have PROXY1 and PROXY2, connecting to the object layer.
          First, I point my browser to https://PROXY1/application. I did some stuff there
          that updated the session. Then I pointed my browser to https://PROXY2/application.
          The session was not replicated. Is this a normal behavior?
          What I thought I did was simulate DNS round-robin. I thought since the cookie
          knows which is the master and slave servers, the proxy can read the cookie, and
          I can continue with the session. Do I have to actually setup the DNS to do this?
          Thanks.
          

No, that did not simulate a round robin. The change in server invalidates
          (in this case, makes invisible) the cookie.
          In your hosts file, add (with the correct names/addresses)
          192.168.0.17 proxy1
          192.168.0.18 proxy2
          Peace,
          Cameron Purdy
          Tangosol Inc.
          Tangosol Coherence: Clustered Coherent Cache for J2EE
          Information at http://www.tangosol.com/
          "Rudy" <[email protected]> wrote in message
          news:3c152f6d$[email protected]..
          >
          > Hi,
          >
          > I'm in the middle of testing the 5.1sp10 that I set up recently.
          >
          > Say I have PROXY1 and PROXY2, connecting to the object layer.
          > First, I point my browser to https://PROXY1/application. I did some stuff
          there
          > that updated the session. Then I pointed my browser to
          https://PROXY2/application.
          > The session was not replicated. Is this a normal behavior?
          >
          > What I thought I did was simulate DNS round-robin. I thought since the
          cookie
          > knows which is the master and slave servers, the proxy can read the
          cookie, and
          > I can continue with the session. Do I have to actually setup the DNS to
          do this?
          >
          > Thanks.
          

Similar Messages

  • Application Server slowdown with multiple proxy servers ?

    Our environment has our iAS boxes talking to iWS web servers which are front-ended with iPlanet Proxy servers (Proxy 3.53 I believe). We are seeing significant slowdown if we try and hit our web apps through the proxy as opposed to going directly to the web server (bypassing the proxy servers). One of our "proxy" guys recalls hearing that there is an issue with the app server's handling of sessions if requests from the same user come in to the web server (and by extension the app server) from multiple proxy servers with different ip's. Has any body ever encountered this or does any body know if the app server has an issue handling the same sessions whose requests come from different ip addresses (different proxies)?

    The proxy work with HTTP 1.0 and the webserver with HTTP 1.1.
    This difference could be the cause of your problems.
    "David Fuelling" <[email protected]> escribio en el mensaje
    news:[email protected]..
    Our environment has our iAS boxes talking to iWS web servers which are
    front-ended with iPlanet Proxy servers (Proxy 3.53 I believe). We
    are seeing significant slowdown if we try and hit our web apps through
    the proxy as opposed to going directly to the web server (bypassing
    the proxy servers). One of our "proxy" guys recalls hearing that
    there is an issue with the app server's handling of sessions if
    requests from the same user come in to the web server (and by
    extension the app server) from multiple proxy servers with different
    ip's. Has any body ever encountered this or does any body know if the
    app server has an issue handling the same sessions whose requests come
    from different ip addresses (different proxies)?
    Try our New Web Based Forum at http://softwareforum.sun.com
    Includes Access to our Product Knowledge Base!

  • Running multiple proxy servers

     

              Hi,
              I am aware that I cannot use a product like Central Dispatch to balance load
              between multiple WLS instances. I understand that I should use WLS as a
              proxy in front of a cluster of WLS instances.
              If I deploy mulitple WLS proxies to refer to a singel cluster of WLS, could I use
              the Global Dispatch product from Resonate to 1) ensure that load is balanced
              appropriately across the different proxies and 2) forward requests to a "holding"
              pen if
              the cluster is overloaded.
              If I use Round-robin DNS in front of the 2 proxies, then some users would
              need to explicitly point to one, or the other proxy. Is this correct?
              If I use Round-robin DNS in front of the 2 proxies, then I cannot control the
              number of users which end up on each of the 2 proxies. Is this correct?
              Thanks,
              Rob
              Prasad Peddada wrote:
              > As long as the proxy servers are configured the same way it is possible.
              >
              > Regards
              > Prasad
              >
              > Matias Pelenur wrote:
              >
              > > Hi,
              > > In the weblogic documentation it says that "When using in-memory state
              > > replication, your WebLogic Cluster must live behind one -->or more<-- proxy
              > > servers." What needs to be done in weblogic.properties, etc, if we want to
              > > have two proxy servers instead of just one? The scenario I'm thinking of is
              > > two proxy servers, with DNS round-robin so that incoming requests will come
              > > to either of the proxy servers, and then both proxy servers redirecting
              > > requests to a series of weblogic servers running on a cluster. So both proxy
              > > servers would need to know where to redirect a particular request, even if
              > > the other proxy server handled the request first.... Is this possible?
              > >
              > > I hope this is clear enough.
              > >
              > > Thanks,
              > > Matias
              

  • Proxy servers and the "cannot publish" error - v.1.1.2

    Using the latest iWeb (1.1.2), attempts to publish my work to my .Mac account resulted in the infamous "publish error." I then came across this KB article:
    http://docs.info.apple.com/article.html?artnum=303927
    I turned off my proxy access in the Network settings, and voila, publishing was successful. But now, I'm circumventing my much-needed proxy.
    It's been suggested in other threads here that proxies aren't a problem if one's iDisk is accessible through it. This is not the case. With the proxy, iDisk access is fine, it's only iWeb publishing that is a problem.
    Any way to keep my proxy and still publish with .Mac?

    iDisk access and iWeb publishing ARE indeed different activities. They are similar in that they both utilize the WebDAV protocol over Port 80, but they are different in their individual requirements for back and forth communications with the .Mac servers in terms of how soon or in what timeframe they expect to hear confirmation of transfer back from the server.
    It is apparent to me that the network timeout threshold for copying something to iDisk is a lot longer than that for publishing through iWeb. In fact, I would say that iWeb has become a lot more stringent with network timeouts ever since it was updated from 1.0 to 1.1.
    Anything in between your computer and the .Mac servers contributes to network latency. There are both software and hardware contributions to this latency. Proxy servers, like routers, can be software or hardware based. Software-based latency is most often greater than hardware-based latency.
    I would guess that removing any kind of latency "generating" obstacles within your control would likely improve iWeb function and decrease the incidence of publish errors. Some of these obstacles can include background processes, busy LAN activity (like VOIP use or streaming music/video or online gaming), wireless access points, proxy servers, and routers.
    On the other hand, I also think that if Apple increased iWeb's network timeout threshold, that most of the publishing errors that people experience could be eliminated.

  • Is it possible to deploy SharePoint or its Service Applications on: multiple DB-Servers and multiple SQL Instances?

    Hello Forum,
    We have a SharePoint 2013 farm (Enterprise edition) that uses one single SQL Server 2012 (Standard edition). That statement means: All my SharePoint DBs e.g. (Config, Admin, Content, and Service Apps) DBs are hosted and running onto one single instance e.g.
    Server1\SQLInstance1.
    We have some new requirements to install and configure BI tools such as: PerformancePoint services and PowerPivot. BI tools require either SQL Server 2012 Enterprise or BI editions, and we do NOT want to upgrade our current SQL Server1\SQLInstance1
    Instead, We have other separate SQL Server instance which is enterprise edition let's name it (ServerX\InstanceX) that is running standalone, and we are thinking or using it, and my 2 questions are:
    1) Can we use this other separate
    SQL Server instance which is enterprise edition to host the create and hosts the DBs of PerformancePoint services and PowerPivot ?
    2) My second question is the same: Can I create PerformancePoint services application in my SharePoint farm, But in the Database Server field, I fill up
    the details of the other DB server ServerX\InstanceX  which is the one that is SQL
    enterprise edition ? Will this work ?
    Any official Microsoft resources/links tell that it is possible to deploy SharePoint or its service applications on multiple DB-Servers and multiple SQL Instances?

    Thank you Alex and Anil,
    What are the ramifications of that?
    I mean, Assuming that I have created such a farm where most of SarePoint DBs in Standard SQL instance while the PerformancePoint service application and others e.g. PowerPivot and reporting service are deployed and configured onto other Enterprise SQL instance.
    Are there any recommendations or concerns that you would like to draw my attention to ?

  • Multiple LDAP Servers and Attribute-Based Data Partitioning

    Hello
    We currently want to implement following szenario on Netweaver 2004s. From the
    following SAP Help documentation we want attribute based data partitioning:
    http://help.sap.com/saphelp_nw70/helpdata/EN/4e/4d0d40c04af72ee10000000a1550b0/frameset.htm
    The difference to the SAP document is that we want a distribution of attributes over
    multiple LDAP servers. So we tried to fit that concept into xml. see attached xml source.
    The Portal finds both LDAP Systems but it is NOT that the useres are beeing merged
    but they appear as two distict users in the portal UME. If you do a lookup in the portal
    usernamagent system you get and see two users.
    User1: unique ID = USER.Datasource1.uid
    User2: unique ID = USER.Datasource2.uid
    Obviously the UME system was not able to merge that information of the two distict
    LDAP Systems. MSADS and Lotus Notes.
    Hence my questions:
    1) is it possible to distribute attributes over multiple ldap data sources
    2) any ideas why UME constructs two different users based in Datasource ID's specified in XML
    Thanks for any contributions or ideas,
    Ulrich Scherb
    <?xml version="1.0" encoding="UTF-8"?>
    <dataSources>
        <dataSource id="PRIVATE_DATASOURCE"
                    className="com.sap.security.core.persistence.datasource.imp.DataBasePersistence"
                    isReadonly="false"
                    isPrimary="true">
            <homeFor>
                <principals>
                     <principal type="group"/>
                     <principal type="user"/>
                     <principal type="account"/>
                    <principal type="team"/>
                    <principal type="ROOT" />
                    <principal type="OOOO" />
                </principals>
            </homeFor>
            <notHomeFor/>
            <responsibleFor>
                <principals>
                     <principal type="group"/>
                     <principal type="user"/>
                     <principal type="account"/>
                    <principal type="team"/>
                    <principal type="ROOT" />
                    <principal type="OOOO" />
                </principals>
            </responsibleFor>
            <privateSection>
            </privateSection>
        </dataSource>
        <dataSource id="NOTES_LDAP"
              className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence"
              isReadonly="true"
              isPrimary="true">
              <homeFor/>
              <responsibleFor>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user"/>
                             <attribute name="logonalias"/>
                             <attribute name="j_password"/>
                             <attribute name="userid"/>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal"/>
                       </nameSpace>
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname" populateInitially="true"/>
                             <attribute name="lastname" populateInitially="true"/>
                             <attribute name="email"/>
                             <attribute name="uniquename" populateInitially="true"/>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER"/>
                        </nameSpace>
                   </principal>
              </responsibleFor>
              <attributeMapping>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user">
                                  <physicalAttribute name="uid"/>
                             </attribute>
                             <attribute name="logonalias">
                                  <physicalAttribute name="uid"/>
                             </attribute>
                             <attribute name="j_password">
                                  <physicalAttribute name="unicodepwd"/>
                             </attribute>
                             <attribute name="userid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal">
                                 <physicalAttribute name="uid"/>
                            </attribute>
                       </nameSpace>                    
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname">
                                  <physicalAttribute name="givenname"/>
                             </attribute>
                             <attribute name="lastname">
                                  <physicalAttribute name="sn"/>
                             </attribute>
                             <attribute name="uniquename">
                                  <physicalAttribute name="uid"/>
                             </attribute>
                             <attribute name="loginid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                             <attribute name="email">
                                  <physicalAttribute name="mail"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER">
                                  <physicalAttribute name="sapusername"/>
                             </attribute>
                        </nameSpace>
                   </principal>
              </attributeMapping>
            <privateSection>
                   <ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
                   <ume.ldap.access.server_name>ldap1</ume.ldap.access.server_name>
                   <ume.ldap.access.server_port>389</ume.ldap.access.server_port>
                   <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
                   <ume.ldap.access.user>xxxxx</ume.ldap.access.user>
                   <ume.ldap.access.password>xxxxx</ume.ldap.access.password>
                   <ume.ldap.access.base_path.user>O=SMT_TEST</ume.ldap.access.base_path.user>
                   <ume.ldap.record_access>TRUE</ume.ldap.record_access>
                   <ume.ldap.unique_uacc_attribute>uid</ume.ldap.unique_uacc_attribute>
                   <ume.ldap.unique_user_attribute>uid</ume.ldap.unique_user_attribute>
                   <ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
                   <ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
                   <ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
                   <ume.ldap.access.objectclass.user>person</ume.ldap.access.objectclass.user>
                   <ume.ldap.access.objectclass.uacc>person</ume.ldap.access.objectclass.uacc>
                   <ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
                   <ume.ldap.access.auxiliary_naming_attribute.user>uid</ume.ldap.access.auxiliary_naming_attribute.user>
                   <ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
                   <ume.ldap.access.auxiliary_naming_attribute.uacc>uid</ume.ldap.access.auxiliary_naming_attribute.uacc>
              </privateSection>
         </dataSource>
        <dataSource id="CORP_LDAP"
              className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence"
              isReadonly="true"
              isPrimary="true">
              <homeFor/>
              <responsibleFor>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user"/>
                             <attribute name="logonalias"/>
                             <attribute name="j_password"/>
                             <attribute name="userid"/>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal"/>
                            <attribute name="realm"/>
                            <attribute name="domain"/>
                       </nameSpace>
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname" populateInitially="true"/>
                             <attribute name="displayname" populateInitially="true"/>
                             <attribute name="lastname" populateInitially="true"/>
                             <attribute name="fax"/>
                             <attribute name="title"/>
                             <attribute name="department"/>
                             <attribute name="description"/>
                             <attribute name="mobile"/>
                             <attribute name="telephone"/>
                             <attribute name="streetaddress"/>
                             <attribute name="uniquename" populateInitially="true"/>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER"/>
                        </nameSpace>
                   </principal>
                   <principal type="group">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="displayname" populateInitially="true"/>
                             <attribute name="description" populateInitially="true"/>
                             <attribute name="uniquename"/>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE"/>
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.bridge">
                             <attribute name="dn"/>
                        </nameSpace>
                   </principal>
              </responsibleFor>
              <attributeMapping>
                   <principal type="account">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="j_user">
                                  <physicalAttribute name="samaccountname"/>
                             </attribute>
                             <attribute name="logonalias">
                                  <physicalAttribute name="samaccountname"/>
                             </attribute>
                             <attribute name="j_password">
                                  <physicalAttribute name="unicodepwd"/>
                             </attribute>
                             <attribute name="userid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                        </nameSpace>
                       <nameSpace name="com.sap.security.core.authentication">
                            <attribute name="principal">
                                 <physicalAttribute name="samaccountname"/>
                            </attribute>
                            <attribute name="realm">
                                 <physicalAttribute name="*null*"/>
                            </attribute>
                            <attribute name="domain">
                                 <physicalAttribute name="*null*"/>
                            </attribute>
                       </nameSpace>                    
                   </principal>
                   <principal type="user">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="firstname">
                                  <physicalAttribute name="givenname"/>
                             </attribute>
                             <attribute name="displayname">
                                  <physicalAttribute name="displayname"/>
                             </attribute>
                             <attribute name="lastname">
                                  <physicalAttribute name="sn"/>
                             </attribute>
                             <attribute name="fax">
                                  <physicalAttribute name="facsimiletelephonenumber"/>
                             </attribute>
                             <attribute name="uniquename">
                                  <physicalAttribute name="samaccountname"/>
                             </attribute>
                             <attribute name="loginid">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                             <attribute name="mobile">
                                  <physicalAttribute name="mobile"/>
                             </attribute>
                             <attribute name="telephone">
                                  <physicalAttribute name="telephonenumber"/>
                             </attribute>
                             <attribute name="department">
                                  <physicalAttribute name="ou"/>
                             </attribute>
                             <attribute name="description">
                                  <physicalAttribute name="description"/>
                             </attribute>
                             <attribute name="streetaddress">
                                  <physicalAttribute name="postaladdress"/>
                             </attribute>
                             <attribute name="pobox">
                                  <physicalAttribute name="postofficebox"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
                                  <physicalAttribute name="memberof"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="$usermapping$">
                             <attribute name="REFERENCE_SYSTEM_USER">
                                  <physicalAttribute name="sapusername"/>
                             </attribute>
                        </nameSpace>
                   </principal>
                   <principal type="group">
                        <nameSpace name="com.sap.security.core.usermanagement">
                             <attribute name="displayname">
                                  <physicalAttribute name="displayname"/>
                             </attribute>
                             <attribute name="description">
                                  <physicalAttribute name="description"/>
                             </attribute>
                             <attribute name="uniquename" populateInitially="true">
                                  <physicalAttribute name="cn"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.usermanagement.relation">
                             <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE">
                                  <physicalAttribute name="member"/>
                             </attribute>
                             <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
                                  <physicalAttribute name="memberof"/>
                             </attribute>
                        </nameSpace>
                        <nameSpace name="com.sap.security.core.bridge">
                            <attribute name="dn">
                                  <physicalAttribute name="*null*"/>
                             </attribute>
                        </nameSpace>
                   </principal>
              </attributeMapping>
            <privateSection>
                   <ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
                   <ume.ldap.access.server_name>ldap2</ume.ldap.access.server_name>
                   <ume.ldap.access.server_port>389</ume.ldap.access.server_port>
                   <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
                   <ume.ldap.access.user>yyyyy</ume.ldap.access.user>
                   <ume.ldap.access.password>yyyyy</ume.ldap.access.password>
                   <ume.ldap.access.base_path.user>O=SMT_TEST</ume.ldap.access.base_path.user>
                   <ume.ldap.access.base_path.grup>O=SMT_TEST</ume.ldap.access.base_path.grup>
                   <ume.ldap.record_access>TRUE</ume.ldap.record_access>
                   <ume.ldap.unique_uacc_attribute>samaccountname</ume.ldap.unique_uacc_attribute>
                   <ume.ldap.unique_user_attribute>samaccountname</ume.ldap.unique_user_attribute>
                   <ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
                   <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
                   <ume.ldap.access.flat_group_hierachy>true</ume.ldap.access.flat_group_hierachy>
                   <ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
                   <ume.ldap.access.dynamic_groups>false</ume.ldap.access.dynamic_groups>
                   <ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
                   <ume.ldap.access.objectclass.user>User</ume.ldap.access.objectclass.user>
                   <ume.ldap.access.objectclass.uacc>User</ume.ldap.access.objectclass.uacc>
                   <ume.ldap.access.objectclass.grup>Group</ume.ldap.access.objectclass.grup>
                   <ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
                   <ume.ldap.access.auxiliary_naming_attribute.user>samaccountname</ume.ldap.access.auxiliary_naming_attribute.user>
                   <ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
                   <ume.ldap.access.auxiliary_naming_attribute.uacc>samaccountname</ume.ldap.access.auxiliary_naming_attribute.uacc>
                   <ume.ldap.access.naming_attribute.grup>cn</ume.ldap.access.naming_attribute.grup>
              </privateSection>
         </dataSource>
    </dataSources>

    Hi Ulrich,
    Hope your problem is resolved. We are using EP7 and SP18. We are doing some study on your first issue. i.e. Distributing a user attribute into multiple LDAPs. Can you please let me know the feasibility? If yes, what are all step do I have to follow? Expecting your valuable answer. Thanks in advance!
    Regards,
    Kabali

  • Proxy servers and port 80

    I don't know if this will transmit but I am suddenly losing contact with Apple discussions and get a white screen with a reference to Remote proxy servers / port80 / Apple discussions.
    Would anyone know what is going on and if the problem is my end or Apple's.
    Much obliged for some info.
    Regards to all,  71

    Klaus1 wrote:
    The glass is half full: THEY ARE WORKING ON IT!
    I'd be happy just having a glass!
    Actually you're right they are working on it but if we talked about the fix here we'd have to kill everyone below level 6.

  • Running windows 7 firefox refuses to come up, proxy server is refusing connections network adminiastrater says proxy servers are correct and is issue with firefox what do I do/ do

    I start up firefox and it says the proxy server is refusing connection. It is configured to use a proxy server that is refusing connections. To check the proxy servers and ask network administrater to make sure proxy server is correct They say the proxy server is correct and it is a firefox problem. So what to I do now?

    Make sure that the Firefox connection settings are the same as in IE.
    You can find the connection settings in "Tools > Options > Advanced : Network : Connection"
    If you do not need to use a proxy to connect to internet then select No Proxy
    In Firefox 3.6.4 and later the default connection settings have been changed to "Use the system proxy settings".
    You can compare them with the IE settings in the Internet Options (Control Panel).
    Control Panel > Internet Options > Connections: LAN Settings

  • Proxy Servers, Password Resets/Expirations and Password Policies

    Our current configuration has two directory proxy servers and two directory servers, all running DSEE 6.3.1. The LDAP clients point to the proxy servers and the proxy servers point to the directory servers.
    When the LDAP clients user the proxy servers, users aren't notified on password resets or expirations. When I point one of the LDAP clients directly at on the directory servers, bypassing the proxy servers, the expected behavior of being required to change a password on reset or notification of password expiration works fine.
    We would like this to work via the proxy servers as well. Can anyone point me in a direction or two to determine why this isn't working as expected ?
    TIA!

    I opened a service call on this and in speaking with the rep, who was reading the CR mentioned in the first reply, he said it contained a note about the fix being scheduled for release in DSEE 7.x. I'm not sure if it made it into the recently released 7.0 or not.
    A patch released for the 6.3.1 proxy servers on the 21st of December didn't include mention of the CR in the notes, although there was mention of another CR that sounded like it might be related.
    Since it appears the CR was created in late November, I'd be surprised if either the DPS 6.3.1 patch or the 7.0 full release address the CR. In either case, I'm assuming you'll have to wait if you don't have a support contract with Sun that covers DSEE.

  • Question on installing Multiple Directory Servers

    Hello All,
    I seem to be having a problem installing multiple directory servers, and I was hoping that somebody could help me. Here is what I am trying to do:
    I install DS 2005Q4 on HostA. I have it be the User/Group and Configuration Server. This install goes ok and I can use the administration server and console to manage the servers.
    I then go to HostB and install DS 2005Q4 and tell it to use the configuration server on HOSTA. I use the the passwords for Admin and Directory Manager and tell it to store User/Group information. I also install the admistration server.
    The problem is when I go to manage this second ldap server throught either administration server it tells me that I have insufficient rights. That is if I click on the configuration tab and try and look at anything.
    The second adminsitration server can see and manage the DS on HOSTA fine, but not the DS on HostB. The same thing goes for the administration server on HostA. It can manage the DS on HostA but not the DS on HostB. It keeps saying insufficient rights.
    The end goal is to setup these DS in multimaster replication and have the o=netscaperoot replicated to HostB.
    I am sure I must be doing something stupid, but I have banged my head on the wall all week and I thought I would see if somebody had any suggestions.
    The hardware is a pair of v210's with 4GB of memory and I am running Solaris 10 01/06 fully patched.
    Thanks for any help,
    Gary

    just for completness, when you have installed the consumer, you have manually started the admin server up haven't you??? if not, do so!
    also ensure that the host file holds the correct IP and host/host domain name.
    ensure you can contact the config server from your consumer etc.
    ensure you can connect to the consumer from the config server etc.
    if using the GUI from a machine other than the config server, ie pc based. ensure connectivity and host look up is acheivable from the PC.
    HTH

  • Multiple proxy settings for safari?

    I recently switched back to Safari from Firefox, and I am wondering whether there is a plugin or some piece of software that would allow me to effortlessly switch proxy settings. I want to use multiple proxy servers for research, and it's a pain to change the proxy settings in the System Preferences every time I want to switch. Any ideas?

    NetShade: http://www.netshade.net/
    It specializes in providing lists of proxies for you, as well as its own dedicated pay-to-access proxy server, but it also allows you to customize your list and switch between them.

  • Does Siebel Management Server supports multiple gtwy servers/siebelservers?

    Hello,
    Does Siebel Management Server supports multiple gtwy servers and siebel servers when running getservers.pl ?
    Does Siebel Management Agent service run under windows 2008 OS?
    Cheers
    Kota

    Hi,
    In addition to making sure Agent Proxy on all AD FS servers is enabled, please also verify that the IIS 6 Management Compatibility and
    IIS 6 Metabase Compatibility role services are installed. (Some AD FS 2.0 scripts depend on Internet Information Services (IIS) Windows Management Instrumentation (WMI) objects being installed.)
    Here are two links for your reference:
    Discovery Does Not Work in ADFS 2012 R2 MP
    http://blogs.technet.com/b/omx/archive/2014/05/07/discovery-does-not-work-in-adfs-2012-r2-mp.aspx
    http://scug.be/christopher/2012/03/07/opsmgr-scom-adfs-2-0-mp-discovery-issue/
    Regards,
    Yan Li
    Regards, Yan Li

  • Multiple primary server and one stand by server

    Friends,
    Can we have multiple primary servers and one stand by server.
    That is to say ,\
    can we have a system where there are primary servers at different locations and one stand by server
    in another location, so that all the changes that are happenign in all teh preimary servers can be seen
    and queried in stand by server.[logical]
    Assuming the prinmary servers have the same database structure.

    can we have a system where there are primary servers at different locations For one primary server there will be one standby server.
    stand by server in another location, so that all the changes that are happenign in all teh preimary servers can be seen and queried in stand by server.[logical].You can have a standby server in a remote location and use it for reporting purpose, but you should put ur standby db in readonly mode till 10g. In 11g I think you can put ur standby database in managed recovery mode and still you can use it for reporting purpose.
    Satya.

  • Cisco ACS 5.2 authentication against multiple LDAP servers

    Hi Folks,
    I have a wireless network that uses ACS 5.2 to handle authentication.   The ACS is integrated with an Active Directory LDAP server (my_ldap) and is working correctly at the moment.    The authentication flow looks like this:
     - User tries to associate to WLAN
     - Authentication request is sent to ACS
     - Service selection rule chooses an access-policy (wireless_access_policy)
     - wireless_access_policy is configured to use my_ldap as identity source.
    A sister company is about to move into our offices, and will need access to the same WLAN.    Users in the sister company are members of a separate AD domain (sister_company_ldap).    I would like to modify the wireless_access_policy so that when it receives an authentication request it will query both my_ldap and sister_company_ldap, and return a passed authentication if either attempt is successful.     Is this possible?

    Assuming you're already authenticating using your AD binding and AD1 as your identity source, you can add a further LDAP server as another identity source and add this to your identity store sequence in your access policy to authenticate against both.
    You can also add multiple LDAP servers and add them both to the identity store sequence (if you're not using AD1).

  • Multiple Application Servers - Same class instance

    Hi,
    Due to increasing load we have to add multiple Web Servers and Application Servers (custom built) for our Web Application.
    As currently we are using 'synchronized' for adding and releasing connection in ConnectionPool and also using static in several other classes - we have to make these few classes single instance across the application servers.
    We are using iPlanet 6.0 for Win 2000. Is there any way we can direct specific classes for a single instance. Please provide me with all sorts of alternatives.
    Thanks a lot,
    Suman Biswas

    Hi,
    Yes, we have different JVMs. Different JVM means different processes,now there can be two cases,these process running on same machines
    or on different machines.If it is in different machines then undoubtly you require to go for the Distributed Technology(RMI for java).
    As we have couple of classes which are using
    'synchronized' - cann't we use centralized classes for
    these couple of classes to maintain integrity?Yes you can do it,now this centralized class should be available in common place from where your all applications can get results,and for avoiding the data corruption your require to go for synchronized(if some global variables) block,since the same instance will be serving all the requests.
    When you say RMI - my question is how the commercial products handle these kind of issues while they are in multiple servers?I have created some application using RMI but not the same one which you had specified.I had used it for different purpose.
    vicky

Maybe you are looking for