SSO and indexing pages

Hi,
We have a webapp protected with Oracle Single On.
We would like to index the pages for a search engine( lucene ). We use a modified version of spindle.jar to get the pages. Spindle.jar opens URL Connection to fetch the pages.
The problem is that SSO prevents spindle.jar from
fetching the pages. I think i have to make spindle.jar
authenticate against the SSO Server before indexing the pages but i don't how to do that in Java.

cn=XXX information is missing for the SSO Server (orasso) when going to http://servername:7777/pls/orasso/orasso.home. Is that causing the problem? If so, how can I resolve it?
Thanks.
Andy

Similar Messages

  • What's the index node and index page in DB2

    Could you please explain what the index node and index page in DB2, and what's the relationship between them?

    Following paragraph is copied from tadm56.
    Tables contain records of data. One or more records of a table are stored in a DB2 data page. Pages are the minimum I/O unit of DB2. A DB2 data page can contain one or more records. But a record must fit in a data page.
    If a record of a table does not fit in a 4096 byte (4 KB) page, the table must be defined in a tablespace that is based on a larger page size. DB2 also provides page sizes of 8192 bytes (8 KB), 16384 bytes (16 KB), and 32768 bytes (32 KB).
    For improved access to data, indexes are predefined by SAP developers. Indexes can also be defined later as further need arises. An index is defined using a few columns of a table, which are accessed frequently. Index data structures allow for efficient retrieval of small quantities of data. Indexes are based on nodes, their storage is maintained within DB2 index pages. Because the pointers pointing to other index nodes are also stored in the index pages, storage of indexes is not as compact as the storage of data records.
    And above this paragraph, there is a figure that shows relationship. I don't know how to paste a picture here. In the figure, it shows that table records vs data page is n:1, and index nodes vs index page is 1:1.
    How to understand index nodes vs index page is 1:1?

  • Html and indexed pages

    I am trying to get ranked in google and only my index pages
    tend to get indexed. I do not understand why my secondary pages, do
    not get indexed for Lake Martin Real Estate searches.
    http://www.yourlakemartin.com
    Site header and search word as follows:
    LAKE MARTIN REAL
    ESTATE

    You can put a file called ".htaccess" in the root of any folder, and the server will use the directives in that file to control how it serves pages to the client.  There is a complete set of commands you can find by Googling "htaccess", probably more than you'd want to read, but among them is the ability to do a server redirect for any page fetch, which would let you redirect all requests for *.html to *.php automatically.  What's nice is that you can send a header along with the redirection that direts the search engines to adjust their indices, called a '301' header.  It specifies that the page requested has been permanently relocated to the new page name.
    On several of my sites I have such redirection being used - the .htaccess file contains markup like this -
    RedirectEngine On
    Redirect 301 /xyzzy.html http://www.example.com/xyzzy.php
    Give Google a try....

  • Can a Button be created in a PDF to go back to website index page?

    I should know this. But the idea to do it hasn't crossed my mind to do it. I use PDF's extensively in my website http://www.phillipmjones.net/
    Is it possible to put in a Home Button, at the end to have it go back to the index page, rather than having use back button on web Browser?

    Last Reply:
    In order to do so you have to:
    Open a Graphics Program and creae a button, in my case I used Fireworks to create a button with a special Filter that use button affects.
    Create desired button.
    Open original Word File and insert button at Desired Location Save as both Wod Docx and as PDF files.
    open desired Pdf in Acrobat choose replace File.
    Open Forms editor and create a form field that is a button.
    Make form outline with no color.
    make fill color with no color.
    make button action Web URL. Type entire link using all directories, sub directories and index page of desired directory.
    Save.
    get out of forms editor.
    Save file.
    upload to web site.
    It works but is way to many steps be worthwhile.
    This is being posted for those that desire to use a web link button in a PDF.  and want to know the desired steps.

  • My Index and contact page has moved my top nav up

    I only changed my contact styles on my Index page and now my top nav has gone to the top. On my contact page I added two images so I understand I need to add some code to do with that but not sure how to get it back correct.
    When I veiw my contact page through my wamp server though it all looks fine that's why I uploaded it onto the live server.  Does anyone know why that should be?
    www.bristolequestrianservices.co.uk.  Can someone help please?
    Thanks
    </head>
    <body>
    <div id="outer">
    <div id="wrapper">
                        <div id="logo">
                      <img src="images/banner1.jpg" />
              </div>
              <div id="social-media-icons">
                      <ul>
                          <li><a href="https://www.facebook.com/groups/150449201771804/"><img src="images/icons/facebook.jpg" /></a></li>
                  <li><a href="£"><img src="images/icons/rss.jpg" /></a></li>
                  <li><a href="http://www.twitter.com"><img src="images/icons/twitter.jpg" /></a></li>
                  <li><img src="images/icons/youtube.jpg" /></li>
                </ul>
                        </div>
             <div id="contact">
         <p><span class="big-blue">Bristol Equestrian Service</span><br>
         Tel: 0117 9190060 / 07900538697<br>
         Email: [email protected]<br>
          [email protected]</p>    
         </div             
            ><div id="topnav">
                      <ul>
                          <li><a href="index.html">Home</a></li>
                    <li><a href="stablesandfieldshelters.html">Stable and Field Shelters</a></li>
                    <li><a href="pricelist.html">Price List</a></li>
                    <li><a href="gallery.html">Gallery</a></li>
                    <li><a href="contactus.html">Contact Us</a></li>
                </ul>
                        </div>
                        <div id="banner">
                      <img src="images/newbanner.jpg" />
                        </div>
    /* Containers */
    #outer                                         {  width:960px; margin:0 auto; background:#FFF; }
    #wrapper                               {  width:900px; margin:0 auto; background:#FFF; }
    #logo                                         {  margin: 30px 0; float:left; }
    #social-media-icons                              {  float:right; }
    #social-media-icons ul li          {display:inline; }
    #social-media-icons ul                    {margin-top:40px; }
    #social-media-icons2                    {  float:left; }
    #social-media-icons2 ul li          {display:inline; }
    #social-media-icons2 ul                    {margin-top:10px; }
    #topnav                               { clear:both;  }
    #topnav          ul                              { border-top:1px #000 solid; border-bottom:1px #000 solid;
                                                                margin:20px 0; padding:10px 0;           }
    #topnav ul li                    { display:inline; }
    #topnav ul li a                    { padding:0 15px; }
    #topnav a:link                              { color: #000;  }
    #topnav a:visited                    { color: #000;  }
    #topnav a:active                    { color: #000;  }
    #topnav a:focus                              { color: #666;  }
    #topnav a:hover               { color: #f90;  }
    #banner                                        { margin-bottom:30px;  }
    #rightside                               { width:200px; float:right   }
    #content                               { width:650px; float:left;  }
    #content-fullwidth          {width:100%; }
    #footer                               { clear:both; margin-top:20px 0; border-top:1px #ccc solid;

    /* Color Legend */
    /* Reset */
    Oops sorry copied it all!
    html, body { margin: 0; padding: 0; border: 0; 
                                            background: transparent; font-size:10px; }
    div, span, article, aside, footer, header, hgroup, nav, section,
    h1, h2, h3, h4, h5, h6, p, blockquote, a, ol, ul, li,
    table, tr, th, td, tbody, tfoot, thead {
              margin: 0;
              padding: 0;
              border: 0;
              vertical-align: baseline;
              background: transparent;
    img           { margin:0; padding:0; border:0; }
    table, tr, th, td, tbody, tfoot, thead {
              margin: 0; padding: 0; border: 0;
              vertical-align: baseline;
              background: transparent;
    table { border-collapse: collapse; border-spacing: 0; }
    input, select, textarea, form, fieldset {
              margin: 0; padding: 0; border: 0;
    article, aside, dialog, figure, footer, header, hgroup, nav, section {
              display:block; }
    h1, h2, h3, h4, h5, h6, p, li, blockquote, td, th, a, caption, em, strong, strike {
              font-family: Arial, Helvetica, sans-serif;
              font-size:100%;
              font-weight: normal;
              font-style: normal;
              line-height: 100%;
              text-indent: 0;
              text-decoration: none;
              text-align: left;
              color: #000;
    ol, ul { list-style: none; }
    /* Global */
    html           {          }
    body          { background: #960          }
    /* Headings */
    h1, h2, h3, h4, h5, h6 { font-weight: bold; }
    h1 { font-size:24px; color:#BB5E00;
              padding-bottom:15px; border-bottom:1px #ccc solid; margin-bottom:15px; }
    h2 { font-size:20px; color:#666 }
    h3 { font-size:16px; }
    h4 { font-size:20px; color: #666}
    h5 { font-size:14px; }
    h6 { font-size:14px; }
    h1 img, h2 img, h3 img, h4 img, h5 img, h6 img { margin: 0; }
    /* Text Elements */
    p                     { color:#000; font-size:12px; line-height:150%; 
                                             margin:15px; 0; }
    p .left                              { margin: 1.5em 1.5em 1.5em 0; padding: 0; }
    p .right                     { margin: 1.5em 0 1.5em 1.5em; padding: 0; }
    a                     {   }
    a:link                              { color: #00f;  }
    a:visited                    { color: #0f0;  }
    a:active                    { color: #000;  }
    a:focus                              { color: #666;  }
    a:hover               { color: #f00;  }
    blockquote            { color:#000; font-size:12px; }
    strong                { font-weight: bold; }
    em                                    { font-style: italic; }
    /* Images */
    /* Lists */
    ul                    {  }
    ol                    { list-style-type:decimal; }
    ul li                        { color:#000; font-size:12px; }
    ol li                         { color:#000; font-size:12px; }
    dl                    {            }
    dt                           {            }
    dd                    {           }
    /* Tables */
    table                 { width:100%; }
    tr                                        {          }
    .odd                              { background-color:#eee; }
    .even                              { background-color:#fff; }
    th                    { font-weight: bold; }
    thead, th              { background: #ccc; }
    tbody                              {   }
    th,td,caption           {           }
    caption                     {           }
    tfoot                 {          }
    .tfooter                    { background-color:#ccc; text-align:center; font-style:italic; }
    caption               { background: #efefef; }
    /* Miscellaneous */
    sup, sub              { line-height: 0; }
    abbr, acronym   { border-bottom: 1px dotted #666; }
    address               {            }
    del                   { background:#FFCECE; color:#f00; }
    code, pre                    { background-color:#FF9; padding:2px 0px; margin:4px 25px;
                                                      font-family:"Courier New", Courier, monospace; font-size:12px; font-weight:normal; line-height:150%;          }
    /* Containers */
    #outer                                         {  width:960px; margin:0 auto; background:#FFF; }
    #wrapper                               {  width:900px; margin:0 auto; background:#FFF; }
    #logo                                         {  margin: 30px 0; float:left; }
    #social-media-icons                              {  float:right; }
    #social-media-icons ul li          {display:inline; }
    #social-media-icons ul                    {margin-top:40px; }
    #social-media-icons2                    {  float:left; }
    #social-media-icons2 ul li          {display:inline; }
    #social-media-icons2 ul                    {margin-top:10px; }
    #topnav                               { clear:both;  }
    #topnav          ul                              { border-top:1px #000 solid; border-bottom:1px #000 solid;
                                                                margin:20px 0; padding:10px 0;           }
    #topnav ul li                    { display:inline; }
    #topnav ul li a                    { padding:0 15px; }
    #topnav a:link                              { color: #000;  }
    #topnav a:visited                    { color: #000;  }
    #topnav a:active                    { color: #000;  }
    #topnav a:focus                              { color: #666;  }
    #topnav a:hover               { color: #f90;  }
    #banner                                        { margin-bottom:30px; }
    #rightside h2 {
    font-size: 24px;
        color: #999;
        font-weight: normal;
        margin: 0 0 0 0;
        padding: 0 0 10px 0; /*top-right-bottom-left*/
    #rightside p {
        margin: 0 0 0 0;
        padding: 0 0 10px 0; /*top-right-bottom-left*/
    #rightside a {
        text-decoration: none;
        color: #7A7D42;
        font-size: 14px;
        padding: 0 0 15px 0; /*top-right-bottom-left*/
    #rightside a:hover {
    color:#BB5E00
    #rightside p {
        margin: 0 0 0 0;
        padding: 10px 0 10px 0; /*top-right-bottom-left*/
        border-bottom: 1px solid #ccc;
    #content                               { width:650px; float:left;  }
    #content-fullwidth          {width:100%; }
    #footer                               { clear:both; margin-top:20px 0; border-top:1px #ccc solid;
                                                       padding-bottom:20px; }
    .rowWrapper {
        overflow: hidden;
        margin: 0 0 15px 0;
    .details {
    width:286px;
    float:left;
    margin: 0 0 0 20px;
    padding: 15px 0 0 0;
    border-top: 2px solid #000;
    .details p {
    margin: 0;
    padding: 0 20px;
    #box1 {   }
    #box2 {  }
    #box3 {  }
    #box4 {  }
    #box5 {   }
    #box6 {   }
    #box7 {   }
    #box6 {  }
    #box9 {   }
    #box10 {   }
    /* Layout Extra */
    /* Navigation Extra */
    /* Forms */
    /* Forms */
    form ol { list-style-type:none; }
    form           { text-align:left; margin:20px;          }
    label           {
                        float: left; width: 150px; margin-top:5px;
                        text-align:right; display:block; background:none; font-weight:bold;
    submit          { background:none;           }
    input           {
                        width: 280px; margin:0 0 16px 10px;
                        border:1px #bbb solid; padding:5px; background:none;
    input:focus, textarea:focus          { background-color:#CCC; }
    textarea {
                        width: 280px; height: 150px; margin:0 0 16px 10px;
                        border:1px #bbb solid; padding:5px; background:none;
    select { margin-bottom:20px;          }
    .month { margin-left:155px;          }
    .submit {
                        width:90px; height:25px;
                        margin-left:160px;
                        font-size:12px;
    br                    { clear: left;           }
    .clear          { clear:both; }
    /* Miscellaneous  */
    .copyright-text          { font-size:80%; font-style:italic; color:#333; }
    .footer-text          { font-size:100%; font-style:normal; color:#000; text-align:center; }
    .title                              { font-size:18px; font-weight:bold; color:#333;  }
    .subtitle                    { font-size:14px; font-style:italic; color:#333;  }
    .artist                              { font-size:16px; font-weight:bold; color:#333;  }
    .author                              { font-size:14px font-weight:bold; color:#555;  }
    .editor                              { font-size:14px font-style:italic; color:#555;  }
    .pub-date                    { font-size:10px font-style:italic; color:#555; }
    .article-date          { font-size:10px font-style:italic; color:#555;  }
    .location                    { font-size:10px font-style:italic; color:#555;  }
    .float-right          { float:right; }
    .float-left                    { float:left; }
    .clear                              { clear:both; }
    .hide                              { display:none; }
    .block                              { display:block; }
    .inline                              { display:inline; }
    .first                              { font-weight:bold; }
    .last                              { font-weight:bold; }
    .left                              { font-weight:bold; text-align:left; }
    .right                              { font-weight:bold; text-align:right; }
    .added                { background:#D7D7FF; }
    .removed              { background:#FFCECE; color:#f00; }
    .changed                    { background:#FFB; }
    /* Success, info, notice and error/alert boxes - from Blueprint CSS Framework */
    .error, .alert, .notice, .success, .info {
              padding: 0.8em; margin-bottom: 1em; border: 2px solid #ddd; }
    .error, .alert           { background: #fbe3e4; color: #8a1f11; border-color: #fbc2c4; }
    .notice                              { background: #fff6bf; color: #514721; border-color: #ffd324; }
    .success                       { background: #e6efc2; color: #264409; border-color: #c6d880; }
    .info                               { background: #d5edf8; color: #205791; border-color: #92cae4; }
    .error a           { color: #8a1f11; }
    .alert a           { color: #8a1f11; }
    .notice a   { color: #514721; }
    .success a  { color: #264409; }
    .info a                    { color: #205791; }
    #contact {
              float: right;
              clear: both;
    .big-blue {
         font-size:32px;
         color:#000;
               font-family:Monotype Corsiva;

  • InDesign Index - Indexing a book and having page links in PDF

    I am creating an index on a book made up from 30 indesign documents.  When I export the book to a PDF I want to be able to click on the index page numbers and have it go to that page.  The problem is that I can only get the index links in a PDF to work on the document that I have the index.  If I have my index in the last document and I create a index entry to the second page it creates it fine but once exported into a PDF the link doesn't work.  In CS4 I created small books like this with no problems.
    Any sugestions?
    Thanks,
    Josh

    Joshmon2003 wrote:
    Peter,
    The links that work look like this:
    The links that are not working look like this:
    for some reason indesign CS5 created the link differently when it is in a different document but in the same book.  Any ideas on how to fix this??  In CS4 this worked fine.
    Thanks,
    Josh
    Hi, Josh:
    You didn't mention the Tagged PDF and Buttons and Media settings. Not sure if they make a difference, but it helps to know as much as possible, sometimes.
    The failing link is looking for a PDF file on the H: drive, while the successful link doesn't specify a directory path. I haven't done much specifically in InDesign with exported multi-file books. However, from my Acrobat experience, I can see that the individual files of your InDesign multi-file book are being converted to individual PDF files, and their original paths are retained in the exported links.
    I don't know if the link paths are different if you export the book to PDF by deselecting all the individual InDesign book files by clicking in the blank area below the last title in the Book panel, and choose Export Book to PDF from the Book panel menu, or if you select all the titles and choose Export Selected Documents to PDF.
    As far as I know, there's no way to create a single PDF from a multi-file InDesign book document, though it's likely that the links would work because no pathname would be involved, as with your successful link.
    Are all the individual book files in a single folder (a single path), or scattered across multiple folders (multiple paths)?
    If you want your PDF book to be a collection of individual files, on thing you can try is to use Package Book for Print from the Book panel's menu. This copies everything that comprises all the individual book files, and their linked content, into one folder, with a single pathname. Exporting the book file created by the package should make all the link paths the same, so there's a good chance you'll get what you want.
    When you say that this worked in an earlier InDesign release, do you mean that the same set of project files worked in the past and are failing now in CS5? Or, is your current project a new one, with assets in multiple folders? Were all the component files and the linked stuff in your old successful project, all in one folder? 
    HTH
    Regards,
    Peter
    Peter Gold
    KnowHow ProServices

  • Gallery with Paypal buttons and drop-downs on the index page?

    I'm looking for a LR gallery where I can have thumbnails with Paypal buttons and drop-downs on the index page.
    I would prefer to keep my galleries interface streamlined and don't want to clutter it up with dropdowns and cart. I would like to have 1 page for ordering that has all my images as thumbnails with drop downs for price and size, rather than right-clicking on and image which opens in another page like the LRG Gallery with Paypal.
    I don't have a lot of experience messing with code, and none with .js. I did make a drop down in Paypal and have the code, but I think things would be pretty unwield it I designed a page as a table like I would in MS Word.
    I'm familiar with LRG Complete gallery, but don't see that it has the ability to not require a right click to order.
    I don't have a lot of experience messing with code, and none with .js. I did make a drop down in Paypal and have the code, but I think things would be pretty unwield it I designed a page as a table like I would in MS Word.
    Any thoughts, ideas, or help?
    Thanks,
    Reid

    Maybe some could try this out, and has experienced the same problem.
    It is on the site http://www.fonetix.biz
    and then push the German flag in the top Right corner, and further click on the Button "Contact info". It will give the eroor.

  • Typing in url for my company website sends it to https index page in Firefox, but not IE or Chrome, and the behavoir is not wanted

    After upgrading Firefox to version 14.0.1 i noticed when i typed in my company's website address that firefox went to the https:// version of the site when it never did that before.
    Example, if you type in amazon.com in the URL bar, you briefly see that firefox turns the url to https://www.amazon.com before being auto directed to the normal www.amazon.com site.
    My website did not have a secure index page and people were getting a server generated message until I found this issue out.
    Is there a setting in Firefox to prevent the URL bar from selecting a secure connection first? This behavior does not occur in the most recent versions of I.E. or Chrome browsers on a desktop.
    Any help would be greatly apprecaited

    I've now been forced to tell my users NOT to use FF because of it's BUG.

  • IWeb '09 and creating an "Index" page for two separate sides of my website

    I'm redesigning my website with iWeb '09 seeing that I've recently switched to Mac from being a life-long PC/Windows user. I'm not too web programming savvy so iWeb fits my needs as a very good program that redesigns my site very nicely (and quite inexpensively, as well).
    My current incarnation of my website (http://www.jeffreykern.com) was designed by a professional web designer on Dreamweaver for PC a couple of years ago. Some time ago when I was trying to update my PC with XP SP 3 (bad idea as it turned out), my connection to my web hosting service got completely fouled up and I lost the ability to update the site and haven't updated my site since. Knowing that I was going to be switching to Mac (with my new Mac Pro) I never had the desire, or energy, to patch things up to update my site with my PC. Plus, I was in need of a redesign so I eventually got my site ready to go with iWeb 09. That's where I stand right now...
    So, as you can see on my current site I have a main index page that splits up into the two sides of my life: the triathlete side and the writer side. I've already redesigned both sides of my site with iWeb, I'm ready to update it thru my web hosting via FTP and Transmit 3, but I cannot find how to create a main "Index" page on iWeb that will let me branch off into two different directions. By having that "Index" page intact I will be able to keep my domain of jeffreykern.com as it currently stands. I don't mind having to get two different domains for each of my two sides of my site but would like to avoid that extra step -- if, at all, possible.
    Thanks in advance for your help,
    Jeff

    Building three websites on three separate domain files would be my choice.
    Its important to realize that you cannot have a page called "index" using iWeb because the associated index.html file will conflict with the one that iWeb creates.
    As has been suggested, the first site would be one page. The site name would be jeffreykern.
    This site will publish as jeffreykern_files and an index.html file. Inside this folder is another index.html file. This is the one your domain name will be directed at if you don't need an RSS feed.
    If your server allows it, create a root folder on it called "jeffreykern" and upload the contents of the local folder to this and ignore the separate index.html file. Note that I said contents and not the folder itself.
    A lot of servers require that you upload to a pre existing folder. In this case you will have to upload the index.html file and the jeffreykern _files folder.
    The two other sites are named and published as writer and triathlete. The external index files of these two sites are renamed writer.html and triathlete.html.
    These two files and their corresponding folders are uploaded to your root folder on the server after adding tags and optimizing.......
    http://www.iwebformusicians.com/SearchEngines/SEO.html
    Now you have a main (one page) site with two sub sites.
    The domain name http://www.jeffreykern.com/ is directed at the index.html file so that when this is entered into the browser, the main page will appear.
    The links to the two main sections, whether they be text and/or image, are created and selected as external hyperlinks.
    http://www.jeffreykern.com/triathlete/
    http://www.jeffreykern.com/writer/
    Clicking these links will open the first page of their respective sites.
    If you do the sensible thing and trash the iWeb default navigation to replace it with a custom one, you can include external hyperlinks to the landing page and the other site in this.
    The website - iWeb for Musicians - is created like this and is built on 9 separate domain files for ease of updating and publishing. The whole site is tied together with a Main navigation to get to each section which has a Sub navigation to jump around that section.
    For more on navigation see.....
    http://www.iwebformusicians.com/WebMusic/Navigation.html
    Also refer to Fonts, Colors and Navigation on this page ......
    http://www.iwebformusicians.com/WebMusic/iWebandInternetExplorer.html

  • I have the latest Pages  5.2 and get a sign saying "INDEX.pages" can't be opened. I have need of some of the documents. What can i do?

                            I have the latest Pages  5.2 and get a sign saying "INDEX.pages" can't be opened. I have need of some of the documents. What can i do?

    Probably you have 2 versions of Pages on your Mac.
    Pages 5 is in your Applications folder.
    Pages '09/'08 is in your Applications/iWork folder.
    You are alternately opening the wrong versions.
    Pages '09/'08 can not open Pages 5 files and you will get the warning that you need a newer version.
    Older versions of Pages 5 can not open Pages 5.2 files and you will get the warning that you need a newer version.
    Pages 5 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
    Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
    Once opened and saved in Pages 5.2 files can not be opened in Pages 5.
    Anything that is saved to iCloud and opened by newer Pages versions anywhere, is also converted to Pages 5 files.
    All Pages files no matter what version and incompatibility have the same extension .pages.
    Pages 5 files are now only compatible with themselves on a very restricted set of hardware, software and Operating Systems and will not transfer correctly on any other server software than iCloud.
    Apple has removed over 95 features from Pages 5 and added many bugs:
    http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
    Archive/trash Pages 5, after exporting all Pages 5 files to Pages '09 or Word .docx, and rate/review it in the App Store, then get back to work.
    Peter

  • Have changed the "Index" of my website in Dreamweaver and followed the "Put" instructions to upload it back to the "Remote Server," but when I go onto the web to check it, the main (Index) page has not changed.  Help!

    Have changed the "Index" of my website in Dreamweaver and followed the "Put" instructions to upload it back to the "Remote Server," but when I go onto the web to check it, the main (Index) page has not changed.  Help!

    This is a duplicate post; see How do I upload from Dreamweaver CS6?

  • The Index page will not show the title with Bookmarking and the Facebook "like" or "share"

    When you utilize the Facebook Like button on your Muse created web pages, it carries the title over (from the Page Properties) and works fine, except for the Index. This also applies to bookmarking pages. When the Facebook like is used (and the sub window for Facebook opens) it is titled “Home” that’s it. When the index page is bookmarked it also says “Home”. Why won’t the whole title be used? Is there any way to correct this?

    Hi,
    Could you please provide the url of the site and let me take a look to your current settings,

  • 301 redirects and iWeb index page

    Our site has grown and we will be changing our domain name and hosting co. (We are keeping the old domain active for a while at MME before we change domain name and hosting) I will need to redirect traffic for a while so as not to lose those who have just bookmarked us. Will just redirecting on the index page that iWeb creates (post publish) do that without creating a mess of our page rankings at Google? Currently we are in the top 15 responses for our search terms. Or should i create some other type of redirect? 301? (via cname or htaccess) will that ding me at google? Thanks- try to keep it as simple as possible - I don't code - I experiment and Apple has made it easy.
    jy

    What I would do is purchase the hosting and see if you can have more than one add-on domain. Most web hosts let you do this on one account so it doesn't cost you any more money. You are doing this because you will need a .htaccess file to set up your 301 redirects properly. This is what you should do;
    1) Register your new domain and publish your site to it.
    2) Create a webmaster tools account for BOTH your old and new domain name.
    3) Create a 301 redirect for each individual page to the new corresponding page on your new domain. This can be done with a few lines in your .htaccess file. The file should be in your root folder of your OLD domain. Put this on your .htaccess file (NOTE: This assumes you will have the exact same website structure on the new domain);
    RewriteEngine ON
    RewriteRule ^(.*)$ http://mynewdomain.com/$1 \[R=301,L\]
    OPTIONAL: Use Google's canonical tag on each one of your pages to avoid any issues with duplicate content. Link the old page to it's new corresponding page. This is optional but recommended if you can;
    <link rel="canonical" href="http://www.newdomain.com/newpage.html" />
    4) Login to your Webmaster Tools account and select your OLD domain. Then select 'Site Configuration' and then 'change of address'. Follow the steps provided (which are basically what I told you above). Step 4 in there is the important one.
    5) Submit a sitemap for your new website. This will make sure you know when Google has indexed your new website.
    6) Important: Even though you have done everything properly there is a chance your rankings will change. To help prevent this, update as many third party links as you can to your new site. This won't be possible for all links since you won't have control over them but you should try contacting the website owners who have linked to you to update their links. You should also try getting new links to your new domain.
    You can find all the sites you have linked to you by logging into your webmaster tools account and clicking your OLD domain. Then go to 'Your site on the web' and then to 'Links to your site'.
    Nothing will be instant here, it will take a few days for everything to update but the above is the way Google recommends you do it.
    HTH

  • Unable to access java web application index page on Weblogic server 10.3.6

    Hi,
    I have deployed a Web application on Weblogic server.
    My war file is very basic with just a index page.
    I am able to deploy & access its index page properly in OC4J ( applicaton server on soa suite 10g ) and apache tomcat.
    But when i deployed same war file in weblogic am not able to access its index page, Getting below error:
    Error 503--Service Unavailable
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    *10.5.4 503 Service Unavailable*The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
    status=Prepared, Consolidated State=Prepared, Target-Specific State= Prepared.
    what does Prepared indicates here?*
    Adminserver.log prints blow log when i try to access the index page
    ####<Dec 26, 2012 8:27:17 AM GMT> <Warning> <netuix> <soa-app-dev-01.am.health.ge.com> <AdminServer> <[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'> <501226496> <> <9b375c7445d8c121:79ee4f70:13bc880be7a:-8000-0000000000000209> <1356510437306> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WebAppApplicationOverviewPage&WebAppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3D*Weblogs*%2CType%3DAppDeployment%22%29.>
    My Deployment descriptors are as below:
    Web.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
    <display-name>Weblogs</display-name>
    <welcome-file-list>
    <welcome-file>index.html</welcome-file>
    </welcome-file-list>
    <servlet>
    <description></description>
    <display-name>SOA11gLogServlet</display-name>
    <servlet-name>SOA11gLogServlet</servlet-name>
    <servlet-class>com.ge.healthcare.soa.logs.SOA11gLogServlet</servlet-class>
    </servlet>
    </web-app>
    ==================================================================
    weblogic.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-web-app xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.3/weblogic-web-app.xsd">
    <wls:weblogic-version>10.3.6</wls:weblogic-version>
    <wls:context-root>/Weblogs</wls:context-root>
    </wls:weblogic-web-app>
    ==================================================================
    Please help me to resolve the issue,its bit urgent.Let me know in case of anything else required to check and verify.
    Thanks in advance.
    Regards,
    Rahul Aahir
    Edited by: 978673 on Dec 26, 2012 4:22 PM
    Edited by: 978673 on Dec 26, 2012 4:32 PM

    In weblogic 10.3.6, when you deploy using console, you have to click on start button which appears in Deployments page.
    Your weblogic.xml file should be as below:
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-web-app xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.3/weblogic-web-app.xsd">
    <wls:weblogic-version>10.3.6</wls:weblogic-version>
    <wls:context-root>/logs</wls:context-root>
    <container-descriptor>
    <index-directory-enabled>true</index-directory-enabled>
    </container-descriptor>
    <virtual-directory-mapping>
         <local-path>/opt/oracle/logs</local-path> (as per your path)
         <url-pattern>/logs/*</url-pattern>
         <url-pattern>*.log</url-pattern>
    </virtual-directory-mapping>
    </wls:weblogic-web-app>

  • Rediect particular URLs to index page

    Hi,
    From Apache1.3, I have to redirect all the URLs coming from port http://mydomain.com:9001/servlet/* to a index page (index.html).
    I tried giving "Redirect" directive under mod_alias
    Redirect /servlet http://mydomain.com:9001/index.html
    but it is looking for http://mydomain.com:9001/index.html/* and is not redirecting it to the file. How can I do this.

    Allie,
    Can you tell me how you figured out how to have one index page link to a 2nd index page like the california example you described?
    I am trying to do exactly that but layout is not happening the way I would like so i think I am doing something wrong
    Thanks
    Patrick

Maybe you are looking for