We want to build a large customer web portal for our customer care rep and end customers. The web portal has multiple functionalities like Case mgmt, customer mgmt, reports, Trouble shooting tools,etc. Each of these are built by separate team but the portal is to be hosted/deployed/accessed using one url and the portal should have SSO to navigate across these functionalities/modules. Each of the modules can be built and hosted in separate servers. What are the alternatives to build such web application where multiple teams can make releases independent of each other. Less scenarios to merge source code. Note the technology stack is AngularJS for UI and Spring Rest API for backend server. Any design proposals will be appreciated. Not looking for portlets since they have their own challenges
One Option is each of these functionalities will be modeled as tab and within each tab we have an iframe which gets data from separate app server.
Related
This is the first time i'm working with firebase. My goal is to have a bounch of client apps (more and more over time), all of them managed by an admin app (One app to rule them all).
The thing is that the client apps have a certain content that needs to be updated from the admin app. My best approach is to create a firebase project, put the admin app there and adding client apps over time. I'have read that is possible to have an unlimited number of apps inside one Firebase project. On addition, someone told me to create one project for each client app and connect them to the same database somehow. I simply don't know what to do.
Which would be the best solution for my problem? thank you
firebaser here
A Firebase project can currently contain up to 30 app definitions. This is meant to support variations of the same logical application. For example, having an Admin app in addition to the app for regular users, and/or having an iOS, Android, and Web version of the same app, and for example having a free and a pro version of the app (if that is allowed by the stores where you deliver them).
Adding multiple apps to a project is expressly not meant to be used for white labeling apps, where you ship essentially the same app with different branding to different user segments, as you'd be sharing the backend services between them. For some backend services (such as database and storage) this is not necessarily a problem, as you can isolate the customers with security rules. But for other services (such as authentication and analytics) this is not possible, which is why this use-case is not supported.
If you need to define a separate app in the project for each customer, the only supported approach is to create a separate project for each customer.
I'have read that is possible to have an unlimited number of apps inside one Firebase project.
In that case please provide a link, so we can either fix it, or (if it's not in the Firebase documentation) leave a comment to clarify.
Im trying to connect a website i've built using HTML, CSS and JS to the Apache OFBIZ database I have built.
The web app's main purpose is to allow the user to download the app and order the case, and allow them to put in their personal details including method of payment and purchase the case through, by connecting to the OFBIZ data base which has a number of fields that once approved will confirm the order and notify the relevant members of the manufacturing process and allow the user to see that their order has been received and confirmed.
thanks in advance,
H
OFBiz is a web development framework with ERP business modules on top of it. It's made to be enhanced and you can build your own web applications with OFBiz. I would simply build the website with OFBiz, providing a form for the user detail input. You will have all options to use the database, services etc..
If you have to access OFBiz with a native app (IOS, Android & Co.) you might want to implement some RESTful services to connect OFBiz with your app.
From what I understand, I would migrate the website to OFBiz. If it has a responsive UI design, it will run nicely on smartphones.
Let me start with a bit of background: I'm helping a non-profit organization that would like to have a browser-based application that is backed by Salesforce, but has very specific requirements.
I see Salesforce has a REST API that we can call, so we can develop a standalone application to serve the web pages they want and use the REST API to call Salesforce when needed.
I'm wondering if there is a way to host a web application directly on Salesforce; this way we don't have to have a separate application server. Any recommendations or pointers to documentation/open source products is greatly appreciated.
Yes, you can create services that will allow your app to hit Salesforce
Depending on the type of application, yes you can host it on salesforce using the Salesforce Sites feature, also you can develop and host your app on Heroku which is owned by salesforce and can sync data to and from salesforce using Heroku Connect, or you can build and host it on another service like AWS and connect via the REST API. You just need to investigate and choose the option that best fits your use-case. One thing to be aware of is that there are API limits (the number of calls you can make to salesforce in a rolling 24hr period). Depending the the needs of the app be sure to see if those limits will be an issue. Because if the app makes constant calls to salesforce that could be an issue. But there are things you can do to get around that, like caching.
Yes, both Force.com Sites and Site.com features allow you to host webpages on the Force.com Platform. The markup is stored in Visualforce Pages and can use Apex to access records in the Database. I have migrated multiple websites (including our company's www.mkpartners.com) to Force.com using Force.com Sites.
One thing to keep in mind is that you are limited to 500,000 views per month and the rendering of a page with images that are also stored on the platform will incur a single view for the page and a single view for each image. If you already have a very popular website, I wouldn't migrate. If you're a small business or nonprofit, then it should be fine.
Another thing to keep in mind is that dynamic functionality based on records in the database will not work during maintenance windows. There is the ability to upload a static version of your website to be rendered during these windows though.
I have started developing in AngularJS to implement a single-page application. The domain (Single-Page application) looks really interesting; can we develop a round-trip application in which we will have many pages, using AngularJS in some parts of the application. For example, if we are developing a Employees invoice which consists of Employee Management, Invoice management etc.; Can all employee management tasks be implemented in a single page and the Invoice Management in the other page?
Best Regards,
Mouli.
Yes, you can devleop multple page applications.
Here is a good post
Is AngularJS just for single-page applications (SPAs)?
AngularJS Multi-Page App Site Boilerplate Site Structure Advice
I have currently a visual studio that contains 3 projects :
MyApp.Models : Contains all my models with Code-First migrations
MyApp.Web : Contains my main website, only with MVC
MyApp.Pass : Contains a subdomain website, for customers.
We have new projects and we need to have those things :
A WebAPI that can be consumes by my main website, my pass website, a backoffice website, and a mobile application
a backoffice website that consumes WebApi, built with AngularJS
A mobile application that consumes WebApi, built with Xamarin
How can i layer my visual studio solution to only have one WebAPI that can be consume by all my differents websites/mobile app ?
Best regards,
I am currently building a side project - viewingbooker.com which is exactly the setup you are looking for.
What you need to bare in mind is that web api and mvc website have 2 different authentication techniques. Web Api 2 makes amazingly easy to authorise users from eg. xamarin mobile apps. Token is issued and is generally valid for 14 days of inactivity.
I have few projects within my solutions. Most importantly you need a separate project for your business logic. I also use DI to test my business logic as I go.
For website, I serve data as JSON from standard Controllers. For my mobile app, I have a separate web api project that serves the data separately. They both use business logic project so it keeps code redundancy to the minimum.
Remember that mobile app is not a website which you can quickly fix. If you end up using the same models and controllers for website and mobile apps, any change you make will brake your mobile apps and not all users have auto upgrade feature switched on on their mobile devices.
So I recommend you have a standard website with its own models and controllers, which is consumed by angular/knockout etc. Web API 2 project with its own models and controllers. Business logic project in the form of different services accessible by its interfaces so it's easier to test it. And don't get too paranoid with code redundancy that is different controllers, models for website/mobile. This approach will save you a lot of headache in the future - talking from experience.