Search your topic in Java2share
Home > FAQs
eXTReMe Tracker


Weblogic Application Server FAQs

211.How will you Configuring File Replication in WLS?

  • Create a folder shared by all servers on the cluster on a highly available file system.
  • Assign read/write privileges to the folder.
  • Configure file session persistence in the weblogic.xml deployment descriptor.

Ex:
<session-descriptor>
   <persistent-store-type>file</persistent-store-type>
   <persistent-store-dir>/mnt/wls_share</persistent-store-dir>
</session-descriptor>
212.Explain about Cross-Cluster Replication in WLS?
WebLogic provides the ability to replicate HTTP sessions across two clusters in separate domains:

    • This is most applicable to clusters that are distributed geographically.
    • Configure a global proxy to direct clients back to the same cluster (“cluster affinity”).
    • Configure a specific network channel for cross-cluster communication.

213.When can’t I use WebLogic Store-and-Forward?
You can’t use the WebLogic Store-and-Forward service in the following situations:

  • Receiving from a remote destination—use a message driven EJB or implement a client consumer directly.
  • Sending messages to a local destination—send directly to the local destination.
  • Forwarding messages to prior releases of WebLogic Server. See Q. What is a messaging bridge?.
  • Interoperating with third-party JMS products (for example, MQSeries). See Q. What is a messaging bridge?.
  • When using temporary destinations with the JMSReplyTo field to return a response to a request.
  • Environment with low tolerance for message latency. SAF increases latency and may lower throughput.

214..Explain about Embedded LDAP Server?

    • In WLS, users, groups, and authorization information is stored in an embedded LDAP server.
    • Several properties can be set to manage the LDAP server, including:
      • Credentials
      • Backup settings
      • Cache settings
      • Replication settings

215.How will you create a Deployment Plan?

    • Tools for creating a deployment plan:
      • weblogic.PlanGenerator
      • Administration Console
    • Goals for creating a deployment plan:
      • To expose the external resource requirements of the application as variables in the deployment plan
      • To expose additional configurable properties, such as tuning parameters as variables in the deployment plan
  • WLS includes tools to accelerate deployment plan creation.
  • The Administration Console:
      • Generates a skeleton plan.xml if a plan folder is detected with a newly deployed application
      • Updates plan.xml when you use the console to modify the deployment descriptor settings
  • The weblogic.PlanGenerator Java class can also generate a skeleton plan.xml for an existing application.

216..Explain the relationship between Transaction and Resource Managers?

    • A transaction manager coordinates multiple resource managers.
    • The 2PC protocol is used to coordinate the transaction.
    • The XA protocol implements 2PC.

217..What is a topic subscription?
A topic subscription can be thought of as an internal queue of messages waiting to be delivered to a particular subscriber. This internal queue accumulates copies of each message published to the topic after the subscription was created. Conversely, it does not accumulate messages that were sent before the subscription was created. Subscriptions are not sharable, only one subscriber may subscribe to a particular subscription at a time.
218.Explain about Trust and Identity in SSL?

    • SSL and keystore are configured independently.
    • For the purpose of backward compatibility, this release of Oracle WebLogic Server supports private keys and a trusted WebLogic Keystore provider.
    • Identity:
      • Private key and digital certificate (can now be looked up directly from the keystore, not necessarily as a stand-alone file outside the keystore)
    • Trust:
      • Certificates of trusted Certificate authorities

219..How will you access SSL enabled applications?

    • WLS uses SSL to secure HTTP and t3 communication.
    • To use SSL, clients access WLS via the https or t3s protocols.
      • https://localhost:7002/orderStock
      • t3s://localhost:7002/useCreditCard