nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SP - is it required to submit component in runtime environment ?

nirjari

Once component is credated in dev environment, do we need to submit this component in runtime environment ? We need to submit DCR, JSP in runtime environment in order to get them displayed. Sameway , do we need to submit component in the runtime.
I think , we do need to submit it in runtime, otherwise how wd xsl display the content ? But I am not sure.

thanks

Find more posts tagged with

Comments

PayalGarg

If you are talking about LS runtime environment then components are not submitted to LS runtime. Pages (.page files) that contain components are deployed to LS runtime, not actual .component files.

When you create any component, you need to submit it to the STAGING area to make it available to the pages (.page files). Else your component will not be available for use.

Thanks
Payal

vpatel

I think the original post was in context of moving a component from development TS to production TS. If that is the case then you can manually copy it over or you can use Archive Manager (SPAR) mechanism. There are also other ways to do things if you are well-versed with WCM product line.

sumitk

Once component is credated in dev environment, do we need to submit this component in runtime environment ? We need to submit DCR, JSP in runtime environment in order to get them displayed. Sameway , do we need to submit component in the runtime.

What are you referring to by RunTime Environment?

Cheers,

Sumit

nirjari

Thanks Payal, you have got my confusion right.

If we just submit component to staging and not to LS runtime, how will it be available in LS runtime ? Does the .page file contain the component ? I have many pages that use a component. I make a change to this component, in SP and submit it to staging. How will the change be reflected on all the pages in LS runtime ? Do I need to use changed component on all the pages again in SP and submit them in LS runtime environment again ? Or will the change made in component in SP dev will automatically reflect on all the pages ? If change in compnent is not being rerflected on the pages in LS then how can I make change in multiple pages using SP ? do I need to do all the changes manually ?

thanks

vpatel

Read up on the "Component update/overwrite" mechanism in the SP Dev guide. Also in TS CC Pro UI, look at SitePublisher menu item and there is an option to do GetLatest Components -- play around with that a little bit. Alternatively, re-open a .page file that contains components that were updated and it'll prompt you if you want to update/overwrite them.

HTH!

PayalGarg

For multiple SP pages you can use SitePublisher > Get Latest Components. But you need to be careful with options provided along with this command. Alternatively, as vpatel said, you can edit each page, that contains the altered component. It will provide you with an option to "get latest component or override component changes".

After getting latest components on the page, you need to publish the page to LS runtime using workflows. Only then component changes (in .page file) will be available in LS runtime.

Thanks
Payal

Testing_Report.rptdesign

nirjari

If I am using a component in many SP pages, then whenever I open a page using that component I will get a message abpout updating component in that page. This is one way to change the component on page.

What if I want to update the component in all the pages wherever this component is used ? Is there ant functionality available to update the component upon change ? Or we have to update the component on all the pages one by onemanually while visiting that page ?

thanks

Adam Stoller

If I am using a component in many SP pages, then whenever I open a page using that component I will get a message abpout updating component in that page. This is one way to change the component on page.

What if I want to update the component in all the pages wherever this component is used ? Is there ant functionality available to update the component upon change ? Or we have to update the component on all the pages one by onemanually while visiting that page ?

thanks

Did you even bother to read the previously supplied response?

vpatel

Did you even bother to read the previously supplied response?

Apparently not.

nirjari

what I wanted to ask is, if I do SitePublisher > Get Latest Components , it will update all the pages. But if I have to submit all the updated pages individually, then its just like updating all the pages manually. Is there a way to update all pages in runtime simultaneously ?

Adam Stoller

what I wanted to ask is, if I do SitePublisher > Get Latest Components , it will update all the pages. But if I have to submit all the updated pages individually...

Have you never done a View Modified from the top of the workarea?

vpatel

what I wanted to ask is, if I do SitePublisher > Get Latest Components , it will update all the pages. But if I have to submit all the updated pages individually, then its just like updating all the pages manually. Is there a way to update all pages in runtime simultaneously ?

You can select which pages you want the changes applied to. Yes you'll probably have to publish those pages in order to see the changes in Runtime -- depends on what sort of change you are looking at.