CSS best practice / keepalives

We have a Cisco 11503 running 7.40.1.03 (standard feature set) that we are setting up as a load balancer for a new e-mail system. I had two previous threads - thanks to Gilles and the others who responded. The box is now more or less configured to do what we want it to do, but I'm curious about "best practice" suggestions for keepalives.
As I understand it, keepalives are per service. As an example, we have two webmail servers. They are only running SSL, so each server is a service with keepalive type ssl. If webmail1 looses its apache or just dies entirely, the keepalive will not respond, and the CSS will send all traffic to webmail2, which still has its keepalives active.
This is all well and good. But, our IMAP servers are running multiple protocols - 7 of them. I have two services configured; one for each server, with no protocol specification. Then I have a content rule for each seperate protocol, where the port #s are configured.
I am thinking that if I want the most out of the CSS, I need to configure a seperate SERVICE for each protocol for the e-mail servers, with a specific keepalive for each individual protocol. That way if SSH goes away, the CSS will close SSH to email1 and only send that traffice to email2, but will still send IMAP or SIMAP to email1, since those protocols didn't go down.
For me this seems like a configuration disaster. I'd need a seperate service for each server and each protocol, and then a separate content rule as well for every service and every protocol.
Is this correct? Or is there some way of streamlining the configuration to reduce the number of services and/or content rules?
Thank you! And let me know if the configuration would be helpful.
Cheers...

The best is to indeed split each protocol and create a separate service and rule for each of them.
2 servers and 7 protocols is not a big config [some customer have 300 servers and 2 or 3 protocols which makes it more problematic to configure].
If you really think this is too much, simply create 1 ip service per server and 1 ip content rule.
You don't monitor the protocols but just ip connectivity.
Easy config, it works but you don't have the granularity to detect specific protocols going down.
Regards,
Gilles.

Similar Messages

HTML and CSS Best Practices for Eloqua?

Hello Topliners Community,
My name is Ben and I am a Web Designer. I am currently looking for any guidance on HTML and CSS best practices when working with Eloqua. I am interested in the best practices for e-mail and landing pages.
Thank you,
Ben

Personally I like to upload my custom created html/css into Eloqua instead of using the WYSIWYG.
But if you must then right clicking on text boxes and click edit source is the way to go.
There was a good discussion on editing your forms with CSS:
Energize Your Eloqua10 Forms with CSS
created by Ryan Wheler on Nov 2, 2012 8:44 AM, last modified by Greg Stotler on Sep 19, 2013 2:00 PM
Version 2
CSS can be used to heavily customize the layout of forms in Eloqua10. In this article we will provide sample cover some common formatting use cases on Eloqua10 Landing Pages. Further details about uses of CSS in Eloqua10 form templates can be found here: EE12 - Do It - Eloqua - Energize E10 Forms
Eloqua10 Forms HTML Structure
Below is an outline of the structure of the HTML generated by Eloqua when a form is added to a landing page. By targeting the HTML classes highlighted below, we can control the layout of any form on your landing page.
For the rest of page: http://topliners.eloqua.com/docs/DOC-3015

Custom CSS Best Practice?

I am upgrading a company theme (created in 3.2) to 4.2, so porting old tables, tr, td, custom css etc. into the section and div elements of a copy of Theme 25 of 4.2.
I have a master theme application and am subscribing to it from each application, and have a custom CSS file (in Shared Components whilst developing then will become external in production for performance reasons) referenced in the page templates.
My question is, taking the form region as an example, in Theme 25 at the top of the form region definition you have:
<section class="uRegion #REGION_CSS_CLASSES# clearfix" id="#REGION_STATIC_ID#" #REGION_ATTRIBUTES#>I want to customise the uRegion CSS, so what is the best practice - put a new uRegion definition in the custom CSS file with the new CSS in it, to override the standard uRegion, or change the form template to:
<section class="ABCuRegion #REGION_CSS_CLASSES# clearfix" id="#REGION_STATIC_ID#" #REGION_ATTRIBUTES#>and put a new definition for ABCuRegion in the custom CSS file? Both work but I wonder what is best. By referencing the company name ABC in the template it is obvious that this has been overridden, but by just overriding the standard uRegion and leaving the template as-is, is that better for forward compatibility? I have also read that some people create a new directory on the server, copy a standard theme into it and change the standard css files after that.
regards,
Malcolm.

MalcA wrote:
I am upgrading a company theme (created in 3.2) to 4.2, so porting old tables, tr, td, custom css etc. into the section and div elements of a copy of Theme 25 of 4.2.
I have also read that some people create a new directory on the server, copy a standard theme into it and change the standard css files after that use the copy as the base for a custom theme.That's the recommended approach if you're really creating a custom theme rather than just tweaking things here and there. It follows the principle of separation of concerns in that by retaining the standard <tt>uRegion</tt> class you can change the appearance of the application simply by switching the referenced CSS, rather than having to change template, HTML, and CSS.
It's also more efficient than having the browser parse and apply multiple levels of override rules, and more likely to allow designers and developers to remain sane as they have fewer strange cascade and specificity bugs to deal with.
Best practice for serious customization is to leave <tt>/apex/images/...</tt> untouched and create your own CSS/images/JS folder structure elsewhere on the web server. This makes it easier to apply APEX patches and upgrades, and to manage your custom resources.

CSS Best Practice

On the following page, I'm wanting to move the image with the
phone number
up to the top right. What is the best way to do that? Should
I style the
image with a class or try to put the image in a separate div
and move it up?
I know there are multiple ways to do things, but what is
recommended in this
situation?
http://www.presentationsdirect.com/2007/test.asp
Brandon
==================
Presentations Direct - Binding Machines, Laminators and Paper
Shredders
http://www.presentationsdirect.com
==================

Is there a way to move the phone number up to the right
without making the
logo a background image?
Brandon
==================
Presentations Direct - Binding Machines, Laminators and Paper
Shredders
http://www.presentationsdirect.com
==================
"Kim" <[email protected]> wrote in message
news:eqg6ag$e7h$[email protected]..
>I think I would simplify the whole thing a bit...
>
> <div id="header"><a href="#"><img
src="your_img.gif /><a/></div>
>
> and the css would look something like this
>
> #header {background:url(your_img.gif.gif) no-repeat
right
> top;text-align:left}
>
> and then add the link to your logo
>
> (You'll probably need this rule then... #header img
{border:none})
>
>
> Brandon skrev:
>> On the following page, I'm wanting to move the image
with the phone
>> number up to the top right. What is the best way to
do that? Should I
>> style the image with a class or try to put the image
in a separate div
>> and move it up? I know there are multiple ways to do
things, but what is
>> recommended in this situation?
>>
>>
http://www.presentationsdirect.com/2007/test.asp
>>
>
> --
> Kim
> ---------------------------
>
http://www.geekministry.com

Best Practice for serving static files (gif, css, js) from front web server

I am working on optimization of portal performance by moving static files (gif, css, js) to my front web server (apache) for WLP 10 portal application. I end up with moving whole "framework" folder of the portal WebContent to file system served by apache web server (the one which hosts WLS plugin pointing to my WLP cluster). I use <LocationMatch> directives for that:
Alias /portalapp/framework "/somewhere/servedbyapache/docs/framework"
<Directory "/somewhere/servedbyapache/docs/framework">
<FilesMatch "\.(jsp|jspx|layout|shell|theme|xml)$">
Order allow,deny
Deny from all
</FilesMatch>
</Directory>
<LocationMatch "/partalapp(?!/framework)">
     SetHandler weblogic-handler
     WLCookieName MYPORTAL
</LocationMatch>
So, now browser gets all static files from apache insted of the app server. However, there are several files from bighorn L&F, which are located in the WLP shared lib: skins/bighorn/ window.css, wsrp.css, menu.css, general.css, colors.css; skins/bighorn/borderless/window.css; skeletons/bighorn/js/ util.js, buttons.js; skeleton/bighorn/css/layout.css
I have to merge these files into the project and physically move them into apache served file system to make mentioned above apache configuration works.
However, this approach makes me exposed bunch of framework resources, which I do not to intend to change and they should not be change (only custom.css is the place to make custom changes to the bighorn skin). Which is obviously not very elegant solution. The other approach would be intend to create more elaborate expression for LocationMatch (I am not sure it's entirely possible giving location of these shared resources). More radical move - stop using bighorn and create totally custom L&F (skin, skeleton) - which is quire a lot of work (plus - bighorn is working just fine for us).
I am wondering what is the "Best Practice Approach" approach recommended by Oracle/BEA - giving the fact that I want to serve all static files from my front end apache server instead fo WLS app server.
Thanks,
Oleg.

Oleg,
you might want to have a look at the official WLP performance support pattern (Metalink DocID 761001.1 ) , which contains a section about "Configuring a Fronting Web Server Serving WebLogic Portal 8.1 Static Artifacts ".
It was written for WLP 8.1, but most of the settings / recommendations should also to WLP 10.
--Stefan

Best practices for cleaning up an old CSS?

We have a legacy help system that we've put into RH 9. Our CSS has a lot of old styles in it. Is there a best practices document somewhere that we can use to learn how to clean up the CSS and remove old styles but still preserve the ones we want?
thanks...

I don't know of any such document but perhaps this will help.
First archive a copy of the CSS as it is now so that you can go back and retrieve anything that you later find you shouldn't have deleted.
Next you should be safe in deleting any styles you see with kadov in them. You will see they are duplicates of another style and were used for the way RoboHelp used to work.
The rest are a bit more difficult. You need to use the multifile find and replace tool to see if they are used in any topic. Then either change them to what you want now or leave them in the CSS.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Best practices for making the end result web help printable

Hi all, using TCS3 Win 7 64 bit. All patched and up to date.
I was wondering what the best practices are for the following scenario:
I am authoring in Frame, link by reference into RH.
I use Frame to generate PDFs and RH to generate webhelp.
I have tons of conditional text which ultimately produce four separate versions of PDFs as well as online help - I handle these codes in FM and pull them into RH.
I use a css on all pages of my RH to make it 'look' right.
We now need to add the ability for end users to print the webhelp - outside of just CTRL+P because a)that cuts off the larger images and b)it doesn't show header, footer, logo, date, etc. (stuff that is in the master pages in FM).
My thought is doing the following:
Adding four sentences (one for each condition) in the FM book on the first page. Each one would be coded for audience A, B, C, or D (each of which require separate PDFs) as well as coded with ONLINE so that they don't show up in my printed PDFs that I generate out of Frame. Once the PDFs are generated, I would add a hyperlink in RH (manually) to each sentence and link the associated PDF (this seems to add the PDF file to the baggage files in RH). Then when I generate my RH webhelp, it would show the link, with the PDF, correctly based on the condition of the user looking at the help.
My questions are as follows:
1- This seems more complicated than it needs to be. Is it?
2- I would have to manually update every single hyperlink each time I update my FM book, because I am single sourcing out of Frame and I am unable (as far as I can tell) to link a PDF within the frame doc. I update the entire book (over 1500 pages) once every 6 weeks so while this wouldn't be a common occurrence it will happen regularly, and it would be manual (as far as I can tell)?
3- Eventually, I would have countless PDFs inside RH. I assume this will eventually impact performance. So this also doesn't seem ideal?
If anyone has thoughts/suggestions on a simpler way or better way to do this, I'd certainly appreciate it. I have watched the Adobe TV tutorial on adding a master page but that seems to remove the ability to use a css across all my topics and it also requires the manual addition of a manual hyperlink to the PDF file, so that is what I am proposing above, anyway (not sure the benefit, therefore).
Thanks in advance,
Adriana

Anything other than CTRL + P is going to create a lot of work so perhaps I can comment on what you see as drawbacks to that.
a)that cuts off the larger images and b)it doesn't show header, footer,
logo, date, etc. (stuff that is in the master pages in FM).
Larger images.
I simply make a point of keeping my image sizes down to a size that works. It's not a problem for me but that doesn't mean it will work for you. Here all I am doing is suggesting you review how big a problem that would be.
Master Page Details
I have to preface this with the statement that I don't work with FM. The details you refer to print when they are in RoboHelp master pages. Perhaps one of the FM users here can comment on how to get FM master pages to come through.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Best practice in dreamweaver based web design

Hi DW Gurus
I have been learning dreamweaver at work and at home for a while now and I am very interested in getting some details about best practices.
I am aware that my designs are still quite simple and don't expand dreamweaver anyway near its abilities, however as a novice I am sticking with DW CS4 and trying to developing foundation skills before trying to move on to greater adventures in web design. My dream is to eventually leave my employer and start my own freelance design business that I can manage while I am travelling in SE Asia (yeah I know - dream on .....). I am saving for my CS4 master suite license - my current one belongs to my employer.
In particular I have just started to do some free design a community organisation - I am trying to develop a portfolio of sites that I can show new clients (with money) what they could expect for their investments.
I am interested in getting some ideas about work flows - design standards - whether designers use the dreamweaver layouts - whether to code or to use the WYSIWYG.
Anyone care to share how they plan and go about their design work.
In my past life I was a SQL developer and a C#.net programmer - in those feilds there are standards for code and applications . Are there industry standards that would point to good or better designing?
Thanks for your time and interest in my topic,
Respect,
Doug

The first thing you need to learn is html and css, without knowing the programming language will only make DW a hard tool to use. You need to learn coding to WC3 standards.
FREE HTML & CSS Tutorials - http://w3schools.com/
http://reference.sitepoint.com/css
http://reference.sitepoint.com/html
Validation tools that you will need to bookmark.
HTML Validator - http://validator.w3.org
CSS Validator - http://jigsaw.w3.org/css-validator/
Hopefully you use Firefox, and if you do, the web developer toolbar is essential:
http://chrispederick.com/work/web-developer/
Yes, you can rely somewhat on DW's layout mode (or what features are left of it), but this will only lead to problems when it comes time to troubleshoot any problem pages that do not render correctly across the various browsers.
A paying client will expect a well designed, fully functional website and you need to have the programming skills to accomplish this for them.
Not sure how far advanced you are but the Adobe site has quite a few CSS based tutorials - and I would strongly urge you to go through the series listed below - to get up to speed on the correct way to lay out a page.
Creating your first website (series)
http://help.adobe.com/en_US/Dreamweaver/10.0_Using/WS42d4a1c0291fbe4e59147ede1232ff9686c-8 000.html
LIST OF CSS TUTORIALS ON ADOBE SITE:
http://www.adobe.com/devnet/dreamweaver/css.html
If you use Fireworks as a tool to create your layouts, then the following tutorial may be of benefit:
TAKING FIREWORKS COMP TO DREAMWEAVER:
http://www.adobe.com/devnet/dreamweaver/articles/dw_fw_css_pt1.html
Good luck in your future endeavours
Nadia
Adobe Community Expert : Dreamweaver
Unique CSS Templates | Tutorials | SEO Articles
http://www.DreamweaverResources.com
Web Design & Development
http://www.perrelink.com.au
http://twitter.com/nadiap

Best practice for Spark repeating background image in a SkinnableContainer?

In my old Flex 3.5 code I would accomplish this by dropping an Image into a Canvas and hitting the Canvas with some css style stuff to get the repeat. The Image tag had a source property that would take a web address so I could dynamically grab different images from the web based on some conditions. Little bit more trouble with Flex 4.5 and Spark but I'm trying to get there.
Here Adobe docs explain how to *embed* a background image:
http://help.adobe.com/en_US/flex/using/WS422719A4-7849-4921-AF39-57FF567B483B.html#WS063B0 491-B7AB-4b00-A39F-E44310BCB0E0
They use a BitmapFill object in the skin.

    <s:Rect id="background" left="3" top="3" right="3" bottom="3" alpha=".25">
        <s:fill>
            <s:BitmapFill source="@Embed(source='../../assets/myImage.jpg')"/>
        </s:fill>
    </s:Rect>
Problem is I need to do this without embedding the image. In my old code I grabbed the image from web (set source property on Image tag to web address). What's the best practice for achieving this with a skinnable container? The BitmapFill object used above won't take a web address for a source.
Thanks in advance.

Use BitmapImage with a fillMode of repeat:
<s:BitmapImage source="http://www.google.com/intl/en_com/images/srpr/logo2w.png" width="100%" height="100%" scaleMode="stretch" fillMode="repeat" />

Best practice on dynamically changing drop down in page fragment

I have a search form, which is a page fragmant that is shared across many pages. This form allows users to selct a field from the drop down list, and search for a particular value, as seen in the screenshot here:
http://photos1.blogger.com/blogger2/1291/174258525936074/1600/expanded.5.gif
Please note that the search options are part of page fragmant embedded within a page - so that I can re-use it across many pages.
The drop down list changes,based on the page this fragment is embedded. For users page, it will be last name, first name, etc. For parts page, it will be part number, part desc., etc.
Here is my code:
          Iterator it=getTableRowGroup1().getTableColumnChildren();
        Option options[]=new Option[getTableRowGroup1().getColumnCount()];
        int i=0;
        while (it.hasNext()){
            TableColumn column=(TableColumn)it.next();
            if (column.getSort()!=null){
                options=new Option(column.getSort().toString(), column.getHeaderText());
}else{
options[i]=new Option(column.getHeaderText(), column.getHeaderText());
i++;
search search=(search)getBean("search");
search.getSearchDDFieldsDefaultOptions().setOptions(options);
This code works, but it gives me all fields of the table available in the drop down. I want to be able to pick and choose. May be have an external properties file associated with each page, where I can list the fields available for search drop down??
What is the best practice to load the list of options available for drop down on each page? (i.e last name, first name, etc.) I can have the code embedded in prerender of each page, or use sort of a resouce bundle for each page or may be use a bean?

I have to agree with Pixlor and here's why:
http://www.losingfight.com/blog/2006/08/11/the-sordid-tale-of-mm_menufw_menujs/
and another:
http://apptools.com/rants/menus.php
Don't waste your time on them, you'll only end up pulling your hair out :-)
Nadia
Adobe® Community Expert : Dreamweaver
Unique CSS Templates |Tutorials |SEO Articles
http://www.DreamweaverResources.com
Book: Ultimate CSS Reference
http://www.sitepoint.com/launch/005dfd4/3/133
http://twitter.com/nadiap

Best practice for component layout?

Hi,can people tell me their views on best practice in this area, using JSF.
Eg, say I want this:
    LabelSml    InputField
    LabelLarge InputField... ie 2 labels, 2 fields, vertically alligned, and with some space between the label and the field.
and this one:
    Field                             Field... ie 2 fields with a lot of space between them.
Finally, are there any examples on the web of UIs with many discrete fields on them (as opposed to logon/helloWorld and matrix data control), where I can look at how the design has been done.
Marc

I don't know if our solution is a best practice. We are not using the label property of input components because the alignment does not satisfy then. Instead we are using a <h:panelGrid> and nest <ui:label> and <ui:textField> (Studio Creator components) components in it. Multiple components in one cell are surrounded with a nested layout or grid panel. The number of columns is set by the attribute "columns" and width is controlled by the attribute "columnClasses". Example
<?xml version="1.0" encoding="UTF-8"?>
<jsp:root version="1.2" xmlns:bp="http://java.sun.com/blueprints/ui/14" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html"
    xmlns:jsp="http://java.sun.com/JSP/Page" xmlns:ui="http://www.sun.com/web/ui">
    <jsp:directive.page contentType="text/html;charset=UTF-8" pageEncoding="UTF-8"/>
    <f:view locale="#{SessionBean1.locale}">
        <f:loadBundle basename="com.asci.nef.resourcen.Aktionen" var="akt"/>
        <f:loadBundle basename="com.asci.nef.resourcen.Label" var="lab"/>
        <f:loadBundle basename="com.asci.nef.resourcen.Datenlisten" var="datenlisten"/>
        <f:loadBundle basename="com.asci.nef.resourcen.Meldungen" var="msg"/>
        <ui:page binding="#{personal$Mitarbeiterauswahl.page1}" id="page1">
            <ui:html binding="#{personal$Mitarbeiterauswahl.html1}" id="html1">
                <ui:head binding="#{personal$Mitarbeiterauswahl.head1}" id="head1">
                    <ui:link binding="#{personal$Mitarbeiterauswahl.link1}" id="link1" url="/resources/stylesheet.css"/>
                    <ui:script binding="#{personal$Mitarbeiterauswahl.scriptFenster}" id="scriptFenster" url="/resources/fenster.js"/>
                </ui:head>
                <ui:body binding="#{personal$Mitarbeiterauswahl.body1}" id="body1" style=" -rave-layout: grid">
                    <jsp:directive.include file="../Menue.jspf"/>
                    <ui:form binding="#{personal$Mitarbeiterauswahl.form1}" id="form1">
                        <div>
                            <jsp:directive.include file="../Fensterkennung.jspf"/>
                        </div>
                        <ui:tabSet binding="#{personal$Mitarbeiterauswahl.tabSetPersonaldaten}" id="tabSetPersonaldaten" selected="tabSuchen" style="position: absolute; left: 0px; top: 36px; width: 100%;">
                            <ui:tab binding="#{personal$Mitarbeiterauswahl.tabSuchen}" id="tabSuchen" text="#{akt.funktion110}">
                                <ui:panelLayout binding="#{personal$Mitarbeiterauswahl.layoutPanelSuchen}" id="layoutPanelSuchen">
                                    <h:panelGrid binding="#{personal$Mitarbeiterauswahl.gridPanelSuchen}" columnClasses="gridlabel, griddata" columns="2"
                                        id="gridPanelSuchen" style="position:absolute; left:100px; top:30px;">
                                        <ui:label binding="#{personal$Mitarbeiterauswahl.labelPersonalnummerSuchen}" id="labelPersonalnummerSuchen" text="#{lab.mitarbeiterauswahl_personalnummer}"/>
                                        <ui:textField binding="#{personal$Mitarbeiterauswahl.textFieldPersonalnummerSuchen}" converter="javax.faces.Long"
                                            id="textFieldPersonalnummerSuchen" maxLength="10" styleClass="eingabe1"/>
                                        <ui:label binding="#{personal$Mitarbeiterauswahl.labelNameSuchen}" for="textFieldNameSuchen" id="labelNameSuchen" text="#{lab.mitarbeiterauswahl_name}"/>
                                        <ui:textField binding="#{personal$Mitarbeiterauswahl.textFieldNameSuchen}" converter="TextTrim" id="textFieldNameSuchen"
                                            maxLength="30" styleClass="eingabe4"/>
                                        <ui:label binding="#{personal$Mitarbeiterauswahl.labelGeburtsdatumSuchen}" id="labelGeburtsdatumSuchen" text="#{lab.mitarbeiterauswahl_geburtsdatum}"/>
                                        <ui:textField binding="#{personal$Mitarbeiterauswahl.textFieldGeburtsdatumSuchen}"
                                            converter="#{SessionBean1.sqlDateConverter}" id="textFieldGeburtsdatumSuchen" maxLength="10" styleClass="eingabe1"/>
                                        <ui:label binding="#{personal$Mitarbeiterauswahl.labelTaetigkeitSuchen}" id="labelTaetigkeitSuchen" text="#{lab.mitarbeiterauswahl_taetigkeit}"/>
                                        <ui:dropDown binding="#{personal$Mitarbeiterauswahl.dropDownTaetigkeitSuchen}" id="dropDownTaetigkeitSuchen"
                                            items="#{personal$Mitarbeiterauswahl.listOptionsTaetigkeitSuchen}" styleClass="eingabe4"/>
                                        <ui:label binding="#{personal$Mitarbeiterauswahl.labelVereinbarungSuchen}" id="labelVereinbarungSuchen" text="#{lab.mitarbeiterauswahl_zusatzvereinbarung}"/>
                                        <ui:textField binding="#{personal$Mitarbeiterauswahl.textFieldVereinbarungSuchen}" id="textFieldVereinbarungSuchen" styleClass="eingabe4"/>
                                        <ui:label binding="#{personal$Mitarbeiterauswahl.labelSortieren}" id="labelSortieren" text="#{lab.mitarbeiterauswahl_sortieren}"/>
                                        <ui:radioButtonGroup binding="#{personal$Mitarbeiterauswahl.radioButtonGroupSortieren}" columns="4"
                                            id="radioButtonGroupSortieren"
                                            items="#{personal$Mitarbeiterauswahl.radioButtonGroupSortierenDefaultOptions.options}" required="true" selected="#{personal$Mitarbeiterauswahl.radioButtonGroupSortierenDefaultOptions.selectedValue}"/>
                                        <ui:label binding="#{personal$Mitarbeiterauswahl.labelDummy1}" id="labelDummy1"/>
                                        <ui:button action="#{personal$Mitarbeiterauswahl.buttonSuchen_action}"
                                            binding="#{personal$Mitarbeiterauswahl.buttonSuchen}" id="buttonSuchen" text="#{akt.button_suchen}"/>
                                        <ui:label binding="#{personal$Mitarbeiterauswahl.labelDummy2}" id="labelDummy2"/>
                                        <ui:listbox binding="#{personal$Mitarbeiterauswahl.listboxSuche}" id="listboxSuche" monospace="true"
                                            onDblClick="#{personal$Mitarbeiterauswahl.onDblClickAction}" rows="20" styleClass="eingabe7"/>
                                        <ui:label binding="#{personal$Mitarbeiterauswahl.labelDummy3}" id="labelDummy3"/>
                                        <ui:panelLayout binding="#{personal$Mitarbeiterauswahl.layoutPanelButtons2}" id="layoutPanelButtons2" panelLayout="flow">
                                            <ui:button action="#{personal$Mitarbeiterauswahl.buttonNeu_action}"
                                                binding="#{personal$Mitarbeiterauswahl.buttonNeu}" id="buttonNeu" immediate="true" text="#{akt.button_neu}"/>
                                            <ui:button action="#{personal$Mitarbeiterauswahl.buttonBearbeiten_action}"
                                                binding="#{personal$Mitarbeiterauswahl.buttonBearbeiten}" id="buttonBearbeiten" text="#{akt.button_bearbeiten}"/>
                                            <ui:button action="#{personal$Mitarbeiterauswahl.buttonLoeschen_action}"
                                                binding="#{personal$Mitarbeiterauswahl.buttonLoeschen}" id="buttonLoeschen" text="#{akt.button_loeschen}"/>
                                        </ui:panelLayout>
                                    </h:panelGrid>
                                </ui:panelLayout>
                            </ui:tab>
                        </ui:tabSet>
                        <h:panelGrid binding="#{personal$Mitarbeiterauswahl.gridPanelFehler}" id="gridPanelFehler" onclick="this.style.display = 'none';" style="position: absolute; right: 20px; bottom: 50px; width: 250px; height: 78px;"/>
                        <ui:panelLayout binding="#{personal$Mitarbeiterauswahl.layoutPanelConfirm}" id="layoutPanelConfirm" panelLayout="flow" style="position:absolute; top:36px; left:0px;width:100%; height:700px;">
                            <h:panelGrid binding="#{personal$Mitarbeiterauswahl.gridPanelConfirm}" columns="1" id="gridPanelConfirm" style="margin-left:auto; margin-right:auto; margin-top:300px; background-color:#FF3333;">
                                <ui:staticText binding="#{personal$Mitarbeiterauswahl.staticTextConfirm}" id="staticTextConfirm" text="#{msg.global_loeschen}"/>
                                <ui:panelLayout binding="#{personal$Mitarbeiterauswahl.layoutPanelConfirmButtons}" id="layoutPanelConfirmButtons" panelLayout="flow">
                                    <ui:button action="#{personal$Mitarbeiterauswahl.buttonConfirmYes_action}"
                                        binding="#{personal$Mitarbeiterauswahl.buttonConfirmYes}" id="buttonConfirmYes" text="#{akt.button_ja}"/>
                                    <ui:button action="#{personal$Mitarbeiterauswahl.buttonConfirmNo_action}"
                                        binding="#{personal$Mitarbeiterauswahl.buttonConfirmNo}" id="buttonConfirmNo" text="#{akt.button_nein}"/>
                                </ui:panelLayout>
                            </h:panelGrid>
                        </ui:panelLayout>
                    </ui:form>
                </ui:body>
            </ui:html>
        </ui:page>
    </f:view>
</jsp:root>

Best practice to create views

Hi,
I've a question about best practice to develop a large application with many complex views.
Typically at each time only one views is displayed. User can go from a view to another using a menu bar.
Every view is build with fxml, so my question is about how to create views and how switch from one to another.
Actually I load fxml every time the view is required:
FXMLLoader loader = new FXMLLoader();
InputStream in = MyController.class.getResourceAsStream("MyView.fxml");
loader.setBuilderFactory(new JavaFXBuilderFactory());
loader.setLocation(OptixController.class.getResource("MyView.fxml"));
BorderPane page;
try {
     page = (BorderPane) loader.load(in);
     } finally {
          if (in != null) {
               in.close();
// appController = loader.getController();
Scene scene = new Scene(page, MINIMUM_WINDOW_WIDTH, MINIMUM_WINDOW_HEIGHT);
scene.getStylesheets().add("it/myapp/Mycss.css");
stage.setScene(scene);
stage.sizeToScene();
stage.setScene(scene);
stage.sizeToScene();
stage.centerOnScreen();
stage.show();My questions:
1- is a good practice reload every time the fxml to design the view?
2- is a good practice create every time a new Scene or to have an unique scene in the app and every time clear all elements in it and set the new view?
3- the views should be keep in memory to avoid performace issue or it is a mistake? I think that every time a view should be destroy in order to free memory.
Thanks very much
Edited by: drenda81 on 21-mar-2013 10.41

>
>
My questions:
1- is a good practice reload every time the fxml to design the view?
2- is a good practice create every time a new Scene or to have an unique scene in the app and every time clear all elements in it and set the new view?
3- the views should be keep in memory to avoid performace issue or it is a mistake? I think that every time a view should be destroy in order to free memory.
In choosing between 1 and 3 above, I think either is fine. Loading the FXML on demand every time will be slightly slower, but assuming you are not doing something unusual such as loading over a network connection it won't be noticeable to the user. Loading all views at startup and keeping them in memory uses more memory, but again, it's unlikely to be an issue. I would choose whichever is easier to code (probably loading on demand).
In choosing between reusing a Scene or creating a new one each time, I would reuse the Scene. "Clearing all elements in it" only needs you to call scene.setRoot(...) and pass in the new view. Since the Scene has a mutable root property, you may as well make use of it and save the (small) overhead of instantiating a new Scene each time. You might consider exposing a currentView property somewhere (say, in your main controller, or model if you have a separate model class) and binding the Scene's root property to it. Something like:
public class MainController {
private final ObjectProperty<Parent> currentView ;
public MainController() {
    currentView = new SimpleObjectProperty<Parent>(this, "currentView");
public void initialize() {
    currentView.set(loadView("StartView.fxml"));
public ObjectProperty<Parent> currentViewProperty() {
    return currentView ;
// event handler to load View1:
@FXML
private void loadView1() {
    currentView.set(loadView("View1.fxml"));
// similarly for other views...
private Parent loadView(String fxmlFile) {
    try {
     Parent view = FXMLLoader.load(getClass().getResource(fxmlFile));
     return view ;
    } catch (...) { ... }
}Then your application can do this:
@Override
public void start(Stage primaryStage) {
   Scene scene = new Scene();
   FXMLLoader loader = new FXMLLoader(getClass().getResource("Main.fxml"));
   MainController controller = (MainController) loader.getController();
   scene.rootProperty().bind(controller.currentViewProperty());
   // set scene in stage, etc...
}This means your Controller doesn't need to know about the Scene, which maintains a nice decoupling.

Best Practice For Referencing JPEG Path Using Servlets To Prepare HTML IMG

I am migrating a legacy app from Tomcat 5 to Weblogic 11g (10.3). In the legacy app, servlets write HTML that uses relative paths for <IMG src="../images/img.jpeg"> and <script src="../javascript/js.js">. The app is deployed as an exploded archive. Unfortunately, none of the images or script are being loaded. I've tried using http://serverIP:portNum/contextName/images/img.jpeg"> but it doesn't work. I've also checked to get the name of the context in the servlet and it's the root context. Could it have something to do with me having to append .war onto the application when I deploy it? Would it help if I deployed it as a war inside an ear? Basically, I want some best practices for doing this on Weblogic 11g. There are a lot of images and javascript and I'm really hoping they don't have to be inserted using ClassLoader.getResourceAsStream()... thank you.

Best Practice:
1. Move Static files like images, css, java scripts to a web server infrastructure if available.
2. If this is not your case, then please send your directory information how you have packaged your EAR. I can advice :)

What is the best practice to deploy the SharePoint site from test to production environment?

We are beginning to start a new SharePoint 2010 and 2013 development projects, soon developing new features, lists, workflows, customizations to the SharePoint site, customization to list forms and would like to put good practice (that will help in deployment)
in place before going ahead with development.
What is the best way to go about deploying my site from Development to Production?
I am using Visual Studio 2012 and also have Designer 2013...
I have already read that this can be done through powershell, also through visual studio and also via designer. But at this point I am confused as to which are best practices specifically for lists, configurations; workflows; site customizations; Visual studio
development features; customization to list forms etc. You can also provide me reference to links/ebook covering this topic.
Thanks in advance for any help.

Hi Nachiket,
You can follow below approach where the environments has been built in similar fashion
http://thesharepointfarm.com/sharepoint-test-environments/
if you have less data then you can use http://spdeploymentwizard.codeplex.com/
http://social.technet.microsoft.com/Forums/sharepoint/en-US/b0bdb2ec-4005-441a-a233-7194e4fef7f7/best-way-to-replicate-production-sitecolletion-to-test-environment?forum=sharepointadminprevious
For custom solutions like workflows etc you can always build the WSP packages and deploy across the environments using powershell scripts.
Hope this helps.
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful
Hi, can you answer me specifically with regards to the foll:-
lists
configurations
workflows
site customizations like changes to css/masterpage
Visual studio webparts
customization to list forms
Thanks.

Best Practice for VPC Domain failover with One M2 per N7K switch and 2 sups

I Have been testing some failover scenarios with 4 nexus 7000 switches with an M2 and an F2 card in each. Each Nexus has two supervisor modules.
I have 3 VDC's Admin, F2 and M2
all ports in the M2 are in the M2 VDC and all ports on the F2 are in the F2 VDC.
All vPC's are connected on the M2 cards, configured in the M2 VDC
We have 2 Nexus representing each "site"
In one site we have a vPC domain "100"
The vPC Peer link is connected on ports E1/3 and E1/4 in Port channel 100
The peer-keepalive is configured to use the management ports. This is patched in both Sups into our 3750s. (this is will eventually be on a management out of band switch)
Please see the diagram.
There are 2 vPC's 1&2 connected at each site which represent the virtual port channels that connect back to a pair of 3750X's (the layer 2 switch icons in the diagram.)
There is also the third vPC that connects the 4 Nexus's together. (po172)
We are stretching vlan 900 across the "sites" and would like to keep spanning tree out of this as much as we can, and minimise outages based on link failures, module failures, switch failures, sup failures etc..
ONLY the management vlan (100,101) is allowed on the port-channel between the 3750's, so vlan 900 spanning tree shouldnt have to make this decision.
We are only concerned about layer two for this part of the testing.
As we are connecting the vPC peer link to only one module in each switch (a sinlge) M2 we have configured object tracking as follows:
n7k-1(config)#track 1 interface ethernet 1/1 line-protocol
n7k-1(config)#track 2 interface ethernet 1/2 line-protocol
n7k-1(config)#track 5 interface ethernet 1/5 line-protocol
track 101 list boolean OR
n7k-1(config-track)# object 1
n7k-1(config-track)# object 2
n7k-1(config-track)# object 5
n7k-1(config-track)# end
n7k-1(config)# vpc domain 101
n7k-1(config-vpc-domain)# track 101
The other site is the same, just 100 instead of 101.
We are not tracking port channel 101, not the member interfaces of this port channel as this is the peer link and apparently tracking upstream interfaces and the peer link is only necessary when you have ONE link and one module per switch.
As the interfaces we are tracking are member ports of a vPC, is this a chicken and egg scenario when seeing if these 3 interfaces are up? or is line-protocol purely layer 1 - so that the vPC isnt downing these member ports at layer 2 when it sees a local vPC domain failure, so that the track fails?
I see most people are monitoring upstream layer3 ports that connect back to a core? what about what we are doing monitoring upstream(the 3750's) & downstream layer2 (the other site) - that are part of the very vPC we are trying to protect?
We wanted all 3 of these to be down, for example if the local M2 card failed, the keepalive would send the message to the remote peer to take over.
What are the best practices here? Which objects should we be tracking? Should we also track the perr-link Port channel101?
We saw minimal outages using this design. when reloading the M2 modules, usually 1 -3 pings lost between the laptops in the diff sites across the stretched vlan. Obviously no outages when breaking any link in a vPC
Any wisdom would be greatly appreciated.
Nick

Nick,
I was not talking about the mgmt0 interface. The vlan that you are testing will have a link blocked between the two 3750 port-channel if the root is on the nexus vPC pair.
Logically your topology is like this:
| |
| Nexus Pair |
3750-1-----------------------3750-2
Since you have this triangle setup one of the links will be in blocking state for any vlan configured on these devices.
When you are talking about vPC and L3 are you talking about L3 routing protocols or just intervaln routing.
Intervlan routing is fine. Running L3 routing protocols over the peer-link and forming an adjaceny with an router upstream using L2 links is not recommended. Teh following link should give you an idea about what I am talking here:
http://bradhedlund.com/2010/12/16/routing-over-nexus-7000-vpc-peer-link-yes-and-no/
HSRP is fine.
As mentioned tracking feature purpose is to avoid block hole of traffic. It completely depends on your network setup. Don't think you would be needing to track all the interfaces.
JayaKrishna

CSS best practice / keepalives

Similar Messages

Maybe you are looking for