Until recent years, we treated our servers like pets. We gave them names and assigned a high value to their health and uptime. If a server went down, we did everything in our power to get it back up and running. With the advent of virtualization, the term server became more synonymous with VM (Virtual Machine) and the fact that it was running didn’t really have as much significance simply because we could spin up many more like it within minutes. But that was still a problem. We had to spin up many more just like it. We had gone from treating servers like pets, to treating them more like cattle. It appears the dream of virtualization was realized as we didn’t need to worry about one specific server anymore. If web-007 failed, web-001 through web-006 were still around to handle the traffic and no one would even notice the difference while a new instance was generated. But even in this new virtual reality, the virtual environment (our cattle) had to be up and running all the time, feeding on energy and they needed attention.

This was a problem that didn’t seem to have a solution. It seemed that if you needed to compute a bit of logic, you would have to pass that request to a service that could process it for you and give you a result. So, the cattle were as efficient as we could get for a long while. But realistically, each bit of computing request is just a tiny little request. Surely, we don’t need an entire virtual farm always on standby to fulfill requests that are not even being called on all the time. What if we moved from the cattle model to the bacteria model? Imagine an infinite ocean of tiny little computing units (our bacteria) that would instantly rush to our call whenever we needed them. Now imagine if that ocean was shared by all our applications.

This is the serverless dream. In the cloud ecosystem, we call these container services and major cloud providers like Microsoft Azure and Amazon Web Services offer these container services in an all you can eat ocean of compute that you can tap into whenever and however much you desire. Imagine never having to scale your server infrastructure. Imagine only getting charged for the infinitesimally small amounts of time that the CPU is processing your request. That is what services like AWS Lambda provide. AWS Lambda lets you run code without provisioning or managing servers. You pay only for the compute time you consume – there is no charge when your code is not running. You simply write all the logic of your code within a Lambda function, link the function to an application gateway and you’re ready to invoke your logic from anywhere, on any device, at any time, and as many times as you like. It is easy to see that with this new model of computing, your data center will soon become a thing of the past, and with it the skillset you have developed around the data center model.

So, what will it take to go fully serverless? Can you run your applications on this new computing platform? How do you develop applications in a way that can take advantage of these new technologies? Subscribe to our newsletter to be notified of our upcoming articles that will address all these questions. If you have a serverless development project that you would like to talk to us about, you can contact us directly here. Nogalis has been developing serverless applications using AWS Lambda since 2017 and we’d love to discuss your upcoming projects.

The Nogalis team is always busy with multiple projects, and a way to stay on top of our productivity is by using Trello. Trello is a web based list-making application that is shared by everyone in your team to keep everyone up to date on all tasks, progress, and deadlines. This helps our team stay current with all our projects. Trello also has a blog that features tips on increasing productivity, workflows, and current events and news. We’ll be sharing some of those tips on our own blog from time to time. Take a look at the first tip below!

 

Overcoming Defense Mechanisms

Defense mechanisms were first noted by notable psychologist Sigmund Freud. At their core, defense mechanisms are self-serving. We subconsciously use them to protect ourselves from negative thoughts or feelings such as anxiety or guilt. How do you stop your own defense mechanism from becoming a bigger problem, especially in the workplace? There are a few things you can do. The first step in making any change is to recognize the problem. Analyze your thoughts, emotions, reactions, and exchanges at work to figure out which of the above defense mechanisms you’re using as a crutch. Following this you can practice compartmentalization by segregating different thoughts or portions of your life (i.e. shutting out any personal problems while you’re at work). Next, projection; assign your own thoughts and emotions to others. Then practice undoing by attempting to backpedal a negative behavior with a lot of positive. For example, if your first line of defense is to say something negative to a colleague, then backpedal and instead compliment or say something positive about the given situation. We all have defense mechanisms and we all have the capability to change (not use them as often), especially in the workplace. By eliminating such defensive habits, we could get more work done at the office and increase work productivity.

Original post by Kat Boogaard from Trello.

 

For Full Article, Click Here

 

Stay tuned for more tips from Trello!

 

You might come across the need to update a service or identity configuration in ssoconfig (LSF), especially if you have implemented AD FS and need to update your usernames or service URLs. A quick way to update a ssoconfig service is to load an XML file with the updates. Create and save your XML file, set your environment variables on LSF, then run the command ssoconfig -l <password> <filepath>

Here is the file format for a service and an identity (make sure OVERRIDE is set to true if you are doing an update):

 

<?xml version=”1.0″ encoding=”ISO-8859-1″?>

<BATCH_LOAD FORMAT=”” OVERRIDE=”true”>

  <SERVICE>

<HasCredential>TRUE</HasCredential>

<LoginProcedure>Form based</LoginProcedure>

<ID>DSSOIBITEST</ID>

<SvcEntryAttrList>user,password</SvcEntryAttrList>

<LOGINSCHEME NAME=”Form”>

<PROTOASSERT>Use HTTPS always</PROTOASSERT>

<HTTPURL>https://server.company.com:80/sso/SSOServlet</HTTPURL>

<HTTPSURL>https://server.company.com:443/sso/SSOServlet</HTTPSURL>

<PRIMARYTARGETLOOKUP>Verify passwords in Lawson Security</PRIMARYTARGETLOOKUP>

<LOGIN_RDN/>

<NAMING_ATTR>cn</NAMING_ATTR>

<USERNAMEFIELD>_ssoUser</USERNAMEFIELD>

<PASSWDFIELD>_ssoPass</PASSWDFIELD>

<SERVICEURL>https://server.company.com:443/sso/SSOServlet</SERVICEURL>

<LOGIN_SUBMIT_METHOD>POST</LOGIN_SUBMIT_METHOD>

</LOGINSCHEME>

<IdentityAttrList>user</IdentityAttrList>

<CredentialAttrList>PASSWORD</CredentialAttrList>

     </SERVICE>

</BATCH_LOAD>

 

<?xml version=”1.0″ encoding=”ISO-8859-1″ standalone=”no”?>

<BATCH_LOAD FORMAT=”Opaque” OVERRIDE=”TRUE”>

<IDENTITY SERVICENAME=”SSOP” >

<RDID>lawson</RDID>

<USER><![CDATA[[email protected]]]></USER>

</IDENTITY>

</BATCH_LOAD>

 

To convert LBI to use https, the first step is to make sure that you have valid PKCS 12 certificates installed in the Personal and Trusted Root stores on your LBI server. Export your certificate (or have your system admin do it for you) with the public key and private key, and with the full certificate chain.  During the export, provide a password for the certs.

In WebSphere on your LBI server, go to Security > SSL certificate and key management.  Select Key stores and certificates > NodeDefaultKeyStore > Personal certificates. Replace the default certificate with the cert that you just exported. Do the same for the CellDefaultKeyStore (if applicable). Next, under Key stores and certificates again, select the KeyStore and TrustStore, and select “Exchange Signers…”

Add your new certificate from the KeyStore to the TrustStore and Apply. Save the changes. No need to restart your application server yet, we will do that in a bit.

Make sure that your Virtual Hosts contain an alias for the secure port you plan to use. Note that this port must be the WC_defaulthost_secure port under Ports on your Application Server.

In LSF, update your DSP service for LBI to use the new service URL. The service should be set to “Use HTTPS always” and the new service URL should be “https://lbiserver.company.com:port/sso/SSOServlet.

Restart your LSF application server and your LBI application server.

Open your LBI install validator with https://lbiserver.company.com:secureport/efs/InstallValidator and make sure the system URL is set to the new secure URL. Submit the new URL. If the certificates are not valid, you will receive an error message indicating as such. Otherwise, there should be no failed tests.

As you might have heard, we’ve been working on a fully cloud-based, vendor self service solution for about a year now. We have worked with several customers to create a solution that is simple, intuitive, and brings instant value to any organization dealing with vendors and suppliers. Join us on Thursday June 6th (9am PST) as we do a walk-thru and a public Q&A. The webinar will feature the following modules and functionality:

  • Vendor OnBoarding
  • Vendor Check Requests and Invoice Submissions
  • Purchase Requests
  • Routing, Approvals, Document Management, Audit, Integration, and much more

Infor’s newest partnership is with Destination XL Group (DXLG), the industry’s leader in men’s big and tall apparel. This partnership allows DXLG to increase their market share and top line sales, improve customer segmentation and drive state-of-the-art marketing activities. Infor Alliance partner Three Deep Marketing will work alongside DXLG to leverage Infor’s rich breadth of customer engagement solutions to deepen relationships with existing and new customers by better understanding preferences around promotions, pricing and assortment. DXLG will implement Infor CloudSuite CRM, Infor Marketing Resource Management (MRM), Infor Omni-channel Campaign Management (OCM), and Infor Loyalty powered by CrowdTwist to provide relevant communications across all channels. “With Infor’s end-to-end customer engagement solutions, we can understand our customers better, produce rich and deep customer profiles and drive incredibly smart segmentation to connect and engage with our customers in a more meaningful and targeted way,” said Jim Davey, CMO of Destination XL Group. Infor’s Retail division now supports more than 2,500 global fashion, retail, and grocery brands that work to modernize operations by taking advantage of the latest consumer and business technologies — mobile, social, science and cloud.

 

For Full Article, Click Here

When you configure LSF for ADFS, you will need to make some changes to your LBI configuration so that users will be able to access LBI with the userPrincipalName.

The first thing you need to do is ensure that you have a user in Lawson security where RMID = SSOP = UPN (userPrincipalName).  The RM User that is used to search LSF for LBI users must have an account where RMID and SSOP match.  It is recommended that you have a new AD user created for this purpose (such as lbirmadmin).

Add the new user to Lawson, ensuring that their ID and SSOP values both use UPN.  Also make sure the new user is in the appropriate LBI groups for LBI access.

The next change will take place in the sysconfig.xml file located in <LBI install directory>/FrameworkServices/conf.  The ssoRMUserid should be the UPN of your LBI user mentioned above.  After you make these changes, restart the application server, clear the IOS cache in Lawson, and try logging into LBI.

If you update your LSF core technology, and subsequently find that your SSO applications (such as LBI or MSCM) produce a 500 service error, you probably need to update your DSP install on the host server for the SSO application.  Please see our article archive for instructions on how to update and reconfigure DSP.

If you get a “NoClassFoundError”, you may need to add a new class path to your JVM properties in WebSphere.  Figure out which class is missing and add the path to the JVM properties, then restart your application server and check to see if the issue is resolved.

Nothing makes an organization run more smoothly than the right Customer Relationship Management (CRM) system. However, you must regularly evaluate if your current system is doing the job for your growing company. Barrett Cordero, President of BigSpeak, a leading global speakers bureau, recently learned that their CRM system needed updating. He shares seven signs below that you should look for to know when it’s time for you to update your CRM system to something better.

  1. It’s unreliable – If your CRM used to work perfectly but now can’t be relied on 99% of the time, it’s time to switch systems.
  2. It doesn’t do mobile – If you can’t access your CRM by phone, you miss opportunities.
  3. It doesn’t integrate with other software systems – integrating with other systems (sales, contracts, websites) is a huge time saver.
  4. It’s user unfriendly – friendly deisgn makes for quick and easy navigation (again, saving time).
  5. It doesn’t work well across departments – If your CRM works well for one department but bad for others, then it’s bad for your entire company.
  6. It doesn’t have growth potential – If your CRM doesn’t have the potential to grow with your company, then it’s time to find the kind of CRM that can grow with you.
  7. It’s all you talk about – When you reach this stage, it’s time to do the research, take the leap and spend some time getting a new system in place.

It may take a while to realize you need to change your CRM system. But when you first notice it, take immediate action and start finding a newer and better system to help your business go further.

 

For Full Article, Click Here

If you see some error messages when you first open IFS (similar to the message below), make sure that all components of the Application Server have been installed.

These are installed in the Server Management area > Add Roles and Features.  The Application Server role is delivered with PowerShell commands that are required for IFS to run.