I Have Installed Broad leaf Admin and Run Successfully.
But I have only four modules displaying on admin page.
On log in to the Demo at The Broad leaf original site i have seen the extra modules on Admin panel.
How can i get the Remaining options as Displaying on Demo on Broad leaf official site. Please help me to solve this issue.
This is almost certainly because you are running the community version of Broadleaf Commerce locally. However, the demo version online (where a demo is provisioned for you) includes enterprise features. This explains the difference in the modules you are seeing in the admin when you run locally. If you would like to utilize the enterprise features, you'll need to contact Broadleaf in regard to paying for an enterprise subscription.
Related
I apologize if this is a weird question but i can't really find good information regarding this.
I have a website that I would like to deliver as a product for other organizations to download and use within their organization. Much like Confluence or Wordpress. I know how they do it, they just package up their code and you can download it and deploy it yourself, however I'm just wondering what the other options are out there.
Is there a way to bundle up the entire site into an installer or create an image of some sort that can be downloaded and deployed. Ideally, I wouldn't want the customer to deploy the code and configure it themselves. It would be nice for them to just have to download something, run it and its up.
Any process or tool recommendations is greatly appreciated. Thanks!
A solution that I was looking for is something like Docker. https://www.docker.com/
You can build a docker image that basically has all the prerequisites for your application built into it and you can deploy it across most machines that have docker install.
Even with confluence server, you still have to, at the minimum, configure a database, a home folder (for the product logs, plugins, cache), and the server itself to host the confluence product.
If you want to have the customer just use the product, then you should be hosting the whole product from your side and the customer can just create an instance for their company on your product (e.g. confluence cloud, Basecamp, workplace by facebook).
So, for these products that use the cloud solution, I only have to signup for an account, I don't need to handle any server side configuration or database as these are handled by your product hosting. But in the end it depends on what is your product and who are you targeting.
If you are targeting enterprise customers who do not want their data hosted in the cloud and want to have their own firewall, then you will need a server product. Nevertheless, these companies which have their own servers will also have IT admins who can handle the installation and configuration for your product as long as its well documented and easy to follow.
I have a client that wanted an easier way for his team members to build/update pages on their site, their site is heavily customized with a lot of JavaScript. The issues is that when a team member wanted to add a new section to the page they had consult a dev person to hard code in the desired features. So we decided to create customizable web parts of those features making the site more self-serviceable.
When I first started I found some documentation that said to use visual studios to build the web part using sandbox code, upload it to the site and then they would just need to activate it to deploy it on the site. Buuut unbeknownst to me code based sandbox solutions are no longer supported in Sharepoint and therefore the web parts we built could not be deployed. I was then told that I needed to build it as an Add-in, but as I started building the add-ins I found that the customizable field properties (i.e. ability to change background color, text style/color and banner color) that I want are not implementable as a add-ins.
So now I’m back at square one and I don’t know if it’s even possible to build a web part as a add-in or do I need to go a different route?
Any thoughts or links to sources you can provide would be HUGELY appreciated!
Thanks
Terek
In SharePoint 2016 things have changed a lot from the traditional model which was the classic way of building web parts. The way you worked before is called "classic", the new way is called "modern", and the way to get your dev environment is the following (brace yourself, it is a long answer):
1) In SP2016/Online you will need to configure your dev machine with the following environment, installing the following:
NodeJS Long Term Support version
Yeoman (which will be used to create web parts)
GULP (which will play the role of virtual web server)
Once the three components above are installed, you will install the Yeoman SharePoint Generator to create the SharePoint Web Parts, Yeoman simplifies the process of creating things by delivering templates ready to use and making all the configurations standard, you gonna love this guy!
To configure your machine see the following link:
https://dev.office.com/sharepoint/docs/spfx/set-up-your-development-environment
2) In SP2016/SP Online, you will develop for SPFx (SharePoint Framework), Microsoft has made significant efforts to address the changes and help developers to embark on this new journey by publishing training and educational material at GitHub, YouTube, and on its official website (I will add link below), but for the purpose of helping you, please follow this tutorial, it helped me to learn how to develop Modern Web Parts for SP 2016/Online:
https://dev.office.com/sharepoint/docs/spfx/web-parts/get-started/build-a-hello-world-web-part
3) From the tutorial above, you will get a fully functional Modern Web Part that can be deployed to SP2016/Online, you will see the new modern architecture allows you that old experience of "sandboxing" web parts in a faster way without, thus solving your problem of constant updating/refactoring components in a live production environment. This way now allows you to constantly update the code and see the results in real-time , you will be able to see results on your dev environment by calling: https://localhost:4321/temp/workbench.html and at same time on your SP environment. for example: http://portal.company.com/_layouts/workbench.aspx
Links:
YouTube "SharePoint Framework Tutorials" - it is the step by step tutorial video showing the whole process of creating a web part:
https://www.youtube.com/playlist?list=PLR9nK3mnD-OXvSWvS2zglCzz4iplhVrKq
GitHub repository with the full documentation, samples and extras for the SPFx and PnP (this is another story for another time):
https://github.com/SharePoint
I hope it helps you!
I'm creating a UWP application that will be used exclusively on rugged Win10 tablets by a group of initially 10-20. If things go well it will be expanded to 100 users. These users are employees of our company, but will be remotely located.
Currently, with the test tablets, I am pushing the packages in google drive and manually copying them to the tablets, unzipping and executing the ps file on the tablet. This is way to complicated for even a beta test group of our users.
I'm looking for short-term/long-term recommendations for deployment. Someone mentioned SCCM to me and I've read a little, but that seems like quite a major endeavor to host. I would prefer something like a "private store" concept, but I can't find anything like that.
You can create a private store for your company. The best solution is probably to use Windows Store for Business. http://www.microsoft.com/en-us/business-store
Microsoft Azure Active Directory (AD) accounts for your employees are needed if you select this solution.
An alternative way is to use HockeyApp http://hockeyapp.net to deploy your application.
According to your description, HockeyApp should meet your requirement. Via HockeyApp, you can upload and distribute builds for beta or enterprise distribution using our web UI, or our API. HockeyApp also supports build servers like Jenkins or Visual Studio Team Services. Don't forget to upload your dSYM or
mapping.txt to get readable crash reports.
With HockeySDK for UWP integrated, you can also:
Integrate our open-source SDK to:
Collect crash reports
Show update alerts for new beta builds
Add a feedback view directly into your app
For more information, please visit support.hockeyapp.net.
I'm very new to YouTrack and tried using it on local host under Mac OSX. My first impression on it was really stuck and can't say in words how neat and elegant was the whole user interface. I'm really loving it now and would like to adapt the UI to electrical and electronics engineering projects along with the issue tracking. So far I'm already into the play and have found plenty of useful customisable features which I can turn them into the ones relevant to engineering stuff. Now I'm moving to some intermediate skill to change the UI and got some doubts to be clarified. Here are the list of queries I've got now.
I'm now trying it on local host under Mac OSX and its running fine without any issues. I would like to install and do online testing like hosting it under siteground or goddady and use custom domain/sub domain to access it. I mean so that I can give my team the online access.
I've came across other products like team city, upsource and hub. Could you please explain in brief on each?
I will be using it for 8-10 users now and is there any option to purchase access to custom logo, private projects and ssl without upgrading to more users.
Thank you.
I have worked with Websphere Portal 6.0,6.1 and developed portal applications usign JSR 168,JSR 286 Portlets.
Now I am moving to project where I will be working with Liferay portal server and JSR 168,JSR 286.
I know that as per programming interface (JSRs) It will be the same. But want to know what are the major difference at server level ( features,configuration,architecture, out-of-box services) when compared to Websphere Portal ?
Thanks
Liferay also supports JSR168 and JSR286 portlets, so in respect to that you can use the same API's as you are using in WebSphere Portal. The product itself cannot be easily compared to WPS as they both have different concepts. Liferay doesn't have a credential vault, for example, but it still supports SSO (NTLM or CAS). Your WebSphere Portal knowledge won't help you much in Liferay development, as it is a totally different product.
I agree the configuration will be different but I think it will help a lot the fact that you are prepared to think about the information architechture.
The main difference is that Liferay is not really that much prepared for escalability. It uses velocity so neither of the tags you use will help (Placeholders, component, element, etc).
It doesnt have that many portlets by default so you will have to develop a lot from the starter point.
Check this out for a really nice comparision (the slides are in spanish, and require the flash plug-in):
http://www.slideshare.net/mcimino/websphere-portal-vs-liferay-by-gartner-v10
Basically Liferay weaker points are in B2C and support. If you need to build a site that will rely heavily on personalization, you will have much work to do too.
Hope it helps